[ad_1]
<div _ngcontent-c14 = "" innerhtml = "
Last month, I told how Windows 10 April "Patch Tuesday" updates were blocking some computers during the update process himself and prevent others from restarting afterwards. It now appears that the latest operating system updates are preventing new Windows 10 computers from restarting properly. Although Windows 10 users are not bothered by the "vermifuge" Remote Code Execution Vulnerability Fixed in the latest update, these patches also fix many other security issues each month; their importance should not be underestimated. This makes common problems with the update process even more difficult to swallow for long-time Windows 10 users.
What is happening?
The previous issue was only for users running some antivirus solutions, but this time, anyone. Or at least those who want to restore their computer at a time prior to the installation of the latest update of Windows 10. What is, let's face it, a fairly common scenario given the problematic nature of the update process. Bleeping Computer was the first to notice that Microsoft had updated a support document regarding problems restoring the system restore. As long as system protection is enabled in Windows 10 and you have created a system restore point before applying the latest update, you may be stuck out of your computer. Simple as. Microsoft confirmed that under these circumstances the computer may experience "a stop error (0xc000021a)" and when you restart the device "the system can not return to the Windows desktop." In other words, your computer is stuck in a failed restart scenario, caused by the Windows 10 update to protect your system from potential damage.
What's wrong?
Microsoft readily admits that this is "a known problem" in Windows 10. What really does not me to feel better, and you? The support document that I mentioned earlier indicates that the problem comes from the system restore process that organizes the restoration of files in use. This information is stored in the system registry and when restarted, the operation is completed. Or at least that's what should happen. In the restoration scenario on a restore point prior to the update, Windows stages the driver .sys files, and then loads the existing drivers. The most recent versions are loaded later. "The driver versions do not match the versions of the restored catalog files," Microsoft explains, "the restart process stops."
How do you correct that?
Restart the computer and enter the Windows Recovery Environment (WinRE), which should occur automatically after two unsuccessful attempts to boot Windows 10. In the WinRE screen, select "Troubleshoot Problems" | 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 make sure that you have selected "Disable Driver Signature Application." Microsoft advises you to use the F7 key to select this setting. The boot process will now begin and the system restore should resume and finish as expected.
How can you avoid the failure of the system restore?
The simplest answer is to switch to Linux. Readers of my articles have commented this in a familiar way about Windows 10 update issues. However, this is really not an option for most people, for many reasons. So, let's stick with the Windows 10 measures, are we going? & Nbsp; Instead of using the settings dialog to launch 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 in the Windows Recovery Environment, select "Troubleshoot | Advanced Options | System Restore" and follow the instructions in the wizard.
">
Last month, I reported that April's "April Patch" updates on April 10 blocked some computers during the update process and prevented others from restarting afterwards. It now appears that the latest operating system updates are preventing new Windows 10 computers from restarting properly. Although Windows 10 users are not worried about the "modifiable" remote code execution vulnerability corrected in the latest update, these fixes also fix many other security issues each month. Therefore, their importance is not underestimated. This makes common problems with the update process even more difficult to swallow for long-time Windows 10 users.
What is happening?
The previous issue was only for users running some antivirus solutions, but this time, anyone. Or at least those who want to restore their computer at a time prior to the installation of the latest Windows 10 update. Let's be realistic, which is a fairly common scenario given the problematic nature of the update process. Bleeping Computer was the first to notice that Microsoft had updated a support document regarding problems with restarting the system restore. As long as system protection is enabled in Windows 10 and you have created a system restore point before applying the latest update, you may be stuck out of your computer. Simple as. Microsoft confirms that under these circumstances, the computer may encounter "a stop error (0xc000021a)" and that when you restart the device, "the system can not return to the Windows desktop". In other words, your computer is stuck in a failed restart scenario, caused by the Windows 10 update to protect your system from potential damage.
What's wrong?
Microsoft readily acknowledges that it is "a known problem" in Windows 10. What really does not me to feel better, and you? The support document that I mentioned earlier indicates that the problem comes from the system restore process that organizes the restoration of files in use. This information is stored in the system registry and when restarted, the operation is completed. Or at least that's what should happen. In the restoration scenario on a restore point prior to the update, Windows stages the driver .sys files, and then loads the existing drivers. The most recent 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 correct that?
Restart the computer and enter the Windows Recovery Environment (WinRE), which should occur automatically after two unsuccessful attempts to boot Windows 10. In the WinRE screen, select "Troubleshooting | Options. Advanced | More Recovery Options | Startup Settings ", then select" Restart Now "option. A number of startup settings will be available and you need to make sure that you have selected "Disable driver signature application". Microsoft advises you to use the F7 key to select this setting. The boot process will now begin and the system restore should resume and finish as expected.
How can you avoid the failure of the system restore?
The simplest answer is to switch to Linux. Readers of my articles have commented this in a familiar way about Windows 10 update issues. However, this is really not an option for most people, for many reasons. So let's stay on Windows 10 measures are we going? Instead of using the settings dialog to launch the System Restore Wizard, use WinRE instead. You can do this from the Windows desktop by selecting "Start | Settings | Update and Security | Recovery", then selecting the "Restart Now" option in "Advanced Options". Once in the Windows Recovery Environment, select "Troubleshooting | Advanced Options | System Restore" and follow the instructions that appear.