Recent issues for many of our users using Snipping Tool - not creating snip/damaged files, closing unexpectedly.

Question

Recent issues for many of our users using Snipping Tool - not creating snip/damaged files, closing unexpectedly.

Shannan Shapiro 116

We have reports for several users about Snipping Tool not working properly beginning a couple of days ago and the number of reports continues to increase. Not seeing any discussions of known issues with the most recent update, but seems like likely something based on the timing of the influx of reports on our end. We have tried resetting/uninstalling/reinstalling from MS Store, but issue continues. Tried sfc which seems to repair briefly but the issue returns again. Users reported after doing snip, preview is blank, if you try and view the screen shot file, says it is damaged, others reporting it just closes out unexpectedly when doing the snip. Any others experiencing issues? or know of issues with latest version of Snipping Tools. Haven't opened ticket with MS support yet, as often the forums have been faster to find answers.....

Stella, Aaron (A) 20 Reputation points

2025-03-07T15:46:16.4433333+00:00

We're getting reports of the same thing in our org.
Tom DeVries 20 Reputation points

2025-03-07T15:56:01.3+00:00

Same here. Reports started yesterday. Some users were fixed without taking any actions. Some were fixed by disabling "automatically save original screenshot". but it doesn't help everyone. It almost seems like time fixed them. The reports keep coming in.
Shannan Shapiro 116 Reputation points

2025-03-07T19:03:06.1033333+00:00

opened a ticket with MS support, will update if I learn anything helpful.
Joe K 20 Reputation points

2025-03-07T20:15:51.5933333+00:00

We started to experience this issue at my company as well yesterday. We can successfully capture snips using the Snipping Tool only on the primary monitor that is set in Display Settings. It crashes only if the snip is taken on any secondary monitors. This is causing disruptions for those who use this application frequently.
Tom DeVries 20 Reputation points

2025-03-12T20:49:43.09+00:00

Have you found any correlation with the people affected by this problem? Like all have certain hardware/drivers or got a specific version of the snipping tool, etc
Adam Guzman 0 Reputation points

2025-03-12T23:29:51.98+00:00

@Shannan Shapiro Any word back from MS Support?
Shannan Shapiro 116 Reputation points

2025-03-13T13:24:00.62+00:00

Was working with support to gather the logs they requested, etc... but this morning they confirmed it's now considered a known issue and they expect a resolution to be included in the updates scheduled for April. That's not ideal on timing, but that's what was shared with me so far. Asking if they have any known workarounds or not.
Adam Guzman 0 Reputation points

2025-03-13T18:41:35.1133333+00:00

Has anyone here experienced this issue because caused by some sort of security tool? I am trying to test this by removing one of our security tools on an affected host and it seems to "fix" the issue, but I am not sure as to why because the snipping tool is already listed as approved in the tool. Does anyone know what other files the snippingtool.exe uses as part of its screen capturing features?
Shannan Shapiro 116 Reputation points

2025-03-13T20:47:04.77+00:00

we haven't seen it related to our security tools so far, but it does seem to come and go, users reported the issue, happened repeatedly for them for a day or two, then it worked, then it didn't again, then ok again.... in the event viewer we did see an event 1000 for SnippingTool.exe for module c:\windows\system32\ntdll.dll
Shannan Shapiro 116 Reputation points

2025-03-16T12:08:37.89+00:00

small update from Micrososoft, if anything changes with this, they are supposed to let me know : Please be informed that the mentioned known issue does not have any workarounds at the moment as confirmed with the Debugging Team internally and is expected to be resolved in the 11.2502 build of snipping tool. This will be available late march or early April.
Tom DeVries 20 Reputation points

2025-03-17T12:09:04.26+00:00

Our workarounds are to take screenshots on the primary monitor or run snipping tool as admin.
Paul Strobel 0 Reputation points

2025-03-18T17:56:38.3966667+00:00

Nevermind, haven't had consistent luck with service or process fiddling.
Fuchser-Burns, Carol 5 Reputation points

2025-03-20T18:54:09.9666667+00:00

From Application Event Log:

Faulting application name: SnippingTool.exe, version: 11.2501.7.0, time stamp: 0x67ae31d7

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000409

Fault offset: 0x00007ffa8774328f

Faulting process id: 0x4398

Faulting application start time: 0x1DB99C7B3310566

Faulting application path: C:\Program Files\WindowsApps\Microsoft.ScreenSketch_11.2501.7.0_x64__8wekyb3d8bbwe\SnippingTool\SnippingTool.exe

Faulting module path: unknown

Report Id: 8927a047-96df-4228-9fde-199b244b704d

Faulting package full name: Microsoft.ScreenSketch_11.2501.7.0_x64__8wekyb3d8bbwe

