This behavior may be due to your computer being unable to load the files required to open LabVIEW properly. This is typically caused by a lack of Windows user permissions or files that have been corrupted or moved from their default location. The issue can also be caused by the firewall blocking a port that LabVIEW or Volume License Manager needs to communicate over. Steps to resolve these issues can be seen below, organized by the potential causes for this issue.
Lack of Windows User Permissions
If this is the first time LabVIEW has been installed on this computer, then the issue is most likely due to a lack of Windows user permissions. See the steps below to diagnose and fix problems with your user permissions.
- Right-click on 'LabVIEW.exe' and select 'Run as Administrator'.
- The default file path for LabVIEW.exe (32 bit) is C:\Program Files (x86)\National Instruments\[LabVIEW Version]\LabVIEW.exe
- The default file path for LabVIEW.exe (64 bit) is C:\Program Files\National Instruments\[LabVIEW Version]\LabVIEW.exe
- You may need an administrator to enter their credentials to run the program as an administrator
- If LabVIEW loads properly when it is run as an administrator, then the root of the issue is lack of proper permissions on files contained in the National Instruments program file directory. Please work with your IT department to configure your account with the proper permissions to use LabVIEW.
- If using a 32 bit version of LabVIEW, the default path for the relevant National Instrument Program Files folder is C:\Program Files (x86)\National Instruments
- If using a 64 bit version of LabVIEW, the default path for the relevant National Instrument Program Files folder is C:\Program Files\National Instruments
Corrupted or Moved Files
If your software was installed using a DVD, USB, or downloading media from the NI's website:
- Try repairing the software's installation
- For LabVIEW versions 2016 and earlier, follow these steps to repair through the Control Panel
- For LabVIEW versions 2017 and newer, follow these steps to repair through the command line
- Try Force Reinstalling the software, as described in this article
- Try uninstalling and reinstalling the software
If your software was installed using NI Package Manager:
- Uninstall the package through the NI Package Manager
- Download a clean version of the package through the NI Package Manager and install it on your system.
- If the problem is still present after reinstalling the software,
- Uninstall LabVIEW again from the NI Package Manager.
- Then, delete the C:\Program Files (x86)\National Instruments\LabVIEW 20XX folder (32bit) or the C:\Program Files\National Instruments\LabVIEW 20XX folder (64bit), depending on the bitness of your LabVIEW version. Make sure to backup any user library that you're using (user.lib folder), or any instrument driver under the instr.lib folder
- Install the software again using the NI Package Manager.
If, while the software is attempting to load, you see the splash screen for product activation appear, something may have gone wrong with your activation. Try the steps below to correct your activation status.
- Make sure that your NI License Manager is installed correctly and not corrupted.
- Deactivate your software through the NI License Manager
- Use one of these methods to activate your software again
- Try the steps listed above for resolving corrupted or missing files
Firewall blocking a port
If nothing happens when you launch LabVIEW; the firewall might be blocking a port that LabVIEW or Volume License Manager needs to communicate over. If the issue has recently started occurring, check whether you still have an active license.
Follow the next steps to enable dropped packets logging and check what connections are being blocked by your firewall:
- Navigate to Control Panel >> System and Security >> Administrative Tools >> Windows Defender Firewall with Advanced Security.
- From the Action pane, select properties.
- Select the appropriate firewall profile (Domain, Private or Public). You can also enable logging in all the profiles.
- On the logging section, click customize.
- Select the location where you want to save the logs and change the Log dropped packets option to yes.
- Click OK to enable logging.
- Try to open LabVIEW and then open the log file and check for any blocked ports. Pay special attention to ports used by NI products.
If you spot any blocked port in the log file after trying to open LabVIEW, follow the next instructions to allow it:
- In Windows Defender Firewall with Advanced Security select Inbound Rules in the left pane.
- Click new rule.
- On the Rule Type page, select port and click next.
- On the Protocol and Ports page, select the protocol type and the specific local port you want to allow.
- On the Action page, select Allow the connection and then click next.
- On the Profile page, select the profiles to which this rule applies and click next.
- On the Name page, you can write a name and description for your rule.
- Click Finish to apply the rule.
You might not have enough permissions to allow the port. In that case, please work with your IT department to allow it.
If LabVIEW still will not open correctly after following these steps, please contact NI Support for further assistance.