NI Package Manager (NIPM)

Showing results for 
Search instead for 
Did you mean: 

NI Package Manager on offline machine stuck on loading screen

Go to solution



when trying to open the NI Package Manager on a machine that is connected to a local network which does not have access to the internet, it gets stuck on the loading screen and never finishes booting.


Apparently this is related to the Package Manager trying to load some information from which it cannot access and apparently a timeout "never" (maybe after 30+ minutes it would?) kicks in.


I have browsed the forums and NI help, but the solutions either do not work in my case or are not applicable:


We install the Package Manager on a larger number of machines worldwide and cannot expect every user to go through series of steps manually in order to simply open up the Package Manager.


I am looking for a way to programmatically stop the Package Manager from trying to access any online data or to set the timeout for this attempt to e.g. 1s so the Package Manager opens up in an acceptable amount of time.


Any help is appreciated.





0 Kudos
Message 1 of 10

Hi Stefan,


Just to validate the root cause (and not a solution of course), with a machine in this state, if you unplug its network and\or close all wireless connections - then does NIPM start normally?

0 Kudos
Message 2 of 10

I would not call it normally but it does start, yes.

An error message will pop up telling something like Unable to update feeds (I cannot reproduce it at the moment) and after pressing ok the NI Package Manager will open up.

0 Kudos
Message 3 of 10
Accepted by topic author kghzvi

A single switch to shut off access is near the top of my personal wishlist, but it sadly doesn't exist today. There are two main things that need to happen to ensure a fast launch in a network environment like this.


First, unregister all feeds pointing at This PowerShell script will do that (needs to be run as admin):

# Look up nipkg path
$nipkgExe = Get-ItemPropertyValue -Path "HKLM:\Software\National Instruments\NI Package Manager\CurrentVersion" -Name "CLIExecutableFullPath"
# Remove main feed if registered
$mainFeedInstalled = & $nipkgExe list-installed ni-package-manager-released-feed
if ($mainFeedInstalled) { & $nipkgExe remove ni-package-manager-released-feed -y --force-essential }
# Remove all other feeds
& $nipkgExe feed-list | ?{$_ -match "https?://"} | %{($_ -split "`t")[0]} | %{& $nipkgExe feed-remove "$_"}


Second, disable access to the Browse Products tab. The only method for doing that today outside of opening the application and modifying the setting via the UI is to replace the NIPackageManager.exe.config file in the Package Manager install directory with one that pre-disables the setting. Such a file is attached.

Message 4 of 10

Hi Jonathan,


thanks alot for the detailed explanation!


We will test your solution in our environment and give feedback if it worked as expected.

0 Kudos
Message 5 of 10

The solution worked all fine in our environment during the tests and should be implementable in our custom installer.



However I am not quite sure I understand the solution 100%.

Why do we remove all of the feeds and disable the BrowseProducts in that ini file?

Shouldn't the later be sufficient?


Or in other words, if someone manually installs some tool using an offline installer (and thereby adds feeds again?), will that possibly cause the issue to reappear and that powershell script needs to be executed again?



0 Kudos
Message 6 of 10

When Package Manager launches, it initiates two network-based operations that have to complete before the splash screen will close. First, it fetches a current copy of each of the registered feeds and second, it initializes the web API that powers the Browse Products tab (and a couple other less user-visible services).


Those two operations run entirely independent of one another, so that's why there are two steps in order to disable them. (and why one killswitch to rule them all would be helpful)


With the Browse Products tab enabled, the only way to get new product feeds registered is if you install them using an online installer or if you register them manually. Running an offline installer should not result in any new feeds being registered when the Browse Products tab is disabled.


However, upgrading to a new version of Package Manager (via any method) will result in the Package Manager main feed being re-registered and will overwrite NIPackageManager.exe.config, so these steps will need to be re-run any time Package Manager itself gets upgraded.

Message 7 of 10

Thank you so much for taking your time with the explanation.


That should be an expedient (even if not that pretty) solution for us.

0 Kudos
Message 8 of 10
Accepted by topic author kghzvi

Related: NI Package Manager 21.3 now caches a list of domains that are not accessible, including timeout errors, and will not attempt to connect to its feeds for the duration of the process. This should partially mitigate the issue reported in this post.


Reference: Bug "1512240" in Package Manager 21.3 Bug Fixes.

Scott Richardson
National Instruments
Message 9 of 10

Hello Mr. Richardson,


thanks for taking your time to refer to the Bug Fixes of the new Package Manager version 21.3 in this forum post.


We will make sure to include the new version of the Package Manager once we update our custom installer.

0 Kudos
Message 10 of 10