-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
Keep awake indefinetly not work #34487
Comments
We've found some similar issues:
If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.
|
Can you please provide more details - is the laptop on a specific power mode that is custom? Run |
Here’s the output of powercfg /requests:
C:\Windows\System32>powercfg /requests
DISPLAY:
[PROCESS] \Device\HarddiskVolume3\Users\artur\AppData\Local\PowerToys\PowerToys.Awake.exe
SYSTEM:
[PROCESS] \Device\HarddiskVolume3\Users\artur\AppData\Local\PowerToys\PowerToys.Awake.exe
[SERVICE] \Device\HarddiskVolume3\Windows\System32\svchost.exe (Schedule)
Windows will execute '\HP\HP Print Scan Doctor\Printer Health Monitor' scheduled task that requested waking the computer.
AWAYMODE:
None.
EXECUTION:
None.
PERFBOOST:
None.
ACTIVELOCKSCREEN:
None.
Like others had posted. I turned on “Keep screen on” and it seems to make it stay awake:
But that’s still a bug since it should be able to “Keep awake indefinitely” without “Keep screen on”, right?
|
Notice this part:
This means that Awake has requested a system hold. Can you run the same command without the screen on option and see what the output is? |
Here’s the run with Screen On turned off:
DISPLAY:
None.
SYSTEM:
[PROCESS] \Device\HarddiskVolume3\Users\artur\AppData\Local\PowerToys\PowerToys.Awake.exe
[SERVICE] \Device\HarddiskVolume3\Windows\System32\svchost.exe (Schedule)
Windows will execute '\HP\HP Print Scan Doctor\Printer Health Monitor' scheduled task that requested waking the computer.
AWAYMODE:
None.
EXECUTION:
None.
PERFBOOST:
[DRIVER] Legacy Kernel Caller
Power Manager
ACTIVELOCKSCREEN:
None.
That said, even with Keep Screen On, it’s still going to sleep sometimes, so not necessarily the fix I thought – still doesn’t work.
|
I suspect that something else entirely is interfering with the Awake behavior - it has successfully requested the |
Here’s the output with VLC running and Awake off:
DISPLAY:
[PROCESS] \Device\HarddiskVolume3\Program Files\VideoLAN\VLC\vlc.exe
SYSTEM:
[DRIVER] Realtek High Definition Audio (INTELAUDIO\FUNC_01&VEN_10EC&DEV_0294&SUBSYS_104316A3&REV_1000\5&211ffee4&0&0001)
An audio stream is currently in use.
[PROCESS] \Device\HarddiskVolume3\Program Files\VideoLAN\VLC\vlc.exe
AWAYMODE:
None.
EXECUTION:
None.
PERFBOOST:
None.
ACTIVELOCKSCREEN:
None.
|
@Obelix25860 and does the laptop go to sleep with VLC running? |
Obelix25860
commented
Sep 10, 2024
via email
•
edited by microsoft-github-policy-service
bot
Loading
edited by microsoft-github-policy-service
bot
No the laptop stayed on. I left a video looping on VLC, with Awake turned off, overnight and the laptop remained on. Here’s the powercfg /requests output:
C:\Windows\System32>powercfg /requests
DISPLAY:
[PROCESS] \Device\HarddiskVolume3\Program Files\VideoLAN\VLC\vlc.exe
SYSTEM:
[DRIVER] Realtek High Definition Audio (INTELAUDIO\FUNC_01&VEN_10EC&DEV_0294&SUBSYS_104316A3&REV_1000\5&211ffee4&0&0001)
An audio stream is currently in use.
[PROCESS] \Device\HarddiskVolume3\Program Files\VideoLAN\VLC\vlc.exe
AWAYMODE:
None.
EXECUTION:
None.
PERFBOOST:
None.
ACTIVELOCKSCREEN:
None.
|
I just realized my new Windows 11 Machine with Awake indefinitely is going to sleep also. |
Let's consolidate the discussion in #32005 - seems like the same problem |
Microsoft PowerToys version
0.83.0
Installation method
Microsoft Store
Running as admin
Yes
Area(s) with issue?
Awake
Steps to reproduce
I set awake for indefinite. Laptop goes to sleep.
✔️ Expected Behavior
Laptop stays awake idefinitely
❌ Actual Behavior
Laptop goes to sleep
Other Software
Bug Report
PowerToysReport_2024-08-29-15-03-39.zip
No response
The text was updated successfully, but these errors were encountered: