LabVIEW 2012 Runtime on Windows 11 - Installation/Compatibility Issues

[HunterX]

Hello LabVIEW Community,

I'm facing challenges running a legacy LabVIEW 2012 SP1 application on Windows 11 and would appreciate guidance.

Situation:

Production system: LabVIEW 2012 SP1 program on Windows 7

Need to evaluate/extend program on Windows 11 development machine

Have .vi, .ctl, .lvlps files but no deve  I acceptlopment license

Attempted Solutions: ( I assume )

Installed LabVIEW 2012 SP1 Runtime (patch files available, but installer blocked by Windows 11 security)

Windows 11 blocks lvrunner.exe installation; only support files install

.vi files associate with NILVWSPostInstallerScript instead of LabVIEW

Newer Runtime versions (2022 Q3) blocked by company firewall

Questions:

Has anyone successfully run LabVIEW 2012 Runtime on Windows 11?

Are there workarounds for Windows 11 security blocking older NI installers?

Can LabVIEW 2022+ Runtime open 2012 .vi files in read-only mode?

Alternative viewers or methods to examine .vi structure without full LabVIEW?
----------------------------------------------------------------------------------
Any insights would be greatly appreciated.

[Tim_S]

Checking with IT would be a good thing to do as they may have a solution already available.

Older applications can be run using Windows Compatibility mode. That can be a bit of a crap shoot, particularly when you start including drivers into the mix.

Virtual machines solve running older code by using older operating systems. This is great for some applications, but accessing hardware (like anything in a PCIe slot) can become an issue.  Also this may not be an acceptable solution depending on IT security policies and that the virtual machine counts as a separate instance of Windows for licensing costs. This is the route I had to take to get LabVIEW 2012 and needed drivers to install on a WIn10 computer.

If you have the source code (which sounds like you do) and can get a development license you can update the application which would resolve many compatibility issues. Depending on hours spent trying to make this work and how critical the nature is there may be a case this could be the cheapest option.