Labview Installer Requires Windows 10

0 views

Skip to first unread message

Favio Cassidy

unread,

Aug 3, 2024, 6:04:31 PM8/3/24

to styltaimaros

I've got a machine running Windows 10 Enterprise 2015 LTSB. When I try to install the latest LabVIEW (2023Q3), I get an error that says the installer requires Windows 10 64-bit (version 1607) or newer. I've installed all Windows updates on this machine, so it's running the latest available. What can I do to get LabVIEW installed? Thanks in advance.

I guess one obvious question is: "Is your version of windows x64?" Sorry, sometimes it's the obvious questions that you forget about. Also, look here for more reasons why your version of Windows may not qualify.

Note that NI has online and offline installers. Online installers install the latest NIPM version which currently require 1607, so you likely need to download and install the offline version of our installers.

Thanks for the additional detail, Scott! Since I don't think I can download older versions of LabVIEW, I went down the path and upgraded to Windows 10 Enterprise 2019 LTSC, and then I was able to install LabVIEW 2023 without issue.

If the NI product you are installing uses Microsoft .NET 4.6.2, the .NET installer may run before any NI software installs and may require a reboot before the installation of NI software begins. To avoid a .NET reboot, install .NET 4.6.2 separately before you install NI software.

Henning, NI Package Manager has always preinstalled .NET for any NI software that requires it, and now NIPM installs 4.8 for the few software that depend on it. LabVIEW as of yet does not require 4.8, but LabVIEW does depend on a version of NIPM that does.

I have an application built in labview 2012 which we have been distributing fine with an installer built in labview 2012 for some time. Recently, a colleague tried to install the application onto a windows 10 machine and although the installation process seemed to go smoothly, for some reason, one of the two exe's distributed by the installer gives me the ever so helpful "This VI is not executable. Full development version is required. This VI is not executable. Full development version is required. This VI is not executable. Full development version is required. This VI is not executable. Full development version is required. This VI is not executable. Full development version is required. This VI is not executable. Full development version is required. ..... (you get the picture!)" error.

As an experiment I set up two clean virtual machines, one running windows 7 SP1, one running windows 10. I ran the same installer on both. In windows 7, I got a prompt saying that .NET framework 4.6.1 needed to be installed first, and that happened automatically, and after that the installer continued and everything worked fine (including the exe in question). On windows 10 I got no such warning. The installer ran through and the exe failed with the error message described above.

On the Win10 VM, I then went in to "Turn windows features on/off" and although there's a tick in the ".NET framework 4.6 advanced features", there's no specific sign of 4.6.1. for a test, I added a tick to add .NET framework 3.5 (includes .NET 2.0 and 3.0) and installed that. That made my .exe run fine....

So.... is there any way to force the LV installer to prompt for/install the necessary .net "stuff" when running in Windows 10? Anything else I can do to automate things so that our customers dont need to manually add .net support for the program to run if they're using windows 10?

What you ran into is that, by default, LabVIEW 2012 uses .NET 2. There is a significant change to .NET 3 and later that requires different behavior down in the bowels to use. NI has an article on how to specify using later .NET versions. LabVIEW 2015 uses .NET 4 by default (not sure the version where the switch occurs). One option would be to have LabVIEW use .NET 4 as that should be present on Windows 10.

What I find strange is that on a fresh windows 7 install, the installer built with LV tells me I need first to install .NET4.6.1 and then does it. Why cant it do something similar in windows 10 and alert me to the fact that .NET installs are needed and do those for me!

You can easily download the .NET Framework 3.5 offline installer and add this install to your installer as an action. You can run the offline installer in "silent mode" so that it installs or bypasses if installation already exists.

So, I am having an issue among multiple clients who are getting messages that indicate that an application requires 64 bit Windows 10 even though the installation is specified for Windows 7 and the version of LV this is developed in is 32 bit. Does anyone have any thoughts as to what might be going on?

Yes, I saw that and I don't understand that. This was built in 32-bit LV and there is not a specific selection for the drivers that is 32 or 64 bit in the installer dialog. It is also built for Windows 7 or greater but the dialog the customer is getting is that this is for Windows 10.

It's the MDF 20.7 or newer that gets installed with almost all NI 20.7 or newer software components. This Meta Deployment Framework is the shared software component that is used by all product builders, be it the LabVIEW Installer Builder or the LabWindows/CVI Builder, or whatever else can build installer packages such as NIPM.

If you are building the older style of deployment (not using NIPM), then the KB that Rolfk posted above tells you how you can edit .ini file post-build to allow the installer to run on Windows 7 / 32-bit. However, keep in mind that you cannot include any newer drivers that have dropped support for these older OSs, as they may not longer function (such as if 32-bit kernel DLLs have been removed or if the driver signing requirements changed).

Calm down! The workaround is and actually has been for a long time to instal a Virtual Machine Manager and setup an environment that matches your requirements. If you have clients who still require Windows 7 you have exactly two options nowadays:

- Telling them that these systems are unsupported and supporting an unsupported system is very expensive and makes you have to go to extra lengths and back and forth to still support it and that that will cost accordingly.

Anything else is taking up a fight against the big guys in the computer industry (and no NI does not belong to them, they are just little peasants in this as you and me too) and fighting windmills and foot the bill yourself too.

This guide is intended for Java and C++ teams. LabVIEW teams can skip to Installing LabVIEW for FRC (LabVIEW only). Python teams can skip to Python Installation Guide. Additionally, the below tutorial shows Windows 10, but the steps are identical for all operating systems. Notes differentiating operating systems will be shown.

Upgrading from earlier 2024 releases is easy: simply download and run the new installer and it will update your current installation. If you already have the 2024 WPILib vscode installed, it will detect it and you can simply click "next" for that installation step. After installation, vscode will prompt you when opening your robot project whether you want to upgrade it to this version. Note that using the installer is required to get the new version of desktop tools such as Shuffleboard. This release is compatible with both 2024_v2 releases of the RoboRIO image. Mac note: if upgrading from 2024.1.1, it is necessary to manually remove the 2024.1.1 version of AdvantageScope before running the installer in order for the new version to be installed.

System Requirements: WPILib requires 64-bit Windows 10 or 11, Ubuntu 22.04, or macOS 12 or higher. C++ teams should note that Visual Studio 2022 17.9 is required for desktop builds. Mac users will need to have the Xcode Command Line Tools installed before running the installer. This can be done by running xcode-select --install in the Terminal.

If you're returning from a previous season, check out what's new for 2024. You will need a new RoboRIO image for 2024; this is available via the FRC 2024 Game Tools. Follow the WPILib installation guide to install WPILib.

Other installed programs may associate with iso files and the mount option may not appear. If that software does not give the option to mount or extract the iso file, then follow the directions below.

For this release, macOS users will need to have the Xcode Command Line Tools installed before running the installer; we are working on removing this requirement in a future release. This can be done by running xcode-select --install in the Terminal.

You will notice two buttons, Install for this User and Install for all Users. Install for this User only installs it on the current user account, and does not require administrator privileges. However, Install for all Users installs the tools for all system accounts and will require administrator access. Install for all Users is not an option for macOS and Linux.

Selecting this option will bring up a prompt allowing you to select a pre-existing zip file of VS Code that has been downloaded by the installer previously. This option does not let you select an already installed copy of VS Code on your machine.

Visual Studio Code - The supported IDE for 2019 and later robot code development. The offline installer sets up a separate copy of VS Code for WPILib development, even if you already have VS Code on your machine. This is done because some of the settings that make the WPILib setup work may break existing workflows if you use VS Code for other projects.