Faulting package-relative application ID: App
Fuchser-Burns, Carol 5 Reputation points

2025-03-20T18:59:21.4566667+00:00
I have uninstalled / reinstalled and ran a repair on snipping tool. First app hang was March 3 for me, but I have not correlated a patch etc. applying on that date. I don't find my Win11 machine to be in early adopter program, and I also note during the March 2025 CU update the event:

Fault bucket 2289488628523225715, type 5 Event Name: UpdateAgentDiag Response: Not available Cab Id: 0

Problem signature: P1: 22 P2: X P3: 1 P4: 0xC1900401 P5: amd64 P6: 26100 P7: ge_release P8: 26100 P9: ge_release_svc_prod1

.... for that I want to research that the UAC change for repairing apps, during CU update, could be positively impactful by the key below:

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]"DisableLUAInRepair"=dword:00000001
Shannan Shapiro 116 Reputation points

2025-03-20T19:53:02.79+00:00

Microsoft acknowledged an issue on their part and it should have a fix coming later in March/early April - what I received from MS : Please be informed that the mentioned known issue does not have any workarounds at the moment as confirmed with the Debugging Team internally and is expected to be resolved in the 11.2502 build of snipping tool. This will be available late march or early April.
LAlvarez 0 Reputation points

2025-05-07T17:39:57.2866667+00:00

What it found is snipping tool running multiple process,so when I attempt to do a screen capture, I have to select twice the snip I want to capture.

2 answers

Your answer

Stella, Aaron (A) 20 Reputation points

2025-03-07T15:46:16.4433333+00:00

We're getting reports of the same thing in our org.
Tom DeVries 20 Reputation points

2025-03-07T15:56:01.3+00:00

Same here. Reports started yesterday. Some users were fixed without taking any actions. Some were fixed by disabling "automatically save original screenshot". but it doesn't help everyone. It almost seems like time fixed them. The reports keep coming in.
Shannan Shapiro 116 Reputation points

2025-03-07T19:03:06.1033333+00:00

opened a ticket with MS support, will update if I learn anything helpful.
Joe K 20 Reputation points

2025-03-07T20:15:51.5933333+00:00

We started to experience this issue at my company as well yesterday. We can successfully capture snips using the Snipping Tool only on the primary monitor that is set in Display Settings. It crashes only if the snip is taken on any secondary monitors. This is causing disruptions for those who use this application frequently.
Tom DeVries 20 Reputation points

2025-03-12T20:49:43.09+00:00

Have you found any correlation with the people affected by this problem? Like all have certain hardware/drivers or got a specific version of the snipping tool, etc
Adam Guzman 0 Reputation points

2025-03-12T23:29:51.98+00:00

@Shannan Shapiro Any word back from MS Support?
Shannan Shapiro 116 Reputation points

2025-03-13T13:24:00.62+00:00

Was working with support to gather the logs they requested, etc... but this morning they confirmed it's now considered a known issue and they expect a resolution to be included in the updates scheduled for April. That's not ideal on timing, but that's what was shared with me so far. Asking if they have any known workarounds or not.
Adam Guzman 0 Reputation points

2025-03-13T18:41:35.1133333+00:00

Has anyone here experienced this issue because caused by some sort of security tool? I am trying to test this by removing one of our security tools on an affected host and it seems to "fix" the issue, but I am not sure as to why because the snipping tool is already listed as approved in the tool. Does anyone know what other files the snippingtool.exe uses as part of its screen capturing features?
Shannan Shapiro 116 Reputation points

2025-03-13T20:47:04.77+00:00

we haven't seen it related to our security tools so far, but it does seem to come and go, users reported the issue, happened repeatedly for them for a day or two, then it worked, then it didn't again, then ok again.... in the event viewer we did see an event 1000 for SnippingTool.exe for module c:\windows\system32\ntdll.dll
Shannan Shapiro 116 Reputation points

2025-03-16T12:08:37.89+00:00

small update from Micrososoft, if anything changes with this, they are supposed to let me know : Please be informed that the mentioned known issue does not have any workarounds at the moment as confirmed with the Debugging Team internally and is expected to be resolved in the 11.2502 build of snipping tool. This will be available late march or early April.
Tom DeVries 20 Reputation points

2025-03-17T12:09:04.26+00:00

Our workarounds are to take screenshots on the primary monitor or run snipping tool as admin.
Paul Strobel 0 Reputation points

2025-03-18T17:56:38.3966667+00:00

Nevermind, haven't had consistent luck with service or process fiddling.
Fuchser-Burns, Carol 5 Reputation points

2025-03-20T18:54:09.9666667+00:00

From Application Event Log:

