LabVIEW
LabVIEW 2021 SP1 (64 bit) crashes at Startup in Windows 11 Pro
@Ekim wrote:
I have reinstalled LabVIEW 2021 SP1 (64 bit) twice.
LabVIEW 2021 SP1 (32 bit) and all other installed 32 bit LabVIEW versions are working fine.
Also LabVIEW 2020 SP1 (64 bit) and LabVIEW 2019 SP1 (64 bit) have the same issue (a crash of LabVIEW.exe at startup).
LabVIEW 2015 SP1 (64 bit) is however working fine.
It seems your machine has quite a lot of processor cores. And something during initialization of the threads fails. LabVIEW allocates on startup a number of threads per execution system. This number depends on the number of processor cores it detects.
Something in Windows 11 seems to fail when trying to allocate more threads than there are cores. The fact that LabVIEW 2015 seems to work is likely that it used a lower maximum limit of threads to allocate. As stated, LabVIEW 2021 and earlier are not officially supporting Windows 11. It usually works but there are corner cases where something can go wrong and this seems to be one of them.
There is a threadconfig utility in LabVIEW described in this Knowledgebase article. Of course running this while LabVIEW crashes on startup is a bit of a problem. But all that VI basically does is to change entries in your labview.ini file that specifies the number of threads to to startup on launch of LabVIEW and you have to restart LabVIEW after running that utility to make the changes work.
Basically you would add something like this in your LabVIEW.ini file:
ESys.StdNParallel=2This changes globally all execution systems to only allocate 2 threads per priority level.
ESys.StdNParallel=-1
ESys.Bgrnd=2
ESys.Normal=2
ESys.High=2
ESys.VHigh=2
ESys.TCritical=2
ESys.instrument.Bgrnd=2
ESys.instrument.Normal=2
ESys.instrument.High=2
ESys.instrument.VHigh=2
ESys.instrument.TCritical=2
ESys.DAQ.Bgrnd=2
ESys.DAQ.Normal=2
ESys.DAQ.High=2
ESys.DAQ.VHigh=2
ESys.DAQ.TCritical=2
ESys.other1.Bgrnd=2
ESys.other1.Normal=2
ESys.other1.High=2
ESys.other1.VHigh=2
ESys.other1.TCritical=2
ESys.other2.Bgrnd=2
ESys.other2.Normal=2
ESys.other2.High=2
ESys.other2.VHigh=2
ESys.other2.TCritical=2
In this way you can control the number of threads per execution system and priority individually.
What do you mean that that ini file doesn't exist? That is almost impossible. 😀
Although maybe LabVIEW installs indeed without one. The first thing I always do after any installation is going into the Options and disabling some annoying features such as Lock Autotool etc.
You should be able to simply copy the ini file from your 32-bit installation into the 64-bit LabVIEW folder and remove anything that does not relate to the thread configuration and then lets see if it still crashes with less threads.
LabVIEW actually is started up by the OS with one thread active (obviously as it needs to have a thread to do anything) and then generates the execution system threads. So you end up with 301 threads for LabVIEW.
Hmmm, bummer. It seems to crash after the initialization of the threads. There is a lot involved during LabVIEW startup including detecting what kind of CPU it runs on and a lot more such things. Some of that stuff is pretty delicate and there may be something that it tries to do that is now protected in some ways under Windows 11 and simply returns a NULL value if the application tries to do that or is not elevated.
Have you tried to start LabVIEW elevated? (Start as Administrator)
Other possibilities might be to try to play with the startup options for the LabVIEW executable file and try some of the legacy emulation options.
