Windows 10 Update Bugs, Latest News 2019: How to Fix Reboot Issues Caused by Latest Patch Tuesday

Another Windows 10 Update has once again sent personal computers going bonkers as reported by multiple users who have been affected by the recent fiasco. While the previous problem only affected certain users running a particular antivirus, the recent errors are freezing the computers of those wanting to restore their device to a time before the latest update was installed, Bleeping Computer reported.

This is problematic since the Windows 10 Update will not be able to return to the Windows desktop even after restarting the computer. Microsoft’s support document has provided information on why this is.

The Windows 10 Update is supposed to work by temporarily staging the restoration files that are being used before saving that information in the registry. When the computer is restarted, the staged operation is completed. Instead, this is what happened:

“In this situation, Windows restores the catalog files and stages the driver .sys files to be restored when the computer restarts. However, when the computer restarts, Windows loads the existing drivers before it restores the later versions of the drivers. Because the driver versions do not match the versions of the restored catalog files, the restart process stops.” For those who are affected by the latest Windows 10 Update, you can restore your system by following these steps.

First, restart the computer twice to force the Windows Recovery Environment (WinRE) to appear. From this window, click on Troubleshoot>Advanced options>More recovery options>Startup settings>Restart now. While there will be a number of startup setting that will pop up, what you’re looking for is disabling the “driver signature enforcement.” You may need to use the F7 key for this setting to come up. After following these steps, the Windows 10 Update may proceed as intended, and everything will return to normal, Forbes reported.

Of course, to completely dodge this headache, simply opt to not update to the May Patch Tuesday and wait it out after Microsoft has completely fixed the problem. It could be weeks before the next Windows 10 Update may roll out, but that’s better than dealing with this problematic issue at the moment.