09-16-2021 04:03 PM
Hello, hello,
for the past week, the Win10 VM I use for CVI development crashes 5 to 30 minutes after booting. It's caused by NI software. I haven't installed or updated any new NI software in the past 2 years (I use CVI 2019). I know it's caused by NI because:
- if I boot in safe mode, there's no problem
- if I use msconfig to disable all NI services, there's no problem
- I can't start LabWindows 2019 anymore (it shows its start up screen for a minute then disappears)
- LabWindows 2015 running on the same system still works
- I can launch the package manager, but trying to install the version 21 of package manager fails
- also trying to repair anything (like LabWindows) with the package manager fails.
What is weird is that I'm running in a VM, so I went back to a 1-year old snapshot that used to work absolutely fine (for the past year !) and it now has the same problems. So I suspect some shitty online upgrade that was discreetly forced onto me, either by NI or by Microsoft (causing NI to fail).
Anybody has the same issues ?!? ConfigCVILogging.exe didn't give me much info, but I can try again.
09-17-2021 07:33 AM
May there be some event registered in the Windows event log of your VM? You could at lease easily locate those related to the aborted start of CVI 2019: they could shed some light on what's happening.
09-17-2021 07:39 AM
Thanks Roberto, I'll keep it in mind. I use Windows so little nowadays that I even forgot how to debug system issues. I've disabled all NI services and so far so good. I'll re-enable little by little depending on needs.