Showing results for 
Search instead for 
Did you mean: 

64-bit Windows required for Installation

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?

0 Kudos
Message 1 of 14

Do you have a copy of the install.ini (or equivalent) created by the build?

0 Kudos
Message 2 of 14

Yes I do.  Here it is.

0 Kudos
Message 3 of 14

Looks like you include installers for e.g. serialRuntime, serialRuntime64, NIvisaRuntime, NIvisaRuntime64, and many others.


There is also the entry "Has64bitPart=1"


I would look into the additional installers setting of the installer builder and make sure you only include what's needed. Did you do an automatic or manual selection?

0 Kudos
Message 4 of 14

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.

0 Kudos
Message 5 of 14

I recently tried to install NI DAQmx 20.7 but I cancelled when I saw this:


I had a similar issue in the past about LabVIEW 2011 and Windows XP, solved installing LabVIEW in a virtual machine.

Don't know if all this is relevant for you.

LV 7.1, 2011, 2017, 2019, 2021
0 Kudos
Message 6 of 14

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.

Rolf Kalbermatter
DEMO, TU Delft
My Blog
Message 7 of 14
(1,448 Views) what is the work around for this?  This is unacceptable.  I have clients running on 32-bit windows 7 that can not just shift their entire product line.

0 Kudos
Message 8 of 14

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

0 Kudos
Message 9 of 14

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 Windows 7 (and 8 and 8.1) are already fully unsupported and you can't support it anymore

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

Rolf Kalbermatter
DEMO, TU Delft
My Blog
Message 10 of 14