‎10-21-2020 11:18 AM
‎10-21-2020 01:30 PM
Not that this directly helps you, but I've never seen that happen. Right now I have 14, 16, 17, 18, 19, 20 all installed, in that order. I can start any one of them without issue.
So something out of the ordinary is happening in your situation.
‎10-21-2020 02:37 PM
I figured so... I uninstalled and reinstalled it without success. I'm just going to start fresh.
‎10-24-2020 10:42 AM
For what it is worth, until LabVIEW 2019 came out, I had no trouble having multiple versions of LabVIEW installed on my PCs. I called my installation "Triple LabVIEW", as it consisted of LabVIEW 2016, 2017, and 2018. My installation consisted of LabVIEW Professional, Real-Time Toolkit, LabVIEW Vision Development Module, and Drivers, including DAQmx, VISA, Vision Acquisition Software, and PXI Something-or-other. I installed in "chronological order", namely 2016 first, then 2017, then 2018. If I needed to reinstall, I always did a complete uninstall of all NI Software (using Control Panel only), and would sometimes delete the NI folders in Program Files, Program Files (x86), and Program Data. I would also (usually) uninstall JKI, IVI, and VISA software.
When LabVIEW 2019 came out, this process failed totally. After 4-5 months of trying, with help from NI Technical Support, my Support Engineer suggested I install in "Reverse Chronological Order", i.e. 2019, 2018, 2017, and 2016. I laughed, and tried "one 'mo time" in (what I thought was) the "correct" order. Then I, again, uninstalled, and installed 2019 (LabVIEW only, no Toolkits, Modules, or Device Drivers). Success. Installed LabVIEW 2018 (only). Success. Installed LabVIEW 2017 only. Success. Installed LabVIEW 2016 only. Success. Installed 2019 RTM. Installed 2018 RTM. etc. Repeated for VDM (which, as I recall, back-installed for 2018, 2017, and maybe even 2016). Installed Drivers. And ... I now have Quad LabVIEW on my Personal Laptop.
At Work, I also built Quad machines successfully. However, it was a sufficient hassle when "something inevitably goes wrong" that I'm now running them as "2019 Only" systems. Needless to say, I have not installed LabVIEW 2020 (except on a VM, mainly for Testing purposes and to help out on the LabVIEW Forums).
Bob Schor
‎10-26-2020 10:34 AM
Update: I discovered that whoever had installed some of the previous versions of LabVIEW (2015/2016/2017) had installed them to the D:\ drive rather than the C:\ drive. When I installed the newer versions, they went to the C:\ drive (as I incorrectly assumed all the others had). I'm positive that having shared components splintered all over the place was the cause of the issues so I completely wiped the PC clean of NI products and started from scratch.
So far so good.