Share this article
Improve this guide
Microsoft confirms Windows 10/11 forced reboot and BSOD bugs
3 min. read
Published onNovember 6, 2020
published onNovember 6, 2020
Share this article
Improve this guide
Read our disclosure page to find out how can you help Windows Report sustain the editorial teamRead more
Key notes
AlthoughMicrosoftthrottled the delivery of the Windows 10 20H2 update, many users still managed to get their hands on it before others could. However, some of the lucky ones who received the update experienced some critical issues.
Users have reported getting forced reboot warnings shortly after signing in, which obviously ended in their systems being rebooted. On the same note, others have been greeted by Windows’Blue Screen of Death(BSOD), which obviously translates into systemcrashes.
Microsoft issued warnings, recommends rollback
In light of these recent developments, Microsoft issued a couple of warnings regarding updating to the latest version, as it may not be perfectly stable for certain users.
Additionally, the company recommends users to roll back to a previous, working version of theoperating systemuntil the situation is under control.
The rollback recommendation is mainly addressed to users who have experienced these problems. Therefore, if you’ve managed to update and everything is a-ok, you don’t need to worry about it. Not yet, at least.
Device incompatibility causing the issue
Microsoftand Intel have identified somecompatibility issueswith Thunderbolt NVMe SSDs. Plugging such a device in after upgrading toWindows 10 2004or 20H2 can lead to aBSOD.
Microsofthas made efforts to ensure that incompatible devices don’t receive the update by adding compatibility blocks. And for good reason, too.
It would appear that forcefully updating to Windows 10 2004 or 20H2 cantrigger the BSODif your system isn’t eligible for an upgrade.
To avoid this situation entirely, make sure your device is compatible before upgrading by checking for updates only from Windows’ built-in Update Checker.
If you see any compatibility blocks, don’t try to force the upgrade by using physical media or other means of deployment.
You might experienceBSODsand need to revert to a previous, working version of theoperating system, which is not exactly a breeze to do.
Windows 10 force-reboots some systems
Yet anotherbugrendering your PC almost unusable is the forced reboot one thatMicrosoftrecentlyconfirmed. This one might seem a bit more forgiving than theBSODone we described above, but it’s just as merciless regarding system usability.
After upgrading toWindows 10 20H2, if you’re among the unlucky affected ones, Windows will prompt you with a message, informing you that your PC will restart automatically in one minute. The message is followed by a forced reboot of your system.
To make matters worse, rebooting your system or logging out of your user account still spawns thiserror. Therefore, you’ll need to roll back to a previous, stable version ofWindows 10to fix it.
As with theBSOD,Microsoftalready applied a compatibility hold on affected devices. So, if your system is not deemed to accommodate the update without any incidents, it’s best if you don’t force it.
Did you have any of these issues after upgrading to a newer version ofWindows 10? Tell us all about your experience in the comments section below:
[wl_navigator]
Vlad Constantinescu
Vlad might have a degree in Animal Husbandry and Livestock Management, but he’s currently rocking anything software related, ranging from testing programs to writing in-depth reviews about them.
He spent 3-4 years as a software editor at Softpedia and another year as a VPN specialist before he landed his current job as an author at Windows Report.
In his free time, Vlad enjoys playing guitar, doing jigsaw puzzles, researching cybersecurity, and even having a good read on rainy days.
User forum
6 messages
Sort by:LatestOldestMost Votes
Comment*
Name*
Email*
Commenting as.Not you?
Save information for future comments
Comment
Δ
Vlad Constantinescu
