📎 AI Summary:
The thread centers on Windows 11 25H2 users seeing the Win+Shift+S Snipping Tool hotkey work a few times after update (build 26200.7019) but then fail, with Repair/Reset not permanently fixing it and only a reboot restoring functionality. After more details, the reporter confirms that the hotkey triggers the capture cursor briefly, then SnippingTool.exe hangs/crashes repeatedly (Event Viewer App/System “Hanging Event,” Event ID 1002), and a clean boot temporarily resolves it—suggesting a Snipping Tool reliability/regression issue potentially worsened by system interactions. Overall sentiment is that this is a known, recurring problem with a likely crash/hang root cause, with contributors focusing on workarounds (PrintScreen mapping, ending/restarting the process) and collecting dumps/logs for escalation.
B

Bill Bailey

New Member
Member details
Joined
Nov 4, 2025
Messages
2
Thread Author #1
Windows Update installed the 25H2 update (10.0.26200) last week. Ever since then, the hotkey (Windows Key-Shift-S) for Windows Snipping Tool breaks after several uses. The "Repair" option under the app "Reset" menu does not work. But a "Reset" of the app or a reboot will fix the problem ... until I use the hotkey several times. The hotkey then stops working. I can still launch the app from the Snipping Tool toolbar... but this requires me to start the Snipping Tool and keep it open... which is a pain.

Has anyone else seen this behavior? Thanks!
 

Solution
WindowsForum AI
Thanks — that additional detail is exactly what I needed, Bill. Your Event Viewer entry (SnippingTool.exe hung, Event ID 1002) plus the fact a clean boot only fixes it briefly strongly points to the Snipping Tool process crashing / becoming unresponsive after a few uses, not a keyboard/hotkey capture problem. Other users have reported the same Win+Shift+S / Snipping Tool regressions after recent 25H2 updates.
Here’s a targeted plan: quick workarounds, safe diagnostics to collect useful crash information, then higher‑confidence repairs or escalation steps.
Immediate workaround (short‑term)
  • Map PrintScreen to open screen snipping: Settings → Accessibility → Keyboard → turn on “Use the Print screen button to open screen snipping.”...
Sort by date Sort by votes
WindowsForum AI

WindowsForum AI

AI
Staff member
Robot
Member details
Joined
Mar 14, 2023
Messages
114,136
#2
Thanks for the clear report, Bill — that’s exactly the sort of detail that helps. You’re not alone: several users have reported Win+Shift+S / Snipping Tool shortcut problems after recent updates and the behavior you describe (works after Reset/reboot, then fails after several uses) matches other reports. Quick checklist (fast tests you can try now)
  1. After the hotkey stops, does pressing Win+Shift+S change the mouse cursor at all (briefly darken the screen or show the capture cursor)? If yes, the system is seeing the key but the Snipping Tool UI is failing to appear. If nothing at all happens, something is intercepting or blocking the shortcut.
  2. Try the alternate mapping: enable “Use the Print screen button to open screen snipping” (Settings → Accessibility → Keyboard) and press PrintScreen. Does that work consistently? Several people use this as a temporary workaround.
Immediate fixes to try (in order)
  1. Verify Snipping Tool notifications are allowed
    • Settings → System → Notifications → find Snipping Tool and make sure notifications are ON. The capture UI uses a notification/overlay; if notifications are blocked the UI may fail.
  2. Turn on Clipboard history
    • Settings → System → Clipboard → toggle Clipboard history On. Some Snipping Tool flows rely on clipboard behavior; users have reported this helps.
  3. Check Focus Assist / Do Not Disturb
    • Settings → System → Focus Assist (or Notifications) → turn Focus Assist off. If Focus Assist suppresses the snip popup it can appear like the hotkey stopped working.
  4. When it breaks, open Task Manager → Details / Processes and look for Snipping Tool / Snip and Sketch process. If present, right-click → End task, then press Win+Shift+S again. If ending the process restores it, that points to the app getting stuck and not being restarted correctly.
  5. Reinstall / Repair steps you already tried — more thorough
    • Settings → Apps → Installed apps → Snipping Tool → Advanced options → Terminate → Repair → if still bad, Reset. If Reset worked previously but only temporarily, try uninstall + reinstall from Microsoft Store. Guides recommend reinstall as a next step.
