LabView often crashes on startup without error

[Kyle97330]

The part about "faulting module path" mentions a "mgcore" DLL, which appears to be a memory management DLL.

I see very few online references to it.  One is here:

https://lavag.org/topic/17810-memory-deallocation-bug/page/2/

That post makes it sound like all 4 of those provide the same functionality with different options, and that by renaming the default one to something else and then one of the others to the default one you can change which one it uses.  No idea if that would help, but you could try it...

[Greenas]

I want to give a small update.
I checked for file integrity of labview, it seems like everything is okay.
However, a few days ago I installed the same labview setup on a different machine and I experience the same problem.
Although there is this error in the windows event viewer, I think that my problem could also be connected to the license server I am using.
I will give an update if I find something out.
PS: I also want to try to rename this library which is connected to the error as someone suggested. However, in the last two days, Labview started without a problem...

[Greenas]

Okay, I think I might have found the problem... (not 100% sure but around 95%)
What I never told because I thought that it is not important is that I always remote control my windows machine.
I use xfreeRDP for that as it is fast. Now I noticed that if I use noVCN (which is a bit laggy) I can always start LabView and if I then switch to RDP it sometimes shuts down.
I think that with RDP I probably block the port of the machine which is important to reach the LabView license server.
So sometimes it will probably go through and sometimes not.
By now I don't know how exactly that is linked to the error message, but I assume there is a link.

Thank you for all your help 🙂
Now I will try to use another port for RDP (lets see how I can do this).