Snipping tool with a bug [App Update behebt das Problem] [2. Update]

The Snipping Tool under Windows 10 and Windows 11 currently has an error that can also be security-related.Because changed images that are saved again with the same name retain the information before the change.

This means that if you edit an image in the Snipping Tool and save it again, the old data will also be retained and can be restored.Until Microsoft corrects this error, there is a workaround.Instead of saving the image, save it with a new name.Then the changes you made to the image cannot be recovered either.

bleeding computer explained this in a little more detail.For you, however, it is only important that you save an image with a new name until Microsoft has provided an update for it.

[Update 23.03.2023]Snipping Tool 11.2302.20.0 and later corrects the bug

Microsoft is currently delivering a new version Snipping Tool 11.2302.20.0 in the Insider channel.If you want to correct the error now, you can download and install the new version manually.

• store.rg-adguard.net call and then from left to right:
• ProductId |9MZ95KL8MR0L |Almost |click tick
• In the selection then the Microsoft.ScreenSketch 2022.2302.20.0 Download …_8wekyb3d8bbwe.msixbundle. (The version number can later be higher)
• Start the app package with a double click.

That’s it already.So it shouldn’t be long before Microsoft will make the app available to all users.

[Update 25.03.2023]: The vulnerability has been officially reported and fixed as CVE-2023-28303

Microsoft has reported the issue as a vulnerability under number CVE-2023-28303.The vulnerability itself has been labeled “Low” and also affects clipping and sketching on Windows 10. “According to the CVSS metric, a successful exploitation of this vulnerability could result in some loss of secrecy”

• The standard snipping tool under Windows 10 was not affected by this vulnerability
• Snip and Sketch on Windows 10 fixes this vulnerability with version 10.2008.3001.0 and later
• The Snipping Tool on Windows 11 fixes this vulnerability with version 11.2302.20.0 and later.(As reported above)

Windows 11 tutorials and help