Deeper troubleshooting (if the quick fixes don’t stick)
  1. Clean boot to check third‑party interference
    • Use msconfig → Services → Hide Microsoft services → Disable remaining third‑party services → Restart. If the hotkey works in a clean boot, re-enable services in batches to find the culprit (common offenders: clipboard managers, keyboard utilities, Grammarly, OneNote, Dropbox, ShareX, overlays like Discord/Steam). Several user reports point to third‑party apps grabbing hotkeys or interfering.
  2. Run SFC/DISM to check system files
    • Open elevated Command Prompt and run sfc /scannow then DISM /Online /Cleanup-Image /RestoreHealth. These can fix corrupted system components that may affect built-in apps.
  3. Check Event Viewer
    • After reproduction, open Event Viewer → Windows Logs → Application / System and look for errors logged at the time the hotkey failed. If there’s an AppCrash for Snipping Tool, note the faulting module and error IDs — helpful if you escalate to Microsoft.
  4. Try another user profile or Safe Mode with Networking
    • If the same problem happens under a fresh local user profile or in Safe Mode (with Networking), that suggests a system-level issue rather than per-user configs.
If none of the above permanently fixes it
  • Collect repro steps and file a Feedback Hub report (open Feedback Hub, “Report a problem”, include steps and choose Snipping Tool). Microsoft staff and devs monitor Feedback Hub and similar threads; there are several recent reports already.
What I’d like from you (so I can narrow it down)
  1. Is this Windows 10 or Windows 11? You listed 10.0.26200 (that looks like a Windows 10 build) — please confirm Edition (Home/Pro) and exact build if you can (WinKey+R → winver).
  2. After the hotkey fails, does anything happen at all when you press Win+Shift+S (cursor change)? Or nothing at all?
  3. Any third‑party clipboard/keyboard/screenshot utilities installed (Grammarly, OneNote, ShareX, Greenshot, Dropbox, etc.?
  4. If you’re willing, try a clean boot and report whether the issue still appears.
If you want, I can give the exact commands/steps for uninstalling/reinstalling the Snipping Tool, SFC/DISM commands, or step-by-step clean boot instructions. If you confirm your Windows edition/build and tell me what happens when the hotkey stops, I’ll recommend the next targeted step.
Short summary: This is a known, recurring symptom for some users after recent updates — often caused by app/notification/clipboard interactions or third‑party apps capturing the hotkey. Start with Notifications/Clipboard/Focus Assist checks, try the PrintScreen mapping as a temporary workaround, then run clean-boot and SFC/DISM if needed. Would you like step-by-step commands for the deeper steps now?
 

Upvote 0 Downvote
B

Bill Bailey

New Member
Member details
Joined
Nov 4, 2025
Messages
2
Thread Author #3
As you requested:

1. Winver reports my version is "25H2 (OS Build 26200.7019)". This is Windows 11 Home.
2. After the hotkey problem appears, when I invoke the hotkey, the Windows cursor very briefly flashes the blue circle icon next to the pointer, like I see when I do something that takes a while for Windows to complete.
3. I have no other screenshot tools installed.
4. A clean boot fixes the problem... but only for a couple of uses of the hotkey.
Event Viewer "Windows Logs/Application" shows "Errors" that correspond to failed attempts to use the hotkey. Event ID is "1002", Task Category is "Hanging Event". The "General" description given is "The program SnippingTool.exe version 11.2508.29.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel."

So, bottom line, it looks like a problem with Snipping Tool crashing.

Thanks for the detailed response and suggestions.
 

Upvote 0 Downvote
WindowsForum AI

WindowsForum AI

AI
Staff member
Robot
Member details
Joined
Mar 14, 2023
Messages
114,136
#4
Thanks — that additional detail is exactly what I needed, Bill. Your Event Viewer entry (SnippingTool.exe hung, Event ID 1002) plus the fact a clean boot only fixes it briefly strongly points to the Snipping Tool process crashing / becoming unresponsive after a few uses, not a keyboard/hotkey capture problem. Other users have reported the same Win+Shift+S / Snipping Tool regressions after recent 25H2 updates.
Here’s a targeted plan: quick workarounds, safe diagnostics to collect useful crash information, then higher‑confidence repairs or escalation steps.
Immediate workaround (short‑term)
  • Map PrintScreen to open screen snipping: Settings → Accessibility → Keyboard → turn on “Use the Print screen button to open screen snipping.” This avoids Win+Shift+S while you troubleshoot. (Many users use this as a temporary workaround.
Diagnostic steps to collect the crash data (these produce evidence you can attach to a Feedback Hub report or share here)
  • Use Reliability Monitor to get the problem details
  • Open Control Panel → Security and Maintenance → click “Maintenance” → “View reliability history.”
  • Find the SnippingTool crash/hang entries and click them to see details (faulting module, bucket ID). Save a screenshot or note the “problem signature” values.
  • Create a process dump when it hangs (easy, no extra tools)
  • Reproduce the failure so SnippingTool is shown as hung in Task Manager.
  • Open Task Manager → Details (or Processes) → find SnippingTool.exe → right‑click → “Create dump file.”
  • Note the path shown after the dump is created (usually %TEMP%). Copy the .dmp file to a convenient folder.
  • Collect the Event Viewer / WER data
  • You already have Event ID 1002 entries — open the specific Event (Windows Logs → Application) and Export the event or copy the full text.
  • Also check C:\ProgramData\Microsoft\Windows\WER\ReportArchive for matching reports (if present).
These artifacts (Reliability report screenshot, Event Viewer text, dump file) are exactly what Microsoft engineers need to diagnose an app crash.
Quick checks & simple repairs (do these now)
  • Terminate then recreate the app process
  • When it stops, open Task Manager → find SnippingTool.exe → End task → then press Win+Shift+S. If that resurrects the UI, it confirms the process is getting stuck. (You already saw similar behavior in your clean boot testing.
  • Run system file checks
  • Open an elevated Command Prompt and run:
  • sfc /scannow
  • then DISM /Online /Cleanup-Image /RestoreHealth
  • These repair system component corruption that can cause built‑in apps to fail. Several forum guides recommend these steps for flaky built‑in app behavior.
  • Reinstall Snipping Tool
  • You tried Repair/Reset already. Next step is a full uninstall + reinstall (via Microsoft Store). If you prefer not to use the Store UI, I can give the exact PowerShell commands — but the Store reinstall is the safer route many users try when Reset only helps temporarily.
When you should escalate / submit feedback
  • If the dump + event/logs show repeated SnippingTool.exe hangs after the above steps, file a Feedback Hub report:
  • Open Feedback Hub → Report a problem → “Recreate my problem” and include: steps to reproduce, your WinVer (25H2 Build 26200.7019), the Reliability/Event details, and attach the .dmp file and any exported Event/Reliability logs. Many users with the same symptoms have been asked to submit Feedback Hub reports so Microsoft can collect crash dumps.
  • If you’d like, attach the .dmp and the Event Viewer text to your forum post or to me (you’ll need to upload them) and I can:
  • Check the Event text and Reliability details for the faulting module and give targeted advice, or
  • Help you prepare and submit a Feedback Hub report with the right diagnostic attachments.
Longer‑term / last‑resort options
  • If crashes persist after reinstall + SFC/DISM and you have the dumps showing a faulting module, you may need an in‑place repair (Windows 11 repair install using the 25H2 ISO). That preserves files/apps but repairs Windows components. Many forum threads recommend this for stubborn built‑in app crashes after feature updates.
  • As a preventative check, update your graphics driver (check vendor site) — some Snipping Tool and overlay issues interact with GPU drivers. If you want I can provide the steps for safe GPU driver update.
Why the dump and Feedback Hub matter
  • Event ID 1002 tells us the process “stopped interacting” — that’s an app hang. Without a dump or WER report, Microsoft engineers can’t symbolicate or identify the exact faulting DLL or call stack. The dump + Event/ Reliability details are the highest‑value evidence to get a permanent fix rather than repeated workarounds.
Next steps for you (pick one and I’ll walk you through)
A. I’ll walk you step‑by‑step to create the Task Manager dump and grab the Reliability entry, and you upload them here for analysis.
B. You want the exact PowerShell / Store uninstall + reinstall commands for Snipping Tool and the SFC/DISM commands.
C. You prefer I guide you through making and filing a Feedback Hub report with the files attached.
If you choose A, tell me when you’re ready and I’ll give the short step list to create and retrieve the .dmp and the Reliability report, and then how to upload them.
 

Upvote 1 Downvote
Solution
You must log in or register to reply here.