This content is not available in your preferred language.

The content is shown in another available language. Your browser may include features that can help translate the text.

Running Executables or Installers on Different Windows Versions

Updated Feb 28, 2019

Reported In

Software

  • LabVIEW Application Builder Module
  • LabVIEW
  • LabWindows/CVI

Operating System

  • Windows
  • Linux
  • Mac OS X

Issue Details

I want to run an executable or installer that was created on a Windows PC on another Windows PC with a different operating system.  Will I run into any issues doing so?

For example:
  • I have created a installer of an application with LabVIEW 2014 on a Windows 7 computer. I would like to know if I can use this same installer to install my application on a Windows 10 computer.
  • I have created an EXE for my application in LabVIEW 2014 on a Windows 7 computer.  I would like to distribute that EXE to computers that run Winodws XP, Windows 7, Windows 8, Windows 10.
  • I have created an EXE for my application in LabWindows/CVI on a Windows XP computer. I would like to run that executable on a target computer that has Windows 7.
  • I have created an installer for my LabVIEW application on my development machine, which is Windows 7. When I move it to an older version of Windows like Windows XP, I get this error: The installation requires Windows 7 SP1 or later.
  • I have created a installer of an application with LabVIEW 2015 on a Windows 7 computer. When I use the same installer to install my application on a Windows 10 computer I get a broke arrow that says "This VI is not executable. The full development version of LabVIEW is required to fix the errors." 

Solution

Installers and executables are only guaranteed to work on the operating system they are specifically built for.  For example, a Windows 7 installer or executable may not work as expected on a different Windows version (e.g. Windows XP, Windows 8, Windows 10). Also, if you are using .NET framework to develop your code, make sure you are using the same versions of .NET in your Development PC and your Deployment PC. 

In the Related Links section you will find a link that explains how to force LabVIEW to use a particular .NET version.

Alternatives:
  • Set up a virtual machine that matches the OS version and bitness of the machine used to build the executable or installer.
  • Run the application using Windows compatibility mode(external link).  This is not known to be a reliable solution.  You will have to look up the steps for running compatibility mode for your specific Windows version as the steps are different for different versions of Windows.

Additional Information

Any VI that you create can be opened and run in LabVIEW Development System on a computer running a different operating system, as long as the version is compatible with the VI (generally must be same version or newer). Bitness of LabVIEW (32-bit, 64-bit) does not need to match, because the code is not compiled until the VI is run.  However, all operating systems and LabVIEW Development Systems involved must have support for all the libraries, toolkits, modules, and drivers used by the given VI.

WAS THIS ARTICLE HELPFUL?

Not Helpful