Snipping Tool issues with Build 25295

Anonymous
2023-02-11T14:14:11+00:00

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.

0 comments

85 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. CrazyKats 19,595 Reputation points Volunteer Moderator
    2023-02-11T16:26:25+00:00

    FG, you have taken 2 different threads OT about the Snipping Tool.

    This is in violation of CoC. Repeated violations of CoC will result

    in a suspension or ban.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-02-11T18:04:44+00:00

    Snipping Tool. "+ New" button fails to open in Build 25295.

    https://aka.ms/AAjlve4

    Was this answer helpful?

    0 comments
  3. BryceSor 5,500 Reputation points Volunteer Moderator
    2023-02-11T19:38:38+00:00

    Hi Fg2001,

    I have the same issue here on different devices, windows key, shift, S still works, reinstalling I still have the same issue.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-02-11T19:53:11+00:00

    Hi Fg2001,

    I have the same issue here on different devices, windows key, shift, S still works, reinstalling I still have the same issue.

    Thanks for confirming the problem. I only had it on one machine.

    Apparently, they were still using the previous build MicrosoftWindows.Client.Core from 25290.1010.

    Issuing the command below in Power Shell fixed the problem.

    The machines that were not failing, only had the correct version of MicrosoftWindows.Client.Core 25295.1000 the old one was no longer there. 🤷‍♂️

    This command fixed the problem:

    Get-AppxPackage MicrosoftWindows.Client.Core -AllUsers | Reset-AppxPackage

    Now I only see the latest version when I list all the installed Apps:

    Get-AppxPackage -allusers | Select Name, PackageFullName

    Image

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. BryceSor 5,500 Reputation points Volunteer Moderator
    2023-02-11T20:16:57+00:00

    FIXED with the code, cheers, funny last night I tried reinstalling through the Store and looked at the code but thought re-installing would work and then started watching youtube

    Was this answer helpful?

    0 comments