LabVIEW 2014 installer points to wrong minimum OS

[goed99]

Yep this happened to mee too. I'm running lv2014 on a win 7 machine. It started after I did an update with the NI-Update service. Very annoying.

[Baptiste_CA]

Under LabView 2012SP1, I am having the same issue. I do not think that I updated anything from NI lately, except the NI Updater itself.

I noticed that the installer builer files (C:\Program Files (x86)\National Instruments\Shared\MIF\MetaSuite) are all pretty recent on my pc (2016-06-02) and the version of Setup.exe is 16.0.0.169, the same as the versin of the setup.exe generated in my installer.

The older installer that I generated had a setup.exe with version 15.0.0.172.

So looks like NI Installer Version 16.0.0 does not support Windows XP, whereas Version 15.0.0 did.

I am not sure how NI Installer 16 got on my PC in the first place though... Does someone have an Idea? Was it installed together with the Ni-Update-Service Version 16.0.0?

[LarryC-ATS]

---

@Baptiste_CA wrote:

Does someone have an Idea? Was it installed together with the Ni-Update-Service Version 16.0.0?

---

That is the last thing that I recall updating.  It sounds reasonable to me that this is the source.  So it seems that the caveat is, if you have to install code on Windows XP/Vista/Server 2003 or 2008, don't update the Update Service.  Otherwise you will be stuck editing your setup.ini files until all your targets are upgraded.

[Taki1999]

Yeah. I still think I'd call this an NI rollout bug since they should've nixed the Application Builder option to build for XP when they pushed the Update Service Update.

Would've saved me some headache with my customer if I'd gotten a popup that told me my project was now broken and needed to be retargeted.

So two things:

1. My customer really shouldn't be on XP anyway, but it's hard to convince them of that.

2. If I setup Application Builder to build for XP, Builder should tell me if it can't do that and is now going to automatically set Vista as the minimum.

1. is a people thing that I can't do a whole lot about. 2 is an NI thing that I hope a future update at least makes consistent.

[Edna-S]

Hi all,

I apologize that you are experiencing this issue. Please take a look at this newly written NI KB (79UC78LS) that can potentially resolve this issue.

[goed99]

Thanks.

It would be really helpful with a note on the easiest/least painful way to Roll back the MDF 16.0 to its previous version.

[Baptiste_CA]

I think I managed to revert to the previous version of MDF (version 15). This allowed again to generate an installer that works on XP without manipulation.
Here are the steps I followed:
1- uninstall MDF 16: browse to C:\ProgramData\National Instruments\MDF\ProductCache\MDF Support [16.0.169]\MDF, double-click MDFSupport.msi and select uninstall when the dialog appears.
2- download the Update Service version 15: http://www.ni.com/download/ni-update-service-15.0/2617/en/, do not start the exe
3- extract the content of the exe (it is a selfextracting zip file) into a temporary folder "NIUS1500".
4- in the de-archived folder, browse to .\Products\MDF\MDF and double-click MDFSupport.msi. Install.
5- Voila - I do not guarantee that this does not break something else...

[Edna-S]

MDF isn't forward compatibile, therefore we don't recommend downgrading the MDF version. This will cause problems in some cases. If you absolutly have to run your deployment installer on Windows XP, Windows Vista or Windows Server 2003, we would recommend you modify the setup.ini file.

[WNM]

Note that if you also happened to install any of the drivers that come in the August 2016 driver update DVDs and if your installed application makes use of any of those drivers, then even if you manage to trick the installer to install onto the older system, the application will fail to run because these newest drivers will be incompatible with the older system.  To add insult to injury, there is not a good way to back out of a driver update because any attempt to install the newer drivers will also want to uninstall any older NI software that depends on them which can be very disruptive to a development system if you have multiple older versions of LabVIEW installed.

[BRLUIZFELIPPE]

I found myself in a similiar situation. I have an application running since 2015. Currently, after refactoring this application and rebuilting it, I have got this message informing this application requires windows 7 or later, but no change was made to my advance settings (Installer builder). After changing the setup.ini file to the same OS as done before, I could have my application installed and running again.