-
Notifications
You must be signed in to change notification settings - Fork 6.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MWB service causes monitor to not sleep #26339
Comments
Same problem, turn off MWB service and the screen sleeps normally. |
It appears (at least for me) to not even require that MWB "Service" mode be enabled. Just enabling the MWB feature is enough to prevent monitor sleep. This was never an issue with the standalone MWB install. |
Same issue, it seems like the mouse virtually move or such and caused the monitor to constantly wake up. One way to verify this is by playing video in full screen, the playback control automatically hides, but appears in constant intervals as if mouse moved. |
The 'Block screen saver on other machines' setting seems to be the culprit on my machine. Disabling this allows my laptop to sleep again. |
Yep. That seems to be it!
…________________________________
|
/dup #26339 |
Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report! |
(the actual dup is #26261) |
Microsoft PowerToys version
0.70.0
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
Mouse Without Borders
Steps to reproduce
When I set this new feature to on, my monitors would no longer go into sleep mode. As soon as I turned to off, sleep worked as expected.
✔️ Expected Behavior
Sllep would work as normal
❌ Actual Behavior
Monitors stayed on instead of going into sleep mode
Other Software
Edition Windows 11 Pro
Version 22H2
Installed on 10/5/2022
OS build 22621.1702
Experience Windows Feature Experience Pack 1000.22641.1000.0
The text was updated successfully, but these errors were encountered: