Open CalebKeatts opened 2 months ago
Might be similar to this issue: https://github.com/ramensoftware/windhawk-mods/issues/478. I assume it happens even if no themes or styles are used, right?
Can you capture a crash dump? You should be able to get it with the following steps:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting
LocalDumps
DumpType
with value 2
%LocalAppData%\CrashDumps
folder, you should see a dump file in thereIt does appear to be a similar issue, though this happens (at least to me) more than a few times a week. EDIT removed attachment.
Sorry about that, here's a zip of the crash dump
Thanks, I ended up using PeaZip. There's nothing in the dump that seems related to the mod. If no styles are applied, then my best guess is that it's a Windows problem caused by their implementation of XAML diagnostics, which is a way of receiving events about UI elements, used mainly for debugging.
One way to verify it is to disable the mod, and try one of the following which uses XAML diagnostics too:
Thank you for the feedback and troubleshooting tips. So I tried using UWPSpy (already had installed) and it also caused the crash to occur. Unfortunate as I use virtual dekstops hundreds of times a day, and I'm sure Microsoft won't be bothered fixing a bug none of their "normal" users will encounter.
After using process of elimination, I have determined this mod causes weird behavior with desktop switching. Namely, in some rare (but not rare enough) edge cases, explorer will completely crash when attempting to switch virtual desktops.
Steps to reproduce:
Doing these same steps without Taskbar Styler installed switches desktops as expected.
I have a Surface Pro 10 running Windows 11 23H2 Build 22631.4169