Faulting application name: SnippingTool.exe, version: 11.2501.7.0, time stamp: 0x67ae31d7

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000409

Fault offset: 0x00007ffa8774328f

Faulting process id: 0x4398

Faulting application start time: 0x1DB99C7B3310566

Faulting application path: C:\Program Files\WindowsApps\Microsoft.ScreenSketch_11.2501.7.0_x64__8wekyb3d8bbwe\SnippingTool\SnippingTool.exe

Faulting module path: unknown

Report Id: 8927a047-96df-4228-9fde-199b244b704d

Faulting package full name: Microsoft.ScreenSketch_11.2501.7.0_x64__8wekyb3d8bbwe

Faulting package-relative application ID: App
Fuchser-Burns, Carol 5 Reputation points

2025-03-20T18:59:21.4566667+00:00

I have uninstalled / reinstalled and ran a repair on snipping tool. First app hang was March 3 for me, but I have not correlated a patch etc. applying on that date. I don't find my Win11 machine to be in early adopter program, and I also note during the March 2025 CU update the event:

Fault bucket 2289488628523225715, type 5 Event Name: UpdateAgentDiag Response: Not available Cab Id: 0

Problem signature: P1: 22 P2: X P3: 1 P4: 0xC1900401 P5: amd64 P6: 26100 P7: ge_release P8: 26100 P9: ge_release_svc_prod1

.... for that I want to research that the UAC change for repairing apps, during CU update, could be positively impactful by the key below:

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]"DisableLUAInRepair"=dword:00000001
Shannan Shapiro 116 Reputation points

2025-03-20T19:53:02.79+00:00

Microsoft acknowledged an issue on their part and it should have a fix coming later in March/early April - what I received from MS : Please be informed that the mentioned known issue does not have any workarounds at the moment as confirmed with the Debugging Team internally and is expected to be resolved in the 11.2502 build of snipping tool. This will be available late march or early April.
LAlvarez 0 Reputation points

2025-05-07T17:39:57.2866667+00:00

What it found is snipping tool running multiple process,so when I attempt to do a screen capture, I have to select twice the snip I want to capture.

Answer 1

TrinityZ-1778 50

This is my first time posting so please bear with me, but I also had the problems listed with my snipping tool at work and managed to fix the issue by:

Go to Windows Settings
Apps
Default Apps
Snipping Tool
Scrolling down to the bottom where it says MS-SCREENCLIP
Change the Default App from Snipping Tool to Screen Snipping

I was able to edit the snip, snip across multiple screens instead of just the main one, and it didn’t close unexpectedly anymore, and it wasn’t just a white damaged file.

I hope this helps somebody else :)

Paul Strobel 0 Reputation points

2025-03-21T15:49:59.48+00:00

Wonderful! Thank you!
Katt Wallingford 0 Reputation points

2025-03-21T16:30:06.9+00:00

Our desk had been inundated with this particular glitch. It's been less than a few hours since your post, but we've gotten at least 7 massive tickets resolved because of this. Thank you!
C Ruhe 0 Reputation points

2025-03-25T07:44:47.4333333+00:00

Thanks alot. Got this issue after updating from 23H2 to 24H2. I just want a working system and not ALL THE TIME some 'little' problem here and there. Wastes so much time.
Adam Guzman 0 Reputation points

2025-03-28T20:57:05.5+00:00

We found that this solution fixed the issue for all of our affected users. Also, since the update to the newest release, we have not experienced any more issues with the Snipping Tool.
F G 41 Reputation points

2025-05-09T05:33:40.4133333+00:00

Unfortunately, the suggested workaround is only good with Build 26100.3915 and Canary 27842.100, it is no good for Dev 26200.5581 nor Beta 26120.3950.
F G 41 Reputation points

2025-05-10T03:33:39.6366667+00:00

There is another side effect on the suggested workaround, it appears to be incompatible with the new Text Extractor feature which only work if MS-SCREENCLIP is set to default to Snipping Tool.

The only choice left is one bug versus the other. Microsoft needs to fix this mess that they recently created.
FredSwims 0 Reputation points

2025-05-14T07:15:23.43+00:00

This works however only for snipping. It will not Record. And the new toolbar with the "Click to Do" app does not appear; the old toolbar appears.

Answer 2

Shannan Shapiro 116

11.2502.18.0 of snipping tool is available in the MS Store now. We are manually updating a few of our most impacted users now.

Tom DeVries 20 Reputation points

2025-03-28T17:41:12.0333333+00:00

11.2502.18.0 has not fixed all my users. Anyone else notice that as well?

Share via

Recent issues for many of our users using Snipping Tool - not creating snip/damaged files, closing unexpectedly.

2 answers

Your answer