If you add a DWORD 32-bit value DisableWUfBSafeguards and set it to 1, the upgrade locks of Windows Update are bypassed.īut note the risk of unlocking the upgrade lock set by Microsoft. HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate This policy is available for Windows Update for Business (WUfB) with Windows 10 version 1809 or higher, provided the security update from October 2020 has been installed.īleeping Computer had taken up the topic promptly in this article and points out that you can also access the following registry branch via the registry editor:
Then activated the Group Policy Disable safeguards for Feature Updates and have the policy updated (for example, by rebooting or by running the gpupdate /force command from an administrative command prompt) Start gpedit.msc with administrative permissions and navigate in the Group Policy Editor's left pane to the branch:Ĭomputer Configuration > Administrative Templates > Windows Components > Windows Update > Windows Update for BusinessĢ. The easiest way in Windows 10 Pro, Enterprise and Education is to enable the relevant Group Policy.ġ. There are several ways to do this, which Microsoft describes in the article Opt out of safeguard holds.
However, administrators in enterprise environments can deactivate this upgrade lock in Windows 10 via Group Policy. Removing the upgrade lock (safeguard hold) More information about such locks can be found here. Microsoft removes these locks once a fix for the compatibility issue is released and verified on an affected device. Microsoft uses these locks to protect the device and the user from a failed or poor update experience. These safeguard holds prevent a device with a known compatibility issue from being offered a new Windows 10 feature update using Windows Update. The user then receives the following notification in Windows Update. In such cases, the feature update will be blocked in Windows Update (known as Safeguard holds) for these machines. When installing feature updates, there are always machines that Microsoft knows have hardware or software compatibility issues with the new Windows 10 version. Then on October 22, 2020, Microsoft published the article Opt out of safeguard holds on the topic, so I'll bring it up now. I wrote down the value of DisableWUfBSafeguards, but did not pursue the topic any further.
I've had this topic on my radar for about a month now because someone on Facebook had given me the hint 'you know the registry keys to remove an upgrade blocker rule'.
0 kommentar(er)
