HeidiSQL doesn't fully start up after latest Windows 11 update last week

Hi,

we are three colleagues who can't start up HeidiSQL (12.6.0.6765, eg. download today) any more after the latest Windows 11 update last week. Heidi starts, the cursor turns and then dies quickly and quietly. We can connect to the MySQL server via command line just fine and there haven't been any changes associated with the server.

It very much looks like a operating system/Heidi incompatibility or a problem arising from an institution setting associated with the update.

Did anyone else recently have a similar problem, that is, is this some incompatibility between Heidi and the latest Windows 11 update? Or is it just us and strongly suggests an institutional setting gone astray with the newest Windows update?

We would very much appreciate feedback that allows us to clarify where to start with the troubleshooting.

Thanks a lot!

I would watch out for error messages in your Windows event log.

Hi Ansgar,

Thanks a lot for pointing me to the Event Viewer. Below is the entry in the error log. It seems to be an ntdll.dll problem - unfortunately this doesn't tell me if the problem is on our side or not.

Thanks!

Faulting application name: heidisql.exe, version: 12.6.0.6765, time stamp: 0x654778d2
Faulting module name: ntdll.dll, version: 10.0.22621.3374, time stamp: 0xeae8eecc
Exception code: 0xc0000409
Fault offset: 0x000000000008ebdf
Faulting process ID: 0x0x7AF8
Faulting application start time: 0x0x1DA96487F1C203E
Faulting application path: C:\Program Files\HeidiSQL\heidisql.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report ID: f326704d-1ccf-4579-aeb3-17f4dac4dad5
Faulting package full name: 
Faulting package-relative application ID:

First time I see such an error. Yes, probably related to the Windows updates, but I have no clue.

You could try out a newer nightly build and see if that helps: https://www.heidisql.com/installers/HeidiSQL_12.6.0.6831_Setup.exe

The nightly build provided no success. I will forward the error log message to our IT and see if they can relate the error to something specific.

Thank you very much for having looked into this!