LabVIEW or LabWindows™/CVI Taking a Long Time to Launch

Updated Jul 31, 2023

Reported In


  • LabVIEW
  • LabWindows/CVI

Issue Details

Whenever I try to launch LabVIEW or  LabWindows™/CVI, it sits at the main window or splash screen for several minutes. Why is it taking so long to launch LabVIEW or  LabWindows™/CVI and are there any configuration changes I can make so that LabVIEW launches faster?


  • Change your Remote System settings to only search for resources that are present and being used.
To change your Remote Settings:
  1. Open MAX
  2. Under My System, expand the Software folder
  3. Under the Software folder, click on NI-VISA
  4. At the bottom of the MAX window, select the VISA Options tab
  5. Select General Settings » Remote.
  6. Uncheck any unnecessary targets.
  • Check for any expired or invalid LabVIEW or  LabWindows™/CVI licenses. 
To check if you have expired licenses:
  1. Open NI License Manager
  2. Under the LabVIEW or  LabWindows™/CVI version, you are trying to launch, check to see if there are any half red/half white boxes or circles. This indicates an expired or invalid license
  3. Uninstall any toolkits that are expired
  4. If any volume licenses are shown as evaluation or backup mode, confirm that the client is able to access the license server.
  • Disable CRL checking by changing a setting in Internet Explorer. Use the following steps to disable the CRL checking in Internet Explorer:
  1. Select Start » Control Panel.
  2. Open the Network and Internet category.
  3. Click Internet Options.
  4. Select the Advanced tab.
  5. In the Security section, uncheck the Check for publisher's certificate revocation option.
This disables the CRL check that is delaying the application.
  • Check for a corrupted LabVIEW.ini file:
Locate your LabVIEW installation folder:
  • LabVIEW 32-bit: C:\Program Files (x86)\National Instruments\LabVIEW 20xx
  • LabVIEW 64-bit: C:\Program Files\National Instruments\LabVIEW 20xx 
In the LabVIEW installation folder, you will find the LabVIEW.ini file. If this file has a size grater than a few KBs (red Box in the Screenshot) it’s a corrupted INI-file which causes the long start-up time.

To resolve this issue, you need:
  1. Locate your LabVIEW.ini File
  2. Delete all the ini$$X.TMP Files (yellow Box in the Screenshot)
  3. Delete the LabVIEW.ini File (be aware that all your LabVIEW settings will be reset)
  4. Restart LabVIEW
More information regarding the INI-file, can we found in the Additional Information section.
  • Upgrade to the newest version of NI License Manager. The latest version can be downloaded from here .
If you are already using an up-to-date version of NI License Manager, then please try deleting the NI LM configuration file to avoid any kind of corruption that might cause the slow startup of LabVIEW. Here is the configuration file path: "%localappdata%\Nationalnstruments\UserAccount\Configuration.xml"
  • If none of the above listed steps help, Repair or reinstall LabVIEW or LabWindows™/CVI

Additional Information

When working with real-time targets using VISA, it is possible to setup LabVIEW to connect to specified real-time targets and search for available resources every time LabVIEW launches. The more targets that are specified, the longer the time it takes to find all the available resources. The length of time it takes for LabVIEW to find the resource on a real-time target is dramatically increased if a target is specified that does not exist anymore. If this is the case, LabVIEW searches for the resource that is no longer present and eventually times out. 

A similar thing happens when there are expired licenses for Toolkits. When LabVIEW launches, it checks the licenses for the development system and any toolkits installed. If there is a toolkit installed with an expired license, LabVIEW will timeout trying to verify this license. 

An .ini file is a plain text file set up to store and retrieve settings. These settings can be used to configure an application such as LabVIEW.
The LabVIEW.ini is created on the first start-up of LabVIEW and loaded each time LabVIEW starts.
Therefore, a force reinstall will not work to resolve this issue because the LabVIEW.ini file is not created or replaced by the LabVIEW installer.