NI Package Manager (NIPM)

cancel
Showing results for 
Search instead for 
Did you mean: 

NIPM installing and keeping packages twice

Solved!
Go to solution

Hello,

this happens on every machine Windows that uses NIPM, at least in my experience.

NIPM downloads and installs packages twice, reserving twice as much space on precious HDD/SSDs.

 

I am not sure wether these are symbolic links or not, but they reserve memory either way, at least please take a look at this.

 

First dir:

 

Spoiler
C:\ProgramData\National Instruments\NI Package Manager\packages\

 

 

Second dir: 

Spoiler
C:\Users\All Users\National Instruments\NI Package Manager\packages\

Please see the attached images.

image_b.png

image_a.png

  

 

Researcher @ Gdańsk University of Technology
Python enthusiast
0 Kudos
Message 1 of 4
(2,104 Views)
Solution
Accepted by topic author nlhnt

Also for a lot of the NI software, it also has the copies of most of the package contents in the MDF folder (C:\ProgramData\National Instruments\MDF\ProductCache\). You can disable the NIPM caching as mentioned in this Knowledge Article. Personally, I have automated most of our NI install with a batch file that includes a delete of these directories at the end. Only issue would be if the machine does not have internet access and needs to repair; then it might not be able to since the package is not available.

 

 

__________________________________
Bill Eisenhower
Certified LabVIEW & TestStand Developer
Message 2 of 4
(2,072 Views)

Didn't know that was a purposeful action, I will disable the cache.
Thank you for the link! 🙂

Researcher @ Gdańsk University of Technology
Python enthusiast
0 Kudos
Message 3 of 4
(2,064 Views)
Solution
Accepted by topic author nlhnt

@nlhnt wrote:

Hello,

this happens on every machine Windows that uses NIPM, at least in my experience.

NIPM downloads and installs packages twice, reserving twice as much space on precious HDD/SSDs.

 

I am not sure wether these are symbolic links or not, but they reserve memory either way, at least please take a look at this.


Hi,

 

Just to confirm - those two Windows directories are indeed two names for the same folder, so there is only one copy of the packages. However, that KB is accurate in describing that there are two difference caches - one for packages and one for the old .MSI-based installers. That second cache location will be removed in a future release, so the footprint impact will be reduced.

Message 4 of 4
(2,008 Views)