Intermittent windows snap bug

Windows 11 and Start11 in Windows 10 mode

from Stardock Forums

Has anyone else experienced intermittent issues with the window snap key function (e.g., <win>-<right arrow>) not working on specific monitors in a multi-monitor setup?  I have found that restarting the Windows Explorer app fixes the issue temporarily, but it recurs later.  Not sure if this relates to waking from sleep/hibernation.

Moved Start Menu Products area

stardock software start menu products
307 views 7 replies
Reply #1 from Stardock Forums Top

Hello,
I have forwarded your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience. Thank you.

Basj,
Stardock Community Assistant

Reply #2 from Stardock Forums Top

I've seen no follow up to this thread.  

To restate the issue with more specifics, it appears that with my current configuration of Start11 ver. 2.71 Business edition in Windows 10 mode, running in Window 11 version 24H2 (OS Build 26100.8037), that any time the screen configuration changes, the windows snap hot-key function (<Windows>+<left or right arrow key>) ceases to work on at least one of the screens.  This appears to occur if you change the display configuration (such as by docking/undocking) or if the machine sleeps or hibernates.  To restore function, it is necessary to right-click Windows Explorer within the Task Manager and select restart. I am also using Fences ver. 6.46 on this computer, though I see no evidence Fences has any relation to the issue.

TouchTasks - Access tasks with ease on Windows touchscreens.
Reply #3 from Stardock Forums Top
Quoting mibrown769, reply 3993720

I've seen no follow up to this thread.  

 

To restate the issue with more specifics, it appears that with my current configuration of Start11 ver. 2.71 Business edition in Windows 10 mode, running in Window 11 version 24H2 (OS Build 26100.8037), that any time the screen configuration changes, the windows snap hot-key function (<Windows>+<left or right arrow key>) ceases to work on at least one of the screens.  This appears to occur if you change the display configuration (such as by docking/undocking) or if the machine sleeps or hibernates.  To restore function, it is necessary to right-click Windows Explorer within the Task Manager and select restart. I am also using Fences ver. 6.46 on this computer, though I see no evidence Fences has any relation to the issue.

End of mibrown769's quote

Is there any reason you think Start11 is the cause of this as thats not a feature we provide, thats a feature of Windows itself.

Reply #4 from Stardock Forums Top

The issue did not appear before I installed and started using Start11.  I suppose I could uninstall Start11 to test the theory.

Reply #5 from Stardock Forums Top

Over the past hour I uninstalled Start11 and performed a series of test sleep, hibernation, and docking/undocking scenarios but was unable to replicate the issue.  I have now reinstalled the app.  We will see if the issue recurs.

Reply #6 from Stardock Forums Top

If it continues I would recommend installing the 2.72 beta just in case that helps.

Reply #7 from Stardock Forums Top

I have continued to see the issue, but I also did a little more querying.  It seems this may be a general issue with Windows 11 losing track of the screen configurations, particularly with multi-screen DisplayPort connections, and is not necessarily related to Start11 (though I had not observed it before that... odd coincidence?).  

A quick fix that seems to work reliably is to reset the graphics subsystem via the key combination <ctrl><shift><win><b>.  When this key combination is input, the PC will beep and the screen(s) will briefly go black and then come back up. It takes less than 5 seconds. It does not seem to disrupt any active apps, but the snap functionality is restored.  This is preferable to restarting Windows Explorer and having to re-open any folders one may be working on.

Thanks for the patience and support.  Hopefully this answer may help someone else down the road.