Showing results for 
Search instead for 
Did you mean: 

Updating Labview created application

Matt, the exception code 0xe0434352 is non-specific, so it is likely that the NI Package Manager C# application is throwing a .NET exception very early. Normally there is a .NET Runtime exception that is also logged but we are not seeing that so unclear how far we are getting into the NIPM code.


I would be interested in knowing if C:\Program Files\National Instruments\NI Package Manager\nipkg.exe is working OK. Some commands to try are and maybe share back those results.

  • nipkg.exe show-version
  • nipkg.exe list-installed
  • nipkg.exe feed-list

Next, I would be interested in what your %localappdata%\National Instruments\NI Package Manager\Logs\ directory contains, specifically the more recent dated files like:

  • errorlog.txt
  • agentsErrorLog.txt
  • UnhandledException.log
  • NIPkgLogs\*.txt

Next you could uninstall NI Package Manager and reinstall it. This will not affect any other NI software that is installed. You can do this by going to Add/Remove Programs for the OS and choosing to uninstall NI Package Manager. You will get a warning which you can acknowledge and continue. Then you can run the latest NI Package Manager installer from Once complete, see if NIPM will launch successfully.


Last options would be to start debugging the exception maybe with Fusion, WinDbg, and Visual Studio.

Scott Richardson
National Instruments
Message 11 of 13

Hey Matt, any progress on NI Package Manager not launching? Where you able to try any of the suggestions I had posted?

Scott Richardson
National Instruments
0 Kudos
Message 12 of 13

Hey Scott,


I have some other projects going on and have not gotten a chance to try out this latest response

0 Kudos
Message 13 of 13