From 708928095c6dd98fbfde6b72fd6d37f73c85ebd4 Mon Sep 17 00:00:00 2001 From: mesharma-msft <69322487+mesharma-msft@users.noreply.github.com> Date: Wed, 12 Aug 2020 17:02:16 -0700 Subject: [PATCH 1/2] Update update-compliance-feature-update-status.md 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. --- .../update-compliance-feature-update-status.md | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-) diff --git a/windows/deployment/update/update-compliance-feature-update-status.md b/windows/deployment/update/update-compliance-feature-update-status.md index 5953fcc349..64c4b2a028 100644 --- a/windows/deployment/update/update-compliance-feature-update-status.md +++ b/windows/deployment/update/update-compliance-feature-update-status.md @@ -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. From 68e7fe75cfa4d3f0e3fbafab3c2d5f467792a6c4 Mon Sep 17 00:00:00 2001 From: Jaime Ondrusek Date: Thu, 13 Aug 2020 09:03:55 -0700 Subject: [PATCH 2/2] Update update-compliance-feature-update-status.md Fixing some style issues. --- .../update-compliance-feature-update-status.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/windows/deployment/update/update-compliance-feature-update-status.md b/windows/deployment/update/update-compliance-feature-update-status.md index 64c4b2a028..0fa0b2283e 100644 --- a/windows/deployment/update/update-compliance-feature-update-status.md +++ b/windows/deployment/update/update-compliance-feature-update-status.md @@ -37,19 +37,19 @@ Refer to the following list for what each state means: ## 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. +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 *safeguard hold* is generated to delay the device's upgrade and protect 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 safeguard holds on the Windows 10 release information page for any given release. -## Queries for Safeguard holds +## Queries for safeguard holds -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. +Update Compliance reporting offers two queries to help you retrieve data related to safeguard holds. The first query shows the device data for all devices that are affected by safeguard holds. The second query shows data specific to devices running the target build. -![Safeguard hold queries](images/UC_workspace_safeguard_queries.png) +![Left pane showing Need Attention, Security update status, feature update status, and Windows Defender AV status, with Need Attention selected. Right pane shows the list of queries relevant to the Need Attention status, with "Devices with a safeguard hold" and "Target build distribution of devices with a safeguard hold" queries highlighted](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. +Update Compliance reporting will display the Safeguard IDs for known issues affecting a device in the **DeploymentErrorCode** column. Safeguard IDs for publicly discussed known issues are also included in the Windows Release Health dashboard, where you can easily find 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**. +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. 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* safeguard holds. Any other value, or deleting the key, will resume compatibility protection on the device.