NI Package Manager (NIPM)

cancel
Showing results for 
Search instead for 
Did you mean: 

An error occurred while upgrading from package 'ni-metauninstaller (23.3.0.49243-0+f91)' to 'ni-metauninstaller (23.5.0.49255-0+f103)'.

Solved!
Go to solution

I am trying to install a package and get this error:

 

An error occurred while upgrading from package 'ni-metauninstaller (23.3.0.49243-0+f91)' to 'ni-metauninstaller (23.5.0.49255-0+f103)'.

Additional error information:
An error occurred while installing the MSI at 'MU\MetaUninstaller.msi'. The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2705.

 

I read an article (located here: Solved: Installation error: ni-metauninstaller (22.0.0.49152-0+f0) - NI Community) and while my error is similar, my error log did not have that same code? I have attached my error log for reference.

0 Kudos
Message 1 of 5
(2,454 Views)
Solution
Accepted by topic author LearningLabVIEW

Thanks for proactively sharing the NIPkgLog files. The error that you are seeing is a failure of the MSI being installed and can occur when security software is interfering/blocking the MSI from installing. Enabling and sharing the generated MSI logs for this error would be helpful, see Generating and Locating NI Package Manager Error Logs.

 

I have seen this error recently reported by two other customers that were using BeyondTrust for system security. It might also be possible to see this error if you are using Windows 11 with Smart App Control enabled, but the error is typically different. Do you know if your company is using BeyondTrust or some similar software to aggressively protect your systems?

Scott Richardson
https://testeract.com
0 Kudos
Message 2 of 5
(2,425 Views)

Yep.... we are using BeyondTrust

 

My apologies on the late reply, I didnt realize anyone replied to my original post.

0 Kudos
Message 3 of 5
(2,260 Views)

Almost all of NI installers and their packages to date contain MSI files that are not signed. Our previous debugging with a different customer of a similar issue found that BeyondTrust was prevent some unsigned MSI from being installed or the custom actions that the unsigned MSI invokes fail to run and error, and the failure did not always occur. We did manually rebuild the packages with signed MSIs in an installer that failed often for the customer, and the customer could not get BeyondTrust to interfere with its installation.

 

We are beginning to sign MSIs in the packages, and we started with the NI Package Manager and a few select products that released in 2023 Q4. We are looking to sign all MSIs in future releases soon.

 

As of today, we are not planning to go back and rebuild any of our previously released packages and installers, so you will need to work with your IT department to determine how to work with BeyondTrust to prevent it from causing these types of installation error, at least until all the NI software you are using contains signed MSIs.

Scott Richardson
https://testeract.com
0 Kudos
Message 4 of 5
(2,234 Views)

Scott,

 

Thank you for the information. I'll have to chat with them about the issue.

0 Kudos
Message 5 of 5
(2,217 Views)