LabWindows/CVI Idea Exchange

Community Browser
Showing results for 
Search instead for 
Did you mean: 
Post an idea



because I had installed CVI2010 on a brand new Windows 7 machine, I was curios to find out about all the service processes running on the system.

It seems that there are quite a few NI services that start after log-on. Some of  them seem superfluous, such as the Lookout Citadel service (no LabVIEW, no Lookout installed), but due to the lack of any information I did not bother trying to stop them



1) NI should critically review the services and only start the services that are absolutely needed.

2) Services that are optional might be selected by a checkbox during installation or from the Options / Environment setting

3) NI should provide some documentation / explanation of each service and why it is needed.



It appears that when adding a font to the installation package by having the installer copy the font file to the [Fonts] installation directory, all the installer appears to do is copy the font to the C:\Windows\Fonts directory.  This is good enough for Windows XP, but in later versions of Windows additional steps must be performed for the font to be recognized by Windows.  It would be nice if the installation package could perform these steps when installing fonts on these versions of Windows.

I develop software for many older systems that can not be upgraded or are running windows embedded.  I just tried to create a new application and could not install it from my distribution.  I found out I had to go and edit the setup.ini.  NI Installer Requires Windows 10 64-Bit (Version 1507) or Newer.  I've been using CVI since the DOS days.  One of the advantages has always been that I could recompile and I generally didn't have to worry about Windows updates screwing up my software.  This change seems ridiculous all of a sudden.


I recently installed the LabWindows 2017 beta version on a lab PC and tried using it to run a project built with 2015 SP1.  Unfortunately it didn't work because of a bug I found in the beta: calling the NewBitmap or SetBitmapData function crashes the program if the number of bits per pixel is 1 or 4.


Uninstalling the beta is proving to be difficult.  I performed an uninstall on LabWindows 2017 and Run-Time Engine 2017 through the Windows control panel, but it made me uninstall LabWindows 2015 SP1, NI-DAQ, and LabVIEW as well (because they were all dependent on the RTE).  Windows appeared to run the uninstall successfully, but the RTE folder and DLLs were somehow not removed or changed.  So when I rebuilt and re-ran my project, it still linked with the 2017 RTE and still crashed.  I had to manually copy the 2015 RTE files from another PC.


Even after this, there are still some other elements of the 2017 version left on the PC, such as the activation manager.


I would like to NI change this so that when the user uninstalls a new RTE, it automatically restores whatever previous version was active before the update without the hassle of having to uninstall and reinstall LabWindows, LabVIEW, etc.

Hi Everybody,
I'm a student, and now i'm interning at a company that wants me to develop an industrial vision system.
I would like to ask you if i can use NI Vision Builder for Automated Inspection (VBAI) with the Labwindows/ CVI
If so, how? and what are the difficulties that may affect me?
THANK YOU for your help !
Best regards,

At present, when you double-click on a .cws or .prj file the most recent version of the CVI IDE is launched with the selected .prj or .cws file loaded.

However, both project and workspace files include the release of CVI they are developed on, so it would be possible to search in the system whether that release is installed and open it instead of the most recent one. This is crucial when you need to modify a program already deployed to a customer but do not want / is not possible to update the target machine configuration installing a newer Run-Time module than the one already installed.

At present you have no control over this event, but consider also that in case you make modifications to the UIR files also, it may become difficult to revert to the original IDE format; for this reason when I need to update an old program I need firstly to open the project file in notepad to see which CVI release to use for this.


If automating the launch in the correct release is not possible, at least issue a warning stating the difference in the IDE release used with respect to the original one.

I feel that beginners might study the examples provided with CVI more frequently / in more detail if they were more aware of the Example Finder. Right now, it can be only found via the Help menu. I think that the Example Finder is as important as the Release Notes or the Readme and thus should be more visible.


Suggestion: Add the Example Finder to the Startup menu.

Newest version of LabWindows have not one importatnt option in installation software builder. It is "run executable at and of installation"