Windows 10 forced reboot and BSOD bugs confirmed by Microsoft

Vlad Constantinescu
by Vlad Constantinescu
VPN Expert & Privacy Advocate
Affiliate Disclosure

  • Microsoft acknowledged the existence of two issues affecting users who upgrade to later versions of Windows 10, due to compatibility issues.
  • Reportedly, owners of affected systems may experience BSODs and even forced system reboots.
  • Check out our Windows 10 section for the latest news, updates, and how-to guides on the popular OS.
  • Visit our Microsoft Hub to discover more Microsoft-related news, events, and features.
Windows 10 BSOD forced reboot

Although Microsoft throttled 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 system crashes.

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 the operating system until 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

Device manager

Microsoft and Intel have identified some compatibility issues with Thunderbolt NVMe SSDs. Plugging such a device in after upgrading to Windows 10 2004 or 20H2 can lead to a BSOD.

Microsoft has 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 can trigger the BSOD if 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 experience BSODs and need to revert to a previous, working version of the operating system, which is not exactly a breeze to do.

Windows 10 force-reboots some systems

Yet another bug rendering your PC almost unusable is the forced reboot one that Microsoft recently confirmed. This one might seem a bit more forgiving than the BSOD one we described above, but it’s just as merciless regarding system usability.

After upgrading to Windows 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 this error. Therefore, you’ll need to roll back to a previous, stable version of Windows 10 to fix it.

As with the BSOD, Microsoft already 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 of Windows 10? Tell us all about your experience in the comments section below:

Leave a comment below!
6 comments

add a comment

Leave a Reply

Your email address will not be published. Required fields are marked *

Bill has once again proven that he has only his own interests at heart. Since the intro of WIN10, people have reported random reconfigs of their PC and phantom changes to their systems after updates (over which they have no real control) It is a PC for which the user has paid-including the OS. Why does a monster corp have the right to alter personal settings on a whim in a PC owner by someone else? Can anyone say Big Brother? I have wrestled with WIN10 for two weeks since I bought a new rig and been plagued by random resetting of everything from my Start menu to vanishing peripherals. One of my printers will still not reinstall after having worked initially due to ‘items in the print queue’ which is odd since I had nothing printed on that unit before it vanished after a random update. No amount of clearing the spooler or resetting, reinstalling, purging the unit from the system or any other standard fix seems to work. The system can’t find anything in the queue when attempting a purge yet finds something tha appears nowhere else when a reinstall of the hardware is attempted. WIN10 is toast. I’ll be migrating to Linux shortly. Bill appears to have gone too far in his attempts to rule the world and , I for one, refuse to participate. Remember, remember the fifth of November-V is for Vendetta.

ROTFLOL…. Bill appears to have gone too far?
Which era are you in?
Do you know that he’s not even on the board of directors for Microsoft since March?

Linux? =) …. you think that is a plug-and-play OS?
There is a reason Linux never took off for the mainstream. No wait, there’s a multitude of reasons.

Have fun with figuring out the command-lines, the linux packages, finding programs that work on linux, finding drivers for cutting edge hardware on Linux, since you can’t even get a printer to work on Windows.

i disagree. bill has left the board on march 2020 and for what? to focus on his charity organisation. Bill is a caring guy. with some tweeking to code he could have changed the world but no he’s not that type of guy. not the type who wants to rule the world. if he was he could have done it a long time ago.

Since the November update to Windows 10, KB4580419, my PC periodically encounters BSOD episodes, most typically occur when using standard wired hp mouse and/or wacom input device and after plugging in my network cable to the standard pc port. These input devices then lag and misbehave erratically. I now connect the cable only to work on line and hope to avoid BSODs. All other application work done off line. These errors have not been an issue until W10. I upgraded to Windows 10 a few months ago.

No problems with 20H2, installed two days ago. Z270, i5-7500, 32gb memory, RX 570, Two 1tb hard drives, three monitors.