Be advised they are also investigating why the
workaround is not working for some.
Thanks! but I wasn't affected by this bug.
It seems that users with the old app still installed might be the ones experiencing it, just a guess.
Snipping Tool issues with Build 25295
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
Split from this thread.
Sure did. Tried also repair and reset.
It didn't help.
Would be nice to be able to install older versions in cases like this.
Hi Sibro,
I solved the Snipping Tool problem by restoring 25284 and then upgrading to 25295 directly, skipping 25290.1000 and 25290.1010.
Snipping tool works fine now on the same machine that was failing when it went from 25290.1010 to 25295.1000.
Go figure!
What made me suspicious was that error on DCOM 25290.1010.
Windows Insider program | Windows Insider preview | Desktop environment and Start menu
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
85 answers
Sort by: Most helpful
-
Anonymous
2023-02-15T20:59:31+00:00 -
Anonymous
2023-02-15T18:49:57+00:00 Hi fg,
They posted a workaround. 👍
- [NEW] We’re investigating reports that the New button in Snipping Tool isn’t working for some Insiders after upgrading to Build 25295. If you are impacted by this, going to Settings > Apps > Default apps, and setting screen snipping as the default for ms-screenclip, it should resolve the issue.
-
Anonymous
2023-02-13T03:20:57+00:00 @Pauli O,
This is a system ugraded directly from 25284.1000 to 25295.1000.
It shows both versions and still the Sipping Tool is happy and works fine without the crash. 😉
No need to reset anything.
I have only seen the problem with the snipping tool on the same system when it went from 25290.1010 to 25295.1000. 🤷♂️
It seems that something got screwed up with 25290.1010 updates.
I hope MS comes up with an explanation. It doesn't make much sense to me. 😎
This one has no problem with Snipping Tool. 👍
This one has the Snipping Tool crash error. 😜
Seen the same error situation on multiple machines.
No problem with Snipping Tool after eliminating the 25290.1010 version. 👍
-
Anonymous
2023-02-12T17:43:19+00:00 Pauli,
This is interesting on Public Build 22621.1194. Still 2 versions of Client.Core.🤷♂️
and on Beta:
Looks like the problem could be specific with .1010.
I had one machine upgraded directly from 25284 and had both 25284.1000 and 25295.1000 and it was not causing the bug.
Also, weird that on the error message in Event Viewer it shows an "!" at the end the name. 🤷♂️
-
Anonymous
2023-02-12T09:22:19+00:00 I take copy/paste of that command from your reply to notepad and add only that filter -Name *Name* before use it in terminal and copy to my reply.
That is the other difference copy/paste with mouse right click to power shell works if I use Terminal, but not if I open Power Shell directly without Terminal.
Even more crazy. 🤣🤣
Try pasting from your post directly to Power Shell without using the terminal and you will see the problem.
Looks like Terminal is translating to normal dash instead of en dash or em dash.
Anyway, mystery solved. 😉😎
I have to go to bed. Good night.