LabVIEW 2012 Runtime on Windows 11 - Installation/Compatibility Issues

[xXHunterXx]

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 developementl 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.

[GerdW]

Hi Hunter,

---

@xXHunterXx wrote:

Have .vi, .ctl, .lvlps files but no developementl license:(

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

---

• When you want to install an executable then you (usually) don't need those VIs, CTLs or lvlps files…
• Why don't you "unblock" the installer installation? Should be the way to go…
• Is there any hardware driver needed for your executable?

[Bob_Schor]

Hello, Hunter.

     You are attempting to "port" LabVIEW 2012 code (14 years out of date) running on Windows 7 (at least three version of Windows out of date) that you want to run on a Windows 11 PC and deploy with a LabVIEW Installer.

     My "guess" is the least-expensive, most-likely-to-succeed method to accomplish your goals is to create a LabVIEW 202x (2024, 2025, 2026) "Development PC" running Windows 11 and running one of the just-mentioned LabVIEW Development licenses (either a "perpetual license" or a "renewable" one, I forget the name for this).

     Your first task, of course, is to upgrade your original LabVIEW 2012/Windows 7 Project to a LabVIEW 202x version, make sure it runs with your (presumably 2012) hardware, then build an Executable or Installer for your "Deployment" PC (also running Windows 11).  I have limited experience with Installers -- I prefer creating Executables and installing the appropriate LabVIEW RunTime on the target PC, but I've done both (though not from LabVIEW 2012/Windows 7!).

Bob Schor