From 91e2c596b4b856cc70a027fcccec51775d30ec39 Mon Sep 17 00:00:00 2001 From: VARADHARAJAN K <3296790+RAJU2529@users.noreply.github.com> Date: Tue, 11 Aug 2020 22:09:13 +0530 Subject: [PATCH] added key path , mad words in bold as per the user report #8028 , so i modified this article by adding certain words, added key paths. --- .../update/update-compliance-feature-update-status.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/windows/deployment/update/update-compliance-feature-update-status.md b/windows/deployment/update/update-compliance-feature-update-status.md index 5953fcc349..143e1075a8 100644 --- a/windows/deployment/update/update-compliance-feature-update-status.md +++ b/windows/deployment/update/update-compliance-feature-update-status.md @@ -41,7 +41,13 @@ Microsoft uses diagnostic data to determine whether devices that use Windows Upd ### Opting out of compatibility hold -Microsoft will release a device from a compatibility hold when it has determined it can safely and smoothly install a feature update, but you are ultimately in control of your devices and can opt out if desired. To opt out, set the registry key **HKLM\Software\Microsoft\Windows NT\CurrentVersion\502505fe-762c-4e80-911e-0c3fa4c63fb0** to a name of **DataRequireGatedScanForFeatureUpdates** and a value of **0**. +Microsoft will release a device from a compatibility hold when it has determined it can safely and smoothly install a feature update, but you are ultimately in control of your devices and can opt out if desired. +To opt out, set the registry key as follows +- Registry Key Path :: **Computer\HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion** +- Create New Key :: **502505fe-762c-4e80-911e-0c3fa4c63fb0** +- Name :: **DataRequireGatedScanForFeatureUpdates** +- Type :: **REG_DWORD** +- Value :: **0** Setting this registry key to **0** will force the device to opt out from *all* compatibility holds. Any other value, or deleting the key, will resume compatibility protection on the device.