Last month I reported how the April Windows 10 “Patch Tuesday” updates were freezing some computers during the update process itself and preventing others from rebooting afterwards. Now it appears that the latest operating system updates are once again preventing Windows 10 computers from rebooting properly. Although Windows 10 users are not troubled by the “wormable” remote code execution vulnerability fixed in the latest update, these patches also fix numerous other security issues each month and so their importance is not to be underestimated. Which makes the ongoing problems of the patching process even harder to swallow for long-suffering Windows 10 users.
The previous issue only involved users running certain antivirus solutions, but this time it’s anyone. Or at least anyone who wants to restore their computer back to a point before the latest Windows 10 update was installed. Which is, let’s face it, a pretty common scenario considering the problematical nature of the update process.
Bleeping Computer was first to spot that Microsoft had updated a support document regarding system restore reboot problems. As long as you have system protection turned on in Windows 10 and have created a system restore point before applying the latest update, then you are at risk of being frozen out of your computer. Simple as. Microsoft confirms that under those circumstances the computer may experience “a Stop error (0xc000021a)” and when you restart the device “the system cannot return to the Windows desktop.” In other words, your computer is borked in a failed reboot scenario caused by the Windows 10 update that is meant to protect your system from potential harm.
What’s gone wrong?
Microsoft readily admits that this is “a known issue” in Windows 10. Which really doesn’t make me feel any better, what about you? The support document I mentioned earlier states that the problem is down to the system restore process staging the restoration of those files that are in use. This information is stored in the system registry and upon reboot the staged operation is completed. Or at least that’s what should happen. In the scenario of restoring to a pre-update restore point, Windows stages the driver .sys files but then loads the existing drivers first and the later versions are loaded later. “Because the driver versions do not match the versions of the restored catalog files,” Microsoft explains, “the restart process stops.”
How do you fix it?
Restart the computer and enter the Windows Recovery Environment (WinRE) which should happen automatically after two consecutive failed attempts to start Windows 10. From the WinRE screen, select “Troubleshoot|Advanced options|More recovery options|Startup settings” and then the “Restart now” option. A number of startup settings will be available and you need to ensure you have selected “Disable driver signature enforcement.” Microsoft advises that the F7 key may need to be employed in order to select this setting. The startup process will now proceed and system restore should resume and complete as intended.
How can you avoid the system restore failure?
The glib answer is switch to Linux and this has, indeed, been a familiar comment from readers of my articles about Windows 10 update problems. However, that really isn’t an option for most people and for so many reasons. So let’s stick to Windows 10 measures shall we? Instead of using the settings dialog to start the system restore wizard, use WinRE instead. You can do this from your Windows desktop by selecting “Start|Settings|Update & Security|Recovery” and then selecting the “Restart now” option from “Advanced options.” Once within the Windows Recovery Environment, select “Troubleshoot|Advanced options|System restore” and follow the instructions in the wizard.
Closing month I reported how the April Windows 10 “Patch Tuesday” updates had been freezing some computer programs at some level of the replace job itself and stopping others from rebooting afterwards. Now it looks that the most modern operating machine updates are all once more stopping Windows 10 computer programs from rebooting successfully. Though Windows 10 customers are not vexed by the “wormable” faraway code execution vulnerability fixed in the most modern replace, these patches furthermore fix a enormous collection of different security complications each month and so their significance is now to not be underestimated. Which makes the continued complications of the patching job even more sturdy to swallow for long-struggling Windows 10 customers.
What’s going down?
The previous effort excellent alive to customers working obvious antivirus solutions, but this time or not it is someone. Or not decrease than someone who needs to restore their computer lend a hand to a few of extent sooner than the most modern Windows 10 replace used to be installed. Which is, let’s face it, a good total scenario pondering about the problematical nature of the replace job.
Bleeping Pc used to be first to space that Microsoft had up so some distance a crimson meat up file in relation to machine restore reboot complications. So long as you’ve gotten machine security modified into on in Windows 10 and non-public created a machine restore level sooner than making utilize of the most modern replace, then you definately are prone to being frozen out of your computer. Straightforward as. Microsoft confirms that underneath those conditions the computer would possibly perhaps maybe presumably furthermore simply skills “a Cease error (0xc000021a)” and while you restart the software program “the machine can not return to the Windows desktop.” In other words, your computer is borked in a failed reboot scenario prompted by the Windows 10 replace that is supposed to present protection to your machine from doable damage.
What’s gone defective?
Microsoft readily admits that here is “a known effort” in Windows 10. Which if fact be told would not save me feel any higher, what about you? The crimson meat up file I mentioned earlier states that the difficulty is the overall style down to the machine restore job staging the restoration of those files which shall be in utilize. This information is saved in the machine registry and upon reboot the staged operation is achieved. Or not decrease than that’s what must accumulated occur. Within the scenario of restoring to a pre-replace restore level, Windows phases the driving force .sys files but then loads the recent drivers first and the later variations are loaded later. “Since the driving force variations accomplish not match the variations of the restored catalog files,” Microsoft explains, “the restart job stops.”
How accomplish you fix it?
Restart the computer and enter the Windows Recovery Atmosphere (WinRE) which must accumulated occur automatically after two consecutive failed attempts to start Windows 10. From the WinRE conceal, take “Troubleshoot|Improved suggestions|More restoration suggestions|Startup settings” and then the “Restart now” option. A group of startup settings shall be on hand and or not it is well-known to save particular you’ve gotten selected “Disable driver signature enforcement.” Microsoft advises that the F7 key would possibly perhaps maybe presumably must accumulated be employed in snarl to lift this environment. The startup job will now proceed and machine restore must accumulated resume and full as supposed.
How will you live some distance from the machine restore failure?
The glib acknowledge is switch to Linux and this has, certainly, been a acquainted comment from readers of my articles about Windows 10 replace complications. Nonetheless, that really is not an option for heaps of folk and for so many causes. So let’s persist with Windows 10 measures shall we? As one more of utilizing the settings dialog to start the machine restore wizard, utilize WinRE as a change. It is likely you’ll perhaps presumably presumably furthermore accomplish this out of your Windows desktop by selecting “Originate|Settings|Replace & Security|Recovery” and then selecting the “Restart now” option from “Improved suggestions.” Once all the design thru the Windows Recovery Atmosphere, take “Troubleshoot|Improved suggestions|Machine restore” and be conscious the instructions in the wizard.