deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-15 18:33:43 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Update update-compliance-feature-update-status.md

Browse Source 
1. Changed the term "compatibility hold" to "safeguard hold" since this is the terminology we are going to use going forward as approved by the Comms team.
2. Added the "Queries for Safeguard holds" section. Unable to upload the UC_workspace_safeguard_queries.png file in images folder, so will email the image to Jaime to upload.
This commit is contained in:
mesharma-msft
2020-08-12 17:02:16 -07:00
committed by GitHub
parent 23e1e195a4
commit 708928095c
1 changed files with 12 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
windows/deployment/update/update-compliance-feature-update-status.md
View File

@ -35,14 +35,22 @@ Refer to the following list for what each state means:
* Devices that have failed the given feature update installation are counted as **Update failed**.
* If a device should be, in some way, progressing toward this security update, but its status cannot be inferred, it will count as **Status Unknown**. Devices not using Windows Update are the most likely devices to fall into this category.
## Compatibility holds
## Safeguard holds
Microsoft uses diagnostic data to determine whether devices that use Windows Update are ready for a feature update in order to ensure a smooth experience. When Microsoft determines a device is not ready to update due to a known issue, a *compatibility hold* is generated to delay the device's upgrade and safeguard the end-user experience. Holds are released over time as diagnostic data is analyzed and fixes are addressed. Details are provided on some, but not all compatibility holds on the Windows 10 release information page for any given release.
### Opting out of compatibility hold
## Queries for Safeguard holds
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**.
With Update Compliance reporting, there are now two available queries to help you retrieve data related to Safeguard Holds. The first query shows the device data for all devices that are impacted by safeguard holds. The second query shows data specific to target build distribution of devices.
![Safeguard hold queries](images/UC_workspace_safeguard_queries.png)
Update Compliance reporting will surface the Safeguard IDs for known issues impacting a device in the ‘DeploymentErrorCode’ column. Safeguard IDs for publicly discussed known issues will also be included in the Windows Release Health Dashboard, enabling easy lookup of information related to publicly available safeguards.
### Opting out of safeguard hold
Microsoft will release a device from a safeguard 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**.
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.
Setting this registry key to **0** will force the device to opt out from *all* safeguard holds. Any other value, or deleting the key, will resume compatibility protection on the device.