meh_817
4 discussion posts
After updating from version 10 (i think?) to version 12. The start button on my DF taskbars do not work with a mouse click. If I click on the secondary screen to make it active and then use the keyboard start button, the start menu opens on the main monitor before moving to the active monitor. I have updated to the latest beta but the issue persists.
• Attachment [protected]: DisplayFusionDebugInfo Minimal.zip [102,027 bytes]
• Attachment [protected]: DisplayFusionDebugInfo.zip [90,861 bytes]
rodhanter
3 discussion posts
Hi, I'm not the OP but I'm experiencing the same issue. When I click the Start button on the DisplayFusion taskbar, nothing happens at all.
This started happening after I updated the Start Menu to use categories. Here's what I've noticed: if I'm focused on a window on another monitor and press the Windows key, the Start Menu opens just fine. But if I click the Start button directly on the DisplayFusion taskbar, nothing happens. The primary monitor's taskbar works perfectly when clicking the button — the issue is only with the DisplayFusion taskbar.
I have a 3-monitor setup. I went through the troubleshooting steps and attached the zip file below. I reproduced the issue at around 10:35 PM UTC (7:35 PM Brasília time).
Any help would be greatly appreciated, thanks!
• Attachment [protected]: DisplayFusionDebugInfo.zip [110,279 bytes]
rodhanter
3 discussion posts
Hi, I analyzed the log with the help of Claude AI and found something relevant. When clicking the Start button on the DF taskbar, the process fails with:
FAIL: windowHandleStartMenu is NULL. [System.Exception]
This happens twice during reproduction. DisplayFusion detects the Start Menu opening but can't grab the window handle in time, so it silently aborts.
The move mechanism itself works fine — pressing the Windows key opens the menu on the primary monitor and DF successfully moves it to the active one. The issue seems isolated to the direct taskbar button click.
My guess is the new categorized Start Menu changed the timing of when the window becomes available. Hope this helps the devs pinpoint the issue!
Could you send me the steps you used to enable Categories for your start menu?
rodhanter
3 discussion posts
Hi! I've attached a screenshot of my Start Menu settings. I didn't actually enable it manually — it was automatically applied after a Windows update. I'm currently on Windows 11 version 25H2, build 26200.7840.
Thanks for looking into this, I really appreciate the support!
• Attachment [protected]: Captura de tela 2026-02-24 070252.png [546,531 bytes]
meh_817
4 discussion posts
I followed the steps and have attached an additional log file.
• Attachment [protected]: DisplayFusionDebugInfo.zip [110,329 bytes]
I tested this here but can't seem to reproduce it. @meh_817 Are you using Categories for your start menu as well?
meh_817
4 discussion posts
I am currently on View: List. I have tried categories and grid, but no success.
Okay strange, we'll do some more testing here and see if we can reproduce it.
meh_817
4 discussion posts
FYI reverting to the older windows start menu seems to be a temporary fix? I have used vivetool to disable the latest windows start menu and it appears to resolve the issue for now. However, any future windows update may break this again.
If you head to C:\Windows\SystemApps\Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy\StartMenuExperienceHost.exe, right click it and head to Properties > Details, what File Version is shown there?
Heath B
2 discussion posts
Same issue starting from latest update, as well. Tried the newest beta and issue still persists.
Replicated the issue twice at 15:13 and 15:14.
StartMenuExperienceHost.exe version is 10.0.26100.7309
• Attachment [protected]: DisplayFusionDebugInfo.zip [95,450 bytes]
I actually had this happen on a different machine that doesn't have DisplayFusion installed, after updating to 25H2 26200.8037. If you exit DisplayFusion, does the make any difference?
