Microsoft Admits Updates Are Freezing Windows 10 Computers - Again

A month ago I detailed how the April Windows 10 "Fix Tuesday" refreshes were cold a few PCs amid the update procedure itself and keeping others from rebooting a while later. Presently it creates the impression that the most recent working framework refreshes are by and by keeping Windows 10 PCs from rebooting appropriately.

In spite of the fact that Windows 10 clients are not disturbed by the "wormable" remote code execution powerlessness fixed in the most recent update, these patches additionally fix various other security issues every month thus their significance isn't to be thought little of. Which makes the continuous issues of the fixing procedure considerably harder to swallow for lenient Windows 10 clients.

What's going on?

The past issue just included clients running certain antivirus arrangements, yet this time it's anybody. Or if nothing else any individual who needs to reestablish their PC back to a point before the most recent Windows 10 update was introduced. Which is, let's be honest, a really regular situation considering the problematical idea of the update procedure.

Bleeping Computer was first to recognize that Microsoft had refreshed a help report with respect to framework reestablish reboot issues. For whatever length of time that you have framework insurance turned on in Windows 10 and have made a framework reestablish point before applying the most recent update, at that point you are in danger of being solidified out of your PC. Straightforward as. Microsoft affirms that under those conditions the PC may encounter "a Stop blunder (0xc000021a)" and when you restart the gadget "the framework can't come back to the Windows work area." as it were, your PC is borked in a fizzled reboot situation brought about by the Windows 10 update that is intended to shield your framework from potential damage.

What's turned out badly?

Microsoft promptly concedes this is "a known issue" in Windows 10. Which truly doesn't make me feel any better, shouldn't something be said about you? The help archive I referenced before states that the issue is down to the framework reestablish process organizing the reclamation of those documents that are being used.

This data is put away in the framework library and upon reboot the organized activity is finished. Or if nothing else that is the thing that ought to occur. In the situation of reestablishing to a pre-update reestablish point, Windows arranges the driver .sys documents yet then loads the current drivers first and the later forms are stacked later. "Since the driver adaptations don't coordinate the variants of the reestablished index records," Microsoft clarifies, "the restart procedure stops."

How would you fix it?

Restart the PC and enter the Windows Recovery Environment (WinRE) which ought to happen naturally after two back to back fizzled endeavors to begin Windows 10. From the WinRE screen, select "Troubleshoot|Advanced options|More recuperation options|Startup settings" and after that the "Restart now" choice.

Various startup settings will be accessible and you have to guarantee you have chosen "Debilitate driver signature implementation." Microsoft exhorts that the F7 key may should be utilized so as to choose this setting. The startup procedure will currently continue and framework reestablish should continue and finish as planned.

How might you stay away from the framework reestablish disappointment?

The chatty answer is change to Linux and this has, for sure, been a well-known remark from perusers of my articles about Windows 10 update issues. In any case, that truly isn't a possibility for the vast majority and for such huge numbers of reasons.

So we should stick to Windows 10 measures will we? Rather than utilizing the settings discourse to begin the framework reestablish wizard, use WinRE. You can do this from your Windows work area by choosing "Start|Settings|Update and Security|Recovery" and after that choosing the "Restart now" choice from "Cutting edge alternatives." Once inside the Windows Recovery Environment, select "Troubleshoot|Advanced options|System reestablish" and adhere to the guidelines in the wizard.