Windows 10: Microsoft is fixing a Windows 10 bug that causes forced reboots

Microsoft is finally fixing an annoying Windows 10 bug that causes a random reboot on some devices running the October 2020 Update. The tech giant has also removed the ‘compatibility hold’, which should allow more users to install the upcoming feature updates.

In November 2020, Microsoft confirmed that some of Windows 10’s most recent updates result in critical problems with the Local Security Authority Process for some configurations.

If your device is affected, Windows will start to randomly reboot with a cryptic error message that states your “PC will automatically restart”. You’ll have less than one minute to save your work. It could lead to data loss if you don’t quickly save any work you’ve open in the background.



The good news is that the issue is rare and a fix is now available, according to a new message posted to the support document.

The documentation states that the fix is bundled with the latest updates and users won’t encounter the critical error as long as they’re using the most recent version of Windows 10 version 20H2.

Microsoft has also lifted the upgrade block, which prevented the October 2020 Update (version 20H2) from being offered on some PCs. This move will also allow the tech giant to deliver the next update codenamed ’21H1′ to more users.

In addition to the forced reboot bug, Microsoft has also started rolling out a fix for an issue that deletes your passwords. When this happens, Windows will automatically delete your login sessions in apps and websites after rebooting your computer.

Anyone suffering from authentication and browser cookies problem will be hoping that the resolution comes soon. However, Microsoft has clarified that it’s still testing the fix with Windows Insiders and the patch will begin rolling out to the general public soon.

The post Microsoft is fixing a Windows 10 bug that causes forced reboots 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 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

 

Windows 10 KB3213986 Update Cripples Multi-monitor Gaming

This should be enough to get the conspiracy theorists suggesting that Microsoft is intentionally crippling multi-monitor support in fullscreen mode since games sold on the Microsoft Store all work in the pseudo-fullscreen mode...

Or it could just be an idiotic bug that will be fixed in time.