Posted on Monday, February 17 2020 @ 11:21 CET by Thomas De Maesschalck
Microsoft saw itself forced to pull another Windows 10 update. Last week's Patch Tuesday release pushed KB4524244 to Windows 10 users but this update is causing significant issues for a portion of users. The patch resolved an undisclosed security vulnerability with third-party UEFI boot managers. On its support pages, Microsoft explains the update can cause the push button reset to fail. This feature of Windows 10 enables you to restore a clean copy of Windows 10, which can be useful in case things go horribly wrong with your PC's configuration. The patch can also cause system hangs, crashes, and freezes.
This standalone security update has been removed due to an issue affecting a sub-set of devices. It will not be re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note Removal of this standalone security update does not affect successful installation or any changes within any other February 11, 2020 security updates, including Latest Cumulative Update (LCU), Monthly Rollup or Security Only update.
Using the “Reset this PC” feature, also called “Push Button Reset” or PBR, might fail. You might restart into recovery with “Choose an option” at the top of the screen with various options or you might restart to desktop and receive the error “There was a problem resetting your PC”.
If you have already installed the patch, you can remove it by uninstalling KB4524244 via "View your update history". You can reach this menu by typing "update history" into the Windows 10 Start Menu:
If you have installed this update and are experiencing this issue, the following steps should allow you to reset your device:
Select the start button or Windows Desktop Search and type update history and select View your Update history.
On the Settings/View update history dialog window, Select Uninstall Updates.
On the Installed Updates dialog window, find and select KB4524244 and select the Uninstall button.
Restart your device.
Upon restart use the “Reset this PC” feature and you should not encounter this issue.
