From 04:00 PM CDT – 08:00 PM CDT (09:00 PM UTC – 01:00 AM UTC) Tuesday, April 16, will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.


Showing results for 
Search instead for 
Did you mean: 

Change currently active LV version in batch script

Go to solution

On my machine the Default value of HKEY_CLASSES_ROOT\LabVIEW.Application\CLSID is {9A872070-0A06-11D1-90B7-00A024CE2744}. This value is equal on three different machines that I checked.


I found 9A872070-0A06-11D1-90B7-00A024CE2744 six times in the registry (I think all with equal values) and decided to use HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{9A872070-0A06-11D1-90B7-00A024CE2744}\LocalServer, since this is the only one in the HKEY_CLASSES_ROOT\ section that you mentioned. This values gives me the path of the active LV version (it changes as expected when I start another LV Version) and I can then start the required LV version if it is not already active.


So far I always use 9A872070-0A06-11D1-90B7-00A024CE2744 for the LabVIEW application key, but following your note I plan to read out the value of HKEY_CLASSES_ROOT\LabVIEW.Application\CLSID in the registry and work with this one.


I don't understand why the active LV version is hidden so deep in the registry and it took half a day until I got through the registry searching stuff and it is still not coded in a "nice" way. But anyway I can get my things done with the above approach.


Thanks very much, Norbert.

0 Kudos
Message 11 of 12

Hi TobiasT, 


I am also looking at a similar problem. We have test stations in production with multiple versions of LV and products that require specific versions. 


Cant your batch file just launch a specific version of LV by calling the .exe? That should set it as the "active" version. Then proceed to call your other code that just references the "active" version. 


Sr Test Engineer at American Innovations - LabVIEW CLA - Kudo's are appreciated!!
0 Kudos
Message 12 of 12