One of the more "challenging" problems with LabVIEW is installing and "repairing" installations. Having worked with LabVIEW systems going back to LabVIEW 7.0, and having struggled to learn the "unwritten Best Practices for Installing and Upgrading LabVIEW systems" as installation media, the installation process, and NIPM have made their appearance on the scene, I can sympathize with your plight.
How recently was LabVIEW 2018 (32-bit or 64-bit?) Professional installed on your PC? Did you install it? Do you have Admin privileges?
Based on my own experience, I rarely attempt to "repair" a LabVIEW installation. This definitely is a "time sink", as it involves unwinding a lot of "connections" between the software being removed and the rest of the LabVIEW system currently installed, making it much faster to do a complete removal of all National Instruments Software and starting a fresh Installation. This, too, can be problematic, particularly if there are multiple versions of LabVIEW installed. The "Good News" is that while doing this means that your existing LabVIEW code is (temporarily) unavailable to you on your own machine (since a VI cannot simply be "viewed" as a text file), it should be living in your User Profile (under "My Documents"), far away from where LabVIEW software is installed.
I'm guessing that if you aborted the Repair process, you will probably have to go the "Remove and Reinstall" route. This is a good time to seek out the most experienced LabVIEW User you can find, particularly someone who has dealt with NIPM and its quirks, and knows how to properly remove all NI Software safely. Whatever you do, do not try to "force-remove" LabVIEW with third-party software -- that is almost guaranteed to lead to a repair whose first steps is (1) Reformat the C: Drive. (2) Reinstall Windows. (3) Reinstall everything else.
Bob Schor
