HeidiSQL is running but not visible

I have been running HeidiSQL Ver. 10.1.0.5464 since yesterday. When I start the program, it will appear in the Task Manager, but no user front-end will appear. There is also no startup screen showing the selection of databases to work with. There is no error message.

Does anyone have any idea why this might be?

and you don't have some kind of dual monitor setup right?

Yes, I work with two monitors in parallel. And Heidi.SQL is not displayed on any of the monitors.

have you tried using only one monitor (restart to be sure) then launch HeidiSQL again?

If I only work with the laptop display, Heidi.SQL will be displayed. I immediately updated to verse 10.1.0.5555. Now at least the program is started so that I can work with it.

A pity, I was happy too early. When restarting I get an error message: "exception class: EAccessViolation exception message: Access violation at address 0000000000917E29 in module 'heidisql.exe'. Read of address 000000000000000F. " The file bugreport.txt is attached as an attachment.

But the workaround works: the program starts with only one monitor.

Oh my god, a new window dimension/screen/position bug. I was just on the way to change the logic for restoring the position, but when testing that I realized that's a really bad idea.

The best you can do is to exit HeidiSQL, start regedit.exe and reset some values to their originals:

• go to HKEY_CURRENT_USER\Software\HeidiSQL
• delete all values starting with "MainWin", as shown in the attached image
• restart HeidiSQL and hope to see it

Thanks for the tip! It worked for me (I had the same problem)

Thanks. I have the same issue, even with the lastest version. Deleting the MainWin fixes that. 👍

Awesome, thanks for that, I use 3 monitors and regularly connect to my machine over RDP etc. Just been foxed by this for a while, tried downgrading from latest version etc. Couldn't understand why the heidisql process was running after I'd tried to connect, but I couldn't see it or get to it. Deleting the MainWin keys fixed it.

Thx...