Indeed, should have checked the path in the .txt beforehand 
But itâs weird, 3.2.3 usually runs rock solid for me, didnât experience any crash with 3.2.3 so far, but had several crashes with 3.2.4 (4 in one session).
Anyway, Iâll try to grab another one. Unfortunately, those only seem to happen when actually controlling, so itâs always a PITA when they happen 
Hi Gergely,
Myself and other controllers in VATĂ©ir on the new 3.2.4 version have experienced seemingly random crashes on almost every controlling session. The faulting module is always ucrtbase.dll (This even happens when logged on as an OBS and not actively interacting with the client)
I also found that one of our aliases causes ES to crash instantly and consistently. Again, the faulting module is ucrtbase.dll.
Hereâs the specific alias if you want to try to reproduce it:
.b3 .msg $aircraft Hello, as per section B3 of the VATSIM Code of Conduct, pilots are not permitted to leave their connection unattended. If it becomes necessary to do so, you are encouraged to disconnect from the network for the duration of your absence. Failure to do this may result in disciplinary action.
sorry for the joke, but thatâs an awesome uno reverse card, you warn a pilot, and you get the crash 
Thank you for the example. I like the bugs (even if they are crashes) that are so easy to reproduce. And that way easy to fix.
And more importantly this bug was about aligning the message line if a message were longer than the space there. This way it could happen anytime in your sessions.
Can we expect a quick update of the found critical bugs then? 
Any known issues with this version and Sweatbox?
Just had the following happen to a student:
Attempt to connect to sweatbox with facility Tower and rating S1 (user is currently an OBS) resulted in âRequested level too highâ.
Still on Sweatbox, try to change facility to OBS, rating to OBS, callsign to _OBS resulted in âInvalid cid/passwordâ.
Restart Euroscope and try again (same profile, so same CID/Password), connected just fine as OBS.
Go back to facility Tower and Rating S1, now results in âInvalid cid/passwordâ, without touching the CID and Password fields.
Revert back to 3.2.3, same profile as before, working as expected.
User was sharing his screen on discord, so I know he did not change his CID/Password during attempts. Wondering if maybe thereâs some issue cleaning up the auth tokens if you get disconnected from the server, and/or some issue with sweatbox when connecting with a higher rating
The authentication has changed in v3.2.4 to a different protocol.
On SweatBox I also received âInvalid cid/passwordâ many times. The conclusion was that the clock in SweatBox was far too different and because of that the generated token was not accepted.
If we find too many such problems we have to check if server clock is ok or not.
Yes. I already have 4 internal updates to VACCHUN. They did excellent job in testing new versions. Now it seems that the last version is stable enough for a public release. I will do an MSI today or tomorrow.