VLM 3.2 leaves package cache duplicate after creation of VLM installer

[Mads]

When creating a VLM installer of LV2019 in VLM 3.2, a second copy of everything is also made to C:\ProgramData\National Instruments\NI Package Manager\packages, wasting 20 GB of disk space. This should not be done, but can it at least be deleted (the files are in the VLM installer anyway)?

The effect of this is twofold; if VLM reads the original installer from a networked drive, and the destination for the VLM installer is another network drive, you still need to be able to store the full installation on the local c-drive...(this caused the process to fail in my case until I could expand the c-drive). Quite inefficient, but OK. It should be deleted afterwards though(!).

[CL_eisenwr]

This is also case of installing via NIPM or a NI Package Builder built installer. Also there is the copies of the installers in <ProgramData>\National Instruments\MDF\ProductCache. You could make NI Package that would delete the folder contents. There apparently is INI file key to have NIPM not cache (https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019KdtSAE&l=en-US), but I am not sure if/how you would use that during a fresh installation of the tool set.

We should have an option to disable the caching for the VLM installations.