The Snipping Tool breaks more often than a built-in Windows utility has any right to. It is not a complex application — it captures a rectangle of pixels and drops them on your clipboard — yet it manages to fail in at least a dozen distinct ways, and Microsoft’s own troubleshooting advice cycles through the same four generic steps regardless of what’s actually wrong. That’s the problem this page exists to fix.

Below is every cause we’ve been able to verify on current Windows 11 builds, ordered by how likely it is to be your problem. Work down the list. Most people are fixed by the time they reach the third heading. The version this was last checked against is in the 11.25xx family of the Snipping Tool app (you can see your exact build at Settings > Apps > Installed apps > Snipping Tool > Advanced options), and the app updates through the Microsoft Store independently of Windows, so the build number moves constantly. Last verified May 2026.

First, work out which failure you have

“Not working” covers several genuinely different problems, and the fix depends entirely on which one you’re seeing. Before you start uninstalling things, identify your symptom:

  • The app won’t open at all, or throws an error the moment you launch it.
  • The app opens, but + New does nothing — the capture overlay never appears.
  • The capture works, but the screenshot is blank, black, or the wrong region (common on multi-monitor setups).
  • Nothing happens when you press Win + Shift + S, but the app itself opens fine from the Start menu.
  • It crashes mid-capture, often after an update.

If your problem is specifically the keyboard shortcut, jump straight to our dedicated walkthrough on why Win+Shift+S stops working and how to get it back — that’s a different fault tree. If your captures are distorted or land on the wrong monitor, that’s almost always a scaling issue, covered in detail in the multi-monitor screenshot bugs explainer. Everything else, stay here.

Cause 1: A recent Windows update broke it (and it’s not your fault)

If your Snipping Tool stopped working suddenly, on a day you didn’t change anything, the most likely explanation in early 2026 is the one nobody wants to hear: Microsoft shipped a bad update.

The January 2026 cumulative update (KB5074109) is the clearest recent example. It triggered error 0x803F8001 — “Snipping Tool is currently not available in your account. Make sure you are signed in to the Microsoft Store and try again” — across a range of built-in apps, not just Snipping Tool but Notepad and Paint too. Microsoft eventually acknowledged the regression and pushed a server-side fix, but for several days the only reliable workaround was to reinstall the app by hand.

Here’s the honest position: when an inbox app dies on the same day for thousands of people at once, the cause is upstream and there is nothing clever you can do locally. Before you spend an hour resetting components, do two things. First, search the exact error code — if it’s a current outbreak, you’ll find a Microsoft community thread filling up in real time. Second, check our Microsoft Office image regression timeline, which logs confirmed image and capture bugs by build and KB number so you can tell at a glance whether your problem is a known regression with a fix on the way.

If it is a known break, the fastest local recovery is the manual reinstall in Cause 6 below. Otherwise, install any pending Windows and Store updates and reboot — Microsoft’s fix usually arrives through one of those channels.

Cause 2: The app needs a Repair (try this before anything drastic)

For everyday “it just stopped” failures that aren’t tied to a known outbreak, the Repair function fixes more cases than any other single step, and it doesn’t touch your settings or history. It should be the first thing you try, and it’s bewildering how rarely Microsoft’s own guidance leads with it.

  1. Open Settings > Apps > Installed apps.
  2. Find Snipping Tool, click the three-dot menu, and choose Advanced options.
  3. Scroll down and click Repair.

Repair re-registers the app package without deleting anything. Test the tool immediately afterward. If it’s still broken, and only if Repair failed, use Reset on the same screen — that one does wipe the app’s local data (recent snips, preferences), but it clears deeper corruption that Repair can’t reach.

This is the part of Microsoft’s advice that’s actually good. The Repair/Reset pair resolves a genuine majority of “won’t open” and “+New does nothing” cases. The trouble is they bury it under a wall of generic filler about restarting your PC and running the Store troubleshooter.

Cause 3: “A problem with Windows is preventing Screen Snipping from opening”

This exact dialog has haunted the Snipping Tool since the Windows 11 launch. Historically its root cause was a genuinely embarrassing one: an expired signing certificate on the app package. Microsoft let a certificate lapse, the package failed validation, and the tool refused to launch until a patch restored it.

The certificate problem itself is long fixed, but the symptom — that specific dialog — still surfaces, now usually because the app package is in a bad state rather than because a certificate has expired. The fix order is:

  1. Set your clock to automatic. Open Settings > Time & language > Date & time and turn on Set time automatically. Certificate and package validation depends on an accurate system clock; a wrong date can make a perfectly valid package look expired.
  2. Run Repair, then Reset (Cause 2).
  3. If both fail, reinstall (Cause 6).

The clock step sounds absurd, but it’s the one fix on this list with a direct logical link to the original certificate fiasco, and it costs ten seconds to rule out.

Cause 4: Corporate machine, virtual desktop, or FSLogix

If you’re reading this on a work laptop or a virtual desktop, your failure mode is probably not the same as a home user’s, and the home-user fixes may be unavailable to you anyway because you can’t reinstall Store apps without admin rights.

The signature problem on Azure Virtual Desktop (AVD) and other multi-session environments is FSLogix trying to re-register an outdated Snipping Tool package into the user’s profile container. The result is intermittent and maddening: the app works on one host, fails on the next, and the + New button does nothing while Win + Shift + S sometimes still works as a fallback. Because it’s profile-bound, it follows the user around rather than staying with one machine.

There’s no clean end-user fix here — this one belongs to whoever administers the environment. If that’s you, the levers are: exclude the Snipping Tool package paths from the FSLogix profile so it isn’t captured and replayed stale, ensure all session hosts carry the same current cumulative update, and avoid pinning an old app version in the golden image. If that’s not you, the honest advice is to log it with IT with the specific detail that Win + Shift + S works while + New doesn’t, because that pattern points straight at the package-registration conflict and saves them an hour of guessing.

Cause 5: The wrong app is registered for screen clipping

Windows routes the screen-snip action through a protocol called ms-screenclip. If a third-party screenshot tool, an old install, or a botched update has hijacked that association, your captures can vanish, open in the wrong app, or do nothing at all.

You can test the routing directly. Press Win + R, type ms-screenclip: (the colon matters), and press Enter. If the capture overlay appears, the app and engine are healthy and your problem is with how the action is being triggered — likely the keyboard shortcut or a hijacking app, which sends you to the Win+Shift+S diagnostic path. If ms-screenclip: does nothing, the app itself is broken and you’re back to Repair, Reset, and reinstall.

To check the default app association, go to Settings > Apps > Default apps, search for the MS-SCREENCLIP protocol, and confirm it points at Screen Snipping / Snipping Tool rather than a third-party tool you installed and forgot about.

Cause 6: A clean reinstall (the fix Microsoft pushed in January 2026)

When Repair and Reset both fail, removing and reinstalling the app clears the package state entirely. During the January 2026 outbreak this was the only thing that worked for most people, and it’s the reliable last resort for any app-side corruption.

The cleanest method uses PowerShell. Open Windows Terminal as Administrator and remove the package:

Get-AppxPackage *ScreenSketch* | Remove-AppxPackage

Then reinstall from the Microsoft Store — search for Snipping Tool and install it fresh. (The package is named ScreenSketch internally for historical reasons; the modern Snipping Tool is the merged successor to the old Snip & Sketch.)

If you’d rather avoid the command line, uninstalling and reinstalling from the Microsoft Store page achieves the same thing for most users. Either way, reboot afterward and test.

Cause 7: Notifications are off, and it only looks broken

This one isn’t really a fault at all, but it sends a steady stream of people looking for fixes that don’t exist. When you capture with Win + Shift + S, the snip goes silently to your clipboard and a notification toast appears so you can annotate or save it. If you’ve disabled notifications for the Snipping Tool, the capture still happens — you just get no confirmation, so it feels like nothing worked. Paste into any app with Ctrl + V and you’ll find your screenshot was there all along.

The fix is to re-enable the toast at Settings > System > Notifications, then scroll to Snipping Tool and switch it on. While you’re thinking about where captures end up, it’s worth knowing that screenshots can also fail to persist if clipboard history is misconfigured — we cover that in why clipboard history doesn’t save screenshots.

When to stop fixing and switch tools

Here’s the position most troubleshooting pages won’t take: the Snipping Tool is good enough for the overwhelming majority of users, and you should not abandon it over a single bad week. But if you’re on a managed machine where the FSLogix problem recurs, or you genuinely need features it lacks — scrolling capture, reliable multi-monitor handling, automatic file naming — then a third-party tool is a legitimate answer rather than an admission of defeat. We test the realistic alternatives in the best screenshot tools for Windows 11, compared, and the honest conclusion there is that most people don’t need to leave. Know that before you pay for anything.

Frequently asked questions

Why did my Snipping Tool stop working all of a sudden? A sudden, same-day failure usually means a Windows or Store update broke it rather than anything you did. The January 2026 update (KB5074109) is the clearest recent case, producing error 0x803F8001. Check for a known regression first, then Repair the app, then reinstall.

What is error 0x803F8001? It’s a Microsoft Store licensing error — “Snipping Tool is currently not available in your account.” It surfaced en masse after a January 2026 update that affected several built-in apps. Reinstalling the app resolved it for most people while Microsoft rolled out a fix.

Does Repair delete my screenshots or settings? No. Repair re-registers the app without touching your data. Reset is the one that wipes local app data, so try Repair first and only fall back to Reset if Repair doesn’t fix it.

Win + Shift + S does nothing but the app opens fine — why? That split is diagnostic: the app is healthy, so the fault is in how the shortcut is triggered — disabled notifications, a hijacking third-party tool, or a gaming-keyboard mode that disables the Windows key. The full diagnostic path is in our Win+Shift+S guide.

My screenshots are distorted or capture the wrong area on a second monitor. That’s a display-scaling problem, not an app problem. It happens when your monitors run different scaling percentages. The fixes and the relevant Microsoft patch are covered in the multi-monitor screenshot bugs explainer.

Is it worth switching to a third-party screenshot tool? For most people, no. The built-in tool is capable and the common faults are fixable. Switch only if you have a recurring environment-specific failure or need a feature it genuinely lacks — see our tested comparison before paying for anything.