MetaUtils\MSIProperties.msi error occurs when installing NIPM 2025 Q4 or earlier versions.

[Long9999]

"I just bought a new computer and started installing NIPM and LabVIEW. However, when installing NIPM, an error appeared as shown in the image below. Could someone please help me fix this issue?

[Scott_Richardson]

I do not remember how to instruct the NIPM installer to log. You could check the log directories mentioned in this KB, but likely they are for subsequent installs after NIPM is installed: Generating and Locating NI Package Manager Error Logs

[Praneeth_B]

Hi Long9999,

Were you able to get past the error? MSIProperties.msi is the first MSI installed when running the 2025 Q4 NIPM installer. If it fails, it usually indicates that something on your system is preventing MSIs from running successfully, possibly due to insufficient permissions on certain folders or registry keys, or a Windows update running in the background.

This KB has the details on some common issues: An Error Occurred While Installing a Package in NI Package Manager - NI

To find the exact issue, NIPM logs present in "C:\Users\<Windows Username>\AppData\Local\National Instruments\NI Package Manager\Logs" would be helpful. 

MSI logs would help us pinpoint the issue even more accurately. They can be enabled by doing the following (Reference: https://learn.microsoft.com/en-us/troubleshoot/windows-client/application-management/enable-windows-...)

1. Edit the registry and create the following key:
   Path:HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer
   Type: Reg_SZ
   Value: Logging
   Data: voicewarmupx
2. Perform the install operation that fails.
3. Look to see what new msi*.log are files created in the directory that %temp% resolve to.
4. Revert the registry change when done with debugging. 

Note that the normal way of enabling MSI logs: Generating and Locating NI Package Manager Error Logs - NI would not work here as NIPM itself is not installed, hence the above steps.

Please see if you can try out some of the suggestion in ⁠the KB or provide us the NIPM and MSI logs so we can find the issue.