قالب وردپرس درنا توس
Home https://server7.kproxy.com/servlet/redirect.srv/sruj/smyrwpoii/p2/ Technology https://server7.kproxy.com/servlet/redirect.srv/sruj/smyrwpoii/p2/ Microsoft Updates Invites Are Freezing Windows 10 Computers – Again

Microsoft Updates Invites Are Freezing Windows 10 Computers – Again



<div _ngcontent-c1

4 = "" innerhtml = "

Getty

Last month I reported how April Windows 10" Patch Tuesday " ] the updates are freezing on some computers during the update process itself and prevents others from rebooting after Today It appears that the latest operating system updates are re- preventing Windows 10 computers from rebooting properly.There is no wormable "wormable" remote code enforcement vulnerability fixed in the latest update, patches also fix many other security issues per months and so their importance is no longer underestimated. The makers of the ongoing problem of patching processes are even harder to devour for the long-suffering of Windows 10.

What's happening? [19659007] The previous issue is only involved with users running on some antivirus solutions, but this time I'm anyone. Or at least anyone who wants to restore their computer back to a point before installing the latest Windows update 10. Which is, let's face it, a typical situation taking into account the problematic nature of the process -update .

The Bleeping Computer first saw that Microsoft updated a support document regarding the system restore reboot problem. You do not have system protection turned on in Windows 10 and create a point restoration system before applying the latest update, then you're at risk of being frozen outside of your computer. Simple number. Microsoft confirms that under these circumstances the computer may encounter "the Stop error (0xc000021a)" and when you restart the device "the system can not return to the Windows desktop." In other words, your computer is borked in a failed reboot situation caused by Windows 10 update that was meant to protect your system from potential harm.

Microsoft immediately admitted it was " a known issue "in Windows 10. I did not really do anything better, what about you? The supporting document I mentioned earlier says the problem is down the system of restoration of the playback process of the restoring files used. This information is stored on the system registry and on reboot the completed operation is completed. Or at least that should be it happens. In the restore situation in a pre-update restore point, Windows is pursuing the driver .sys file but then the existing drivers are loading first and the next versions are loaded later. "Because the driver versions do not match the restored versions of the catalog files," Microsoft explains, "the restart process stops."

How do you fix it?

and enter the Windows Recovery Environment (WinRE) that will automatically occur after two successive failed attempts to start Windows 10. From the WinRE screen, select "Troubleshoot | Advanced options | More options recovery | startup settings "" Restart now "option. A number of startup settings are available and you need to make sure you choose "Disable the implementation of the driver's signature." Microsoft recommends that the F7 key may be required to be used to select this setting. The startup process will continue now and the restoration system should continue and complete as intended.

How can you prevent the system from returning to failure?

The glib answer is moving to Linux and this is, in fact, a familiar comment from readers of my articles about Windows update problems 10. However, this is definitely not an option for to the majority of people and for so many reasons. So we do not have to stay in Windows 10 proposals should we? & Nbsp; 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 select "Restart now" option from "Advanced options." Once you are within the Windows Recovery Environment, select "Troubleshoot | Advanced options | System restore" and follow the instructions in the wizard.

">

Last month I reported how the April 10 update of Windows 10 "Patch Tuesday" was freezing on some computers during the update itself and preventing others from rebooting afterwards. Now it appears that the latest operating system updates have been preventing Windows 10 computers from rebooting properly. Although Windows 10 users are not disturbed by the "wormable" remote code implementation vulnerabilities fixed in the latest update, patches also fix many other security issues each month and so their importance is not underestimated. Indicating the ongoing problems of the patching process is more difficult to swallow the long-suffering of Windows 10.

What's happening?

The previous issue is only involved with users running several antivirus solutions, but this time anyone is. Or at least anyone who wants to restore their computer back to a point before installing the latest Windows update 10. Which is, let's face it, a very generous situation that takes into account the problematic nature of the process of development. update.

Bleeping Computer has first seen that Microsoft has updated a support document regarding the system to restore the reboot problems. You do not have system protection turned on in Windows 10 and create a point restoration system before applying the latest update, then you're at risk of being frozen outside of your computer. Simple number. Microsoft confirms that under those 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 borked in a failed reboot situation caused by Windows 10 update that is meant to protect your system from potential harm.

What's gone?

Microsoft easily recognizes this "a known issue" in Windows 10. Which did not really make feeling any better, what about you? The supporting document I mentioned earlier indicates that the problem is down to the system restore process of the playback process of the files used. This information is stored on the system registry and on reboot the completed operation is completed. Or at least that should happen. In the restore situation in a pre-update restore point, Windows is pursuing the driver .sys file but then the existing drivers are loading first and the next versions are loaded later. "Since the driver versions do not match the versions of the restored catalog files," explains Microsoft, "the restart process will stop."

How do you fix it?

Restart the computer and enter the Windows Recovery Environment that will happen automatically after two successive failed attempts to start Windows 10. From the WinRE screen, select "Troubleshoot | Advanced options | over more recovery options | Startup settings "and then the" Restart now "option. A number of startup settings are available and you need to make sure that you have selected "Disable driving signature enforcement." Microsoft recommends that the F7 key may be required to be used to select this setting. The startup process will continue now and the restoration system should continue and complete as intended.

How can you prevent the system from returning to failure?

The glib answer is moving to Linux and this is, in fact, a familiar comment from readers of my articles about Windows update problems 10. However, this is definitely not an option for to the majority of people and for so many reasons. So are we staying in Windows 10's plans we will do? 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 select the "Restart now" option from "Advanced options." Once inside the Windows Recovery Environment, select "Troubleshoot | Advanced options | System restore" and follow the instructions in the wizard.


Source link