WinMIF Not Compatible With .NET 4.8 Error When Deploying Custom Installer

Updated Mar 6, 2025

Reported In

Software

  • Package Manager
  • LabWindows/CVI
  • LabVIEW
  • TestStand

Issue Details

  • I have built an installer with LabVIEW, and it works on my development machine. When I run the installer on a deployment machine, I see the below error.
  • I recently installed NI Package Manager (NIPM) 23.3 or later and when I build an installer using LabVIEW, TestStand Deployment Utility, LabWindows™/CVI™, or other NI software. The installer builds fine, but when I try to run it on my deployment computer I get the following error message:

This distribution is built with an older version of winMIF that is not compatible with .NET 4.8.0. upgrade to 22.8.0.  
 
installer error.png

Solution

The error is occurring because NI Package Manager versions equal or above 23.3 install .NET 4.8 instead of .NET 4.6.2. When a product like LabVIEW builds an installer that includes the .NET product, the resulting installer only understands how to install .NET 4.6.2 and not .NET 4.8. 

 

In order to fix this, use the attached installer with the below steps on your build system to upgrade the required infrastructure packages to allow built installers to properly install .NET 4.8.
 

  1. Make sure the NI software you are using to build the custom installer is closed.
  2. Download the attached zip file: NI ADE Deployment Support.zip.
  3. Unzip the file.
  4. Navigate to the Install.exe file and run it.
  5. Open your software and rebuild your custom installer. 

Additional Information

You can run into this issue if the NI ADE Deployment Support package under your INSTALLED tab in NIPM is below 23.3 version. The attached installer updates this package (named "ni-mdfsupport_...") and its dependencies in your NI Package Manager cache (C:\ProgramData\National Instruments\NI Package Manager\Downloads) to move to a version that includes the fix for this issue. 

 

Future releases of the NI products will automatically include these updated packages, so you will get this update with most of NI software updates.

 

If you are using an older software stack but you are seeing this issue, please follow the steps of this article to update only the minimum components you need to fix the behavior without changing the versions for the rest of your NI software.