I'm going to buy Fences v6. Didn't know v3 was outdated.
1. First Start11 crashes and doesnt respond
2. (file) Explorer works fine
3. Agressive clicking on start11 triggers restart
4. explorer.exe starts and the normal taskbar shows (at the bottom)
5. 10 sec later start11 restarts and the top taskbar is back and functional
This all takes +/- 1 minute
So Start11 makes explorer restart. not the other way around
Start11 is in the explorer process. Anything in that going wrong will stop Start11 working and the taskbar is still the Windows taskbar. We simply add to it. Clicking on a not responding window will eventually make it restart as you have seen but it just tells you the primary thread in explorer stopped working.
Your file explorer windows may be set to run in a separate process depending on your Windows settings too.
My advice would be remove Fences 3.x as thats very much not designed for Windows 11. See if the issue continues. I would also watch out for user profile corruption causing this. We have no other reports of anything like this which strongly suggests Start11 isn't the root cause of the issue here, it could be something it does triggers a windows setting sync which then runs into a problem due to corrupted data somewhere in your user account though.
Having just checked one further thing there is also one conclusive bit of proof that this dmp has nothing to do with Start11. The Start10_64.dll file isn't actually loaded up in that crash dmp. I assume it is from before Start11 starts up on a restart.
