microsoft / microsoft/PowerToys
Desktop right-click hangs after S3 sleep/wake; shell frozen and restarted by winlogon (Event 1002), recurring since May — suspect context-menu extensions
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 139k
- Forks
- 8.6k
- PR merge metrics
- PR metrics pending
Description
Microsoft PowerToys version
0.100.2.0 (per-user install, PowerToysUserSetup-0.100.2-x64.msi)
Installation method
GitHub release (per-user MSI)
Running as admin
No
Area(s) with issue?
PowerRename / Image Resizer / New+ (context-menu extensions) — General
Steps to reproduce
- Let the PC enter standby (S3 sleep) for a while (e.g. overnight).
- Wake it up and unlock the session.
- Right-click on the desktop (or on a file/folder) shortly after waking.
- The context menu never appears; the desktop becomes unresponsive (mouse cursor moves, but nothing reacts).
Ctrl+Alt+Delalso appears to do nothing for a while. - After ~1–2 minutes the screen goes black and the shell is restarted — the system then works again. No reboot, no bugcheck, no GPU TDR occurs.
✔️ Expected Behavior
Right-click should show the context menu normally right after waking from standby.
❌ Actual Behavior
The desktop right-click hangs the shell. Windows Event Log shows Winlogon event 1002 "The shell stopped unexpectedly, userinit.exe was restarted" — i.e. explorer.exe was killed/restarted by winlogon, which produces the black-screen-then-recovery the user observes.
This has been recurring since May 2026. Winlogon 1002 shell-restart timestamps (local time UTC+8):
2026-05-15 09:46, 2026-05-21 15:10, 2026-06-10 15:13, 2026-06-15 19:34, 2026-07-29 20:49, 2026-08-03 14:49, 2026-08-11 00:07, 2026-08-12 01:47, 2026-08-14 11:56.
Event-log evidence
Incident on 2026-08-14 (the reported hang): S3 resume at 11:54:24 (Kernel-Power 130/131/566, resume OK in ~2 s), session unlock 11:54:52, then explorer hung silently (no WER event for explorer) and winlogon restarted the shell at 11:56:46 (Winlogon 1002). No crash dumps, no Kernel-Power 41, no Event 4101 TDR — purely a user-mode shell hang.
Incident on 2026-08-11 00:06:56 — the smoking gun linking PowerToys to a shell restart: dllhost.exe (COM surrogate) hung while hosting the PowerRename context-menu package, and the shell was restarted 31 seconds later:
Event 1002, source "Application Hang", 2026-08-11 00:06:56
AppName: dllhost.exe AppVersion: 10.0.26100.8737
PackageFullName: Microsoft.PowerToys.PowerRenameContextMenu_0.95.0.0_neutral__8wekyb3d8bbwe
PackageRelativeAppId: Microsoft.PowerToys.PowerRenameContextMenu
HangType: Quiesce
ReportId: b758e46b-3e17-4243-b792-26fcbbd6edce
WER (MoAppHang) details: Hang Signature 463a, Hang Type 2097152, Additional Hang Signature 1 463ab4001f9121355b21380e17e19dea — the exact same signature as issue #40391 (dllhost hang while updating PowerToys; this instance happened during the 0.95.0 → 0.100.2 upgrade, MSI transaction 23:59 → 00:08). WER report: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppHang_Microsoft.PowerT_ea133dc06fc1267b7f5b1475a6c2693c7e5fb0d_e9d9afd9_0e6a0073-4a91-4464-b14b-e4823cf6735a.
Right after the upgrade, PowerToys.Settings.exe crashed twice (00:11:42): 0xc000027b in Microsoft.UI.Xaml.dll 3.2.0.0, WER APPCRASH with faulting module combase.dll (0x80004003, offset 0x9cfc4), Report ID e3b18e0e-9ea7-4fc8-807f-fa2c5ffceb7d.
Currently installed context-menu packages (0.100.2.0):
Microsoft.PowerToys.PowerRenameContextMenuMicrosoft.PowerToys.ImageResizerContextMenuMicrosoft.PowerToys.NewPlusContextMenuMicrosoft.PowerToys.SparseApp
Additional Information / hypothesis
- The hangs cluster around post-S3-resume, i.e. in the window where shell extensions, COM/DCOM and driver stacks are re-initializing. If a context-menu handler performs any synchronous COM/network/device work while building the menu, a wedged handler can block explorer's UI thread — and since the desktop menu is built synchronously by explorer, the whole shell appears dead (including
Ctrl+Alt+Delappearing unresponsive because DWM rendering is stalled). - Other software that also errors on resume: VirtualBox 7.2.12
VBoxNetLwffilter driver logs "internal driver error" nearly every wake (21 errors in 14 days) — noted as a possible co-factor, but it alone does not hang the desktop. - Hardware: Windows 11 Home 24H2 (build 26100, zh-CN), NVIDIA RTX 5070 Ti Laptop GPU (driver 32.0.16.1074), Intel chipset/audio DSP.
- Related issues: #40391 (dllhost hang while updating — same WER signature), #33844 (invoking context menu hangs explorer, closed).
Request: could the WinUI context-menu extensions (PowerRename / Image Resizer / New+) hang explorer during the post-resume window? Any planned hardening (timeouts, out-of-proc hosting with hang detection, or deferring initialization until the shell is idle) would help. Happy to provide the WER .etl/.wer files or run a PowerToys report if useful.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, or entry point is named. Start by reproducing the post-S3 right-click hang and reviewing the cited Winlogon, Application Hang, and WER records for the PowerRename context-menu package; done means identifying the responsible extension and defining a verified fix or confirmed non-PowerToys cause.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100