Windows 10: Microsoft confirms Windows 10’s screenshot tool is crashing for some users

It looks like Windows 10’s native screenshot tool called ‘Snip & Sketch’ is being hit by a pretty annoying problem, where the app simply fails to load for some users when they try to take screenshots. This bug doesn’t appear to entirely affect the operating system’s ability to capture screenshots as long as you don’t rely on Snip & Sketch tool.

The fact that Microsoft’s own app is not able to run on its own operating system isn’t a great look, but this isn’t the first time. A bug broke the same app last year and the company later rushed out a fix for some of the issues.

As you’re probably aware, Snip & Sketch tool allows users to capture screenshots on Windows and it comes with a variety of options, including the ability to edit screenshots, capture only parts of the screen, and later make changes using apps like Paint, so it can be a genuinely useful tool for many folks.

On April 28, Microsoft quietly updated its support documents to acknowledge the problem with Windows 10’s screenshot tool. The document states that the company is aware of an issue whereby the Snip & Sketch app might fail to capture a screenshot and might fail to open when you press and hold Windows key+shift+S.

This issue originated in Windows 10’s February 2022 update and it affects all cumulative updates released later.

Microsoft hasn’t revealed when a fix for the snipping tool will arrive, but it has suggested that it’s actively working on a fix.

“We are presently investigating and will provide an update when more information is available,” Microsoft said.

In addition to a buggy Snip & Sketch tool, Windows 10 is also plagued with an issue whereby the recovery discs created using Control Panel’s legacy Backup and Restore (Windows 7) app won’t start on some devices. Thankfully, no third-party recovery apps are affected and Microsoft is working on a workaround.

It is worth noting that these issues are still present in Windows 10’s latest optional update (KB5011831). This means that the May 2022 Patch Tuesday update won’t resolve the problems, but the hotfix could still arrive by the end of the month via another optional patch.

The post Microsoft confirms Windows 10’s screenshot tool is crashing for some users appeared first on Windows Latest

Weiterlesen...

 

Microsoft Selects Dolby Audio for Windows 10

it would've been great if microsoft added HEVC decoders, LAV filters along with other codecs with Windows 10, and developing WMP to be better than VLC, KMPlayer and such sorts of media players.

Nevertheless, this is good step for microsoft, by far.

 

Microsoft signals end of Paint program

Microsoft has confirmed that it will continue to offer its graphics program Paint.

In a recent update, it had listed Paint as a feature that would be either removed or no longer developed.

Paint, renowned for its simplicity, has been part of the Windows operating system since its launch in 1985.

Microsoft suggested it would not remain on Windows 10 by default but did say it would be available for free on the Windows Store.

BBC news Report here
Microsoft Paint avoids brush with death

 

Microsoft Botches Up UEFI Support for Windows 7 on ASUS Motherboards



Microsoft suggests updating to Windows 10 to patch Windows 7

• 
  
  
• Chris Merriman
• 
  @ChrisTheDJ
• 05 May 2016

• Tweet
• Facebook
• Google plus
• Send to

9 Comments

MICROSOFT HAS confirmed a potentially lappy-borking problem that it won't be fixing, because Windows 7.

Woody Leonhard, the respected Windows columnist, points to a problem involving Asus motherboards, which also appear rebadged in a variety of other manufacturers' machines, and the activation of UEFI Secure Boot for Windows 7 in a patch KB3133977.

Short version: install update, welcome to Borksville, population you.

Both Asus and Microsoft acknowledged the problem. Microsoft entitled the article "BitLocker can't encrypt drives because of service crashes in svchost.exe process in Windows 7 or Windows Server 2008 R2", but we prefer to just call it "Trevor for brevity."

The firm's advice was that it's an optional update, leave well alone, you'll be fine, or alternatively turn secure boot off.

Then Microsoft did a silly, silly thing.

It moved the update from 'optional' to 'recommended' and anyone who reads this site regularly will know what happens when Microsoft does this. That's right boys and girls - it makes it automatically install, unless you've specifically told your machine not to.

So now, if you have one of the affected motherboard and you keep your security updates automatic like wot Microsoft recommends, then your machine will stop working properly.

We should add it's not permanently bricked, but it will take some mucking about in the BIOS to fix and that's a pain even for an experienced computer user.

Microsoft has, by offering a workaround, suggested heavily that it won't be fixing the problem, though we have asked the question, so expect a response in about a fortnight.

But the real kicker is this piece of advice: "Note The Secure Boot feature is supported in Windows 10. To learn more about the security advantages of this feature and about the upgrade path from Windows 7 to Windows 10, go to the following Windows website"

Holy toledo, this company really knows how to rub people up the wrong way.

After all - if the advice is to manually avoid the update or move to a version of the operating system where there's virtually no control over updates, then Microsoft is dealing in massive contradictions.

A more cynical site would suggest that it's yet another example of Microsoft running Windows 7 into the ground and adding built in obsolescence to encourage quicker updates. But we're not that sort of site.

Its the patching to force secure boot that is the problem win 7 does not support secure boot
hence it borks systems and well microsofts answer is Cactus >your Asshole > insert

from the inquirer