@Yamaeda wrote: That's only true for the latest NIPM, as it mentions 2019 i'd assume it was installed before NIPM had VIPM included.
Agreed. I missed the only hidden version clue that was in the popup text and I assumed that this was a very recent installation (maybe for a student course) followed by a quick decision that LabVIEW is not really what they want. In that scenario, it might have even been possible to roll back the OS.
Many details are missing. They did the uninstallation "by the book" using the "uninstaller supplied by NI" as quoted, but I am not aware of any such book and what uninstaller that could possibly be. 😄 Later they manually chopped through the registry and file system, so all bets are now off. Just looking at that popup, the term "VIPM" and "service" would have given strong clues where to look and the statement that the runtime engine could not be located was a clear indication that NI software was already gone.
Still, 4 hours seems quite long for "LabVIEW" unless there were tons of additional modules, drivers, and toolkits. This must have been are relatively low powered system with a conventional HD (no SSD) that was probably quite full and fragmented. 😄
As I said previously, I did use NIPM to uninstall Labview. 4 hours later, I thought Labview was uninstalled. However, there were Labview and NI bits and pieces all through my PC and the registry. So, I went on an NI search and destroy mission and removed anything I could find that referred to Labview, NI or National Instruments.
But, I still got the annoying error message, so I reached out to this forum and learned that there is another program, a VI package manager program, that I was unaware of. After removing that, the problem went away.
So, if some time in the future, I want to re-install Labview on my home PC, I'll find out if I screwed-up or not.