Sadly, NIPM is not "robust", and will frequently cause installation errors, including with the last two LabVIEW releases. A decade and a half ago, when LabVIEW was much simpler, installation issues, often involving starting necessary LabVIEW Services could occasionally creep in, but since LabVIEW 2017 and NIPM, they have become far more frequent.
I notice you have a lot of Services installed, including some I've never encountered. I wonder if you are "installing too much" and overwhelming NIPM.
Can you please provide some additional information:
- How many (and what, both in Year and in Bits) LabVIEW Versions are installed?
- What additional Modules and Toolkits (found on the first page of the NIPM Installation) are you using?
- What Drivers (other than DAQmx, GPIB/IEEE 488, and VISA) are you using?
For what it is worth, I usually install LabVIEW in multiple passes. Where it is difficult or problematic, I also try to install on a machine with no other NI software installed, for example, by spinning up a VM that doesn't (yet) have LabVIEW. You want your test system to have only a single "edition" installed.
On the first pass, install only LabVIEW. No Drivers, no Addition Features (or whatever term VIPM uses). Reboot.
Second pass, add the minimum-required Modules and Toolkits, again no drivers (NIPM will probably ignore some of these choices and add, say, VISA, without asking). Be judicious in your Additional Features (I usually add Report Generation Toolkit, as I do use it). Reboot.
Final pass, add the minimum-necessary Drivers. Add the Additional Features that are appropriate for you situation (but skip things you won't use -- I skip .NET, for example). Reboot.
If you get through all this without NIPM suggesting you have Internet issues (don't ask me why this "excuse" is attached to every NIPM failure I've seen, and is almost always a Service that didn't get installed or started), see if you can open and configure LabVIEW. Prepare to spend quite a bit of time on this (possibly > 1 hour).
Bob Schor
