You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After explorer crashed, the icon does not reappear in the taskbar and the awake functionality is not turned on, while it's set to on in the PowerToys settings.
✔️ Expected Behavior
Should reopen Awake and keep computer awake.
❌ Actual Behavior
not reopening and not keeping computer awake.
Other Software
None
The text was updated successfully, but these errors were encountered:
#21351 is closed, but the problem remains. #34275 is similar, however I have problems after explorer crashed and restarted, not after waking up from sleep. Also the taskbar icon in my case disappeared.
@seanmamasde can you tell me more about how explorer crashed? Was it on boot, during some other app operation, or while you were changing specific PowerToys settings?
dend
added
Product-Awake
Issues regarding the PowerToys Awake utility
and removed
Needs-Triage
For issues raised to be triaged and prioritized by internal Microsoft teams
labels
Sep 8, 2024
No explorer crashing isn't because of PowerToys, it's me doing some other things and find it become unresponsive so I force it to quit using taskmgr and restarted using run explorer.exe. That said the Awake should still re-hook(?) onto the explorer process? I don't know how it worked under the hood, I just observed that it's no longer effective or even turned on after explorer restart. Hope this helps.
Microsoft PowerToys version
0.84.0
Installation method
PowerToys auto-update
Running as admin
No
Area(s) with issue?
Awake
Steps to reproduce
After explorer crashed, the icon does not reappear in the taskbar and the awake functionality is not turned on, while it's set to on in the PowerToys settings.
✔️ Expected Behavior
Should reopen Awake and keep computer awake.
❌ Actual Behavior
not reopening and not keeping computer awake.
Other Software
None
The text was updated successfully, but these errors were encountered: