From ae42af9fdcb377815e91e8ddbfaf2e70eb99824d Mon Sep 17 00:00:00 2001 From: jaimeo Date: Fri, 17 May 2019 08:53:09 -0700 Subject: [PATCH 1/6] import of new material on compatibility holds --- .../update-compliance-feature-update-status.md | 13 +++++++++++++ .../update/update-compliance-perspectives.md | 6 ++++++ 2 files changed, 19 insertions(+) diff --git a/windows/deployment/update/update-compliance-feature-update-status.md b/windows/deployment/update/update-compliance-feature-update-status.md index 4dbf3ca380..3587c79cbd 100644 --- a/windows/deployment/update/update-compliance-feature-update-status.md +++ b/windows/deployment/update/update-compliance-feature-update-status.md @@ -32,3 +32,16 @@ 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 + +Microsoft usesw diagnostic data to determine whether devices that use Windows Update are ready for an 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. + +To learn how compatibility holds are reflected in the experience, see [Update compliance perspectives](update-compliance-perspectives#deployment-status). + +### 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** to 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. + diff --git a/windows/deployment/update/update-compliance-perspectives.md b/windows/deployment/update/update-compliance-perspectives.md index f0403b00c8..9f02e47ed0 100644 --- a/windows/deployment/update/update-compliance-perspectives.md +++ b/windows/deployment/update/update-compliance-perspectives.md @@ -23,6 +23,8 @@ The first blade is the **Build Summary** blade. This blade summarizes the most i The second blade is the **Deferral Configurations** blade, breaking down Windows Update for Business deferral settings (if any). +## Deployment status + The third blade is the **Deployment Status** blade. This defines how many days it has been since the queried version has been released, and breaks down the various states in the update funnel each device has reported to be in. The possible states are as follows: | State | Description | @@ -30,12 +32,15 @@ The third blade is the **Deployment Status** blade. This defines how many days i | Update Completed | When a device has finished the update process and is on the queried update, it will display here as Update completed. | | In Progress | Devices that report they are “In Progress” are one of the various stages of installing an update; these stages are reported in the Detailed Deployment Status blade. | | Deferred | When a device’s Windows Update for Business deferral policy dictates that the update is not yet applicable due to deferral, it will report as such in this blade. | +| Compatibility hold | The device has been placed under a *cmpatibility hold* to ensure a smooth feature update experience and will not resume the update until the hold has been cleared, for more information see [Feature Update Status report](update-compliance-feature-update-status#) | | Progress stalled | Devices that report as “Progress stalled” have been stuck at “In progress” for more than 7 days. | | Cancelled | The update was cancelled. | | Blocked | There is a hard block on the update being completed. This could be that another update must be completed before this one, or some other task is blocking the installation of the update. | | Unknown | Devices that do not report detailed information on the status of their updates will report Unknown. This is most likely devices that do not use Windows Update for deployment. | | Update paused | These devices have Windows Update for Business pause enabled, preventing this update from being installed. | +## Detailed deployment status + The final blade is the **Detailed Deployment Status** blade. This blade breaks down the detailed stage of deployment a device is in, beyond the generalized terms defined in Deployment Status. The following are the possible stages a device can report: | State | Description | @@ -44,6 +49,7 @@ The final blade is the **Detailed Deployment Status** blade. This blade breaks d | Update paused | The device’s Windows Update for Business policy dictates the update is paused from being offered. | | Update offered | The device has been offered the update, but has not begun downloading it. | | Pre-Download tasks passed | The device has finished all necessary tasks prior to downloading the update. | +| Compatibility hold | The device has been placed under a *cmpatibility hold* to ensure a smooth feature update experience and will not resume the update until the hold has been cleared, for more information see [Feature Update Status report](update-compliance-feature-update-status#) | | Download Started | The update has begun downloading on the device. | | Download Succeeded | The update has successfully completed downloading. | | Pre-Install Tasks Passed | Tasks that must be completed prior to installing the update have been completed. | From 96725bbcd2c005c202f75864c5b395600fa7bb93 Mon Sep 17 00:00:00 2001 From: jaimeo Date: Fri, 17 May 2019 09:18:13 -0700 Subject: [PATCH 2/6] fixing crosslinks --- .../update/update-compliance-feature-update-status.md | 2 +- windows/deployment/update/update-compliance-perspectives.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/windows/deployment/update/update-compliance-feature-update-status.md b/windows/deployment/update/update-compliance-feature-update-status.md index 3587c79cbd..f9b26f8340 100644 --- a/windows/deployment/update/update-compliance-feature-update-status.md +++ b/windows/deployment/update/update-compliance-feature-update-status.md @@ -36,7 +36,7 @@ Refer to the following list for what each state means: Microsoft usesw diagnostic data to determine whether devices that use Windows Update are ready for an 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. -To learn how compatibility holds are reflected in the experience, see [Update compliance perspectives](update-compliance-perspectives#deployment-status). +To learn how compatibility holds are reflected in the experience, see [Update compliance perspectives](update-compliance-perspectives.md#deployment-status). ### Opting out of compatibility hold diff --git a/windows/deployment/update/update-compliance-perspectives.md b/windows/deployment/update/update-compliance-perspectives.md index 9f02e47ed0..611b8a05df 100644 --- a/windows/deployment/update/update-compliance-perspectives.md +++ b/windows/deployment/update/update-compliance-perspectives.md @@ -32,7 +32,7 @@ The third blade is the **Deployment Status** blade. This defines how many days i | Update Completed | When a device has finished the update process and is on the queried update, it will display here as Update completed. | | In Progress | Devices that report they are “In Progress” are one of the various stages of installing an update; these stages are reported in the Detailed Deployment Status blade. | | Deferred | When a device’s Windows Update for Business deferral policy dictates that the update is not yet applicable due to deferral, it will report as such in this blade. | -| Compatibility hold | The device has been placed under a *cmpatibility hold* to ensure a smooth feature update experience and will not resume the update until the hold has been cleared, for more information see [Feature Update Status report](update-compliance-feature-update-status#) | +| Compatibility hold | The device has been placed under a *cmpatibility hold* to ensure a smooth feature update experience and will not resume the update until the hold has been cleared, for more information see [Feature Update Status report](update-compliance-feature-update-status.md#compatibility-holds) | | Progress stalled | Devices that report as “Progress stalled” have been stuck at “In progress” for more than 7 days. | | Cancelled | The update was cancelled. | | Blocked | There is a hard block on the update being completed. This could be that another update must be completed before this one, or some other task is blocking the installation of the update. | @@ -49,7 +49,7 @@ The final blade is the **Detailed Deployment Status** blade. This blade breaks d | Update paused | The device’s Windows Update for Business policy dictates the update is paused from being offered. | | Update offered | The device has been offered the update, but has not begun downloading it. | | Pre-Download tasks passed | The device has finished all necessary tasks prior to downloading the update. | -| Compatibility hold | The device has been placed under a *cmpatibility hold* to ensure a smooth feature update experience and will not resume the update until the hold has been cleared, for more information see [Feature Update Status report](update-compliance-feature-update-status#) | +| Compatibility hold | The device has been placed under a *cmpatibility hold* to ensure a smooth feature update experience and will not resume the update until the hold has been cleared, for more information see [Feature Update Status report](update-compliance-feature-update-status.md#compatibility-holds) | | Download Started | The update has begun downloading on the device. | | Download Succeeded | The update has successfully completed downloading. | | Pre-Install Tasks Passed | Tasks that must be completed prior to installing the update have been completed. | From 0452abec2404cb666d908f4130d5010123785001 Mon Sep 17 00:00:00 2001 From: jaimeo Date: Fri, 17 May 2019 09:39:26 -0700 Subject: [PATCH 3/6] fixing typo --- .../update/update-compliance-feature-update-status.md | 2 +- 1 file changed, 1 insertion(+), 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 f9b26f8340..6e0fd2826b 100644 --- a/windows/deployment/update/update-compliance-feature-update-status.md +++ b/windows/deployment/update/update-compliance-feature-update-status.md @@ -34,7 +34,7 @@ Refer to the following list for what each state means: ## Compatibility holds -Microsoft usesw diagnostic data to determine whether devices that use Windows Update are ready for an 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 an 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. To learn how compatibility holds are reflected in the experience, see [Update compliance perspectives](update-compliance-perspectives.md#deployment-status). From c24e93753c9c66333c686cdef74beadf8010c8ae Mon Sep 17 00:00:00 2001 From: jaimeo Date: Mon, 20 May 2019 10:55:42 -0700 Subject: [PATCH 4/6] fixed typo; removed compatibility hold from deployment status table; added failed to deployment status table --- .../update/update-compliance-feature-update-status.md | 2 +- windows/deployment/update/update-compliance-perspectives.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/windows/deployment/update/update-compliance-feature-update-status.md b/windows/deployment/update/update-compliance-feature-update-status.md index 6e0fd2826b..c05f84ec04 100644 --- a/windows/deployment/update/update-compliance-feature-update-status.md +++ b/windows/deployment/update/update-compliance-feature-update-status.md @@ -40,7 +40,7 @@ To learn how compatibility holds are reflected in the experience, see [Update co ### 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** to 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 **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. diff --git a/windows/deployment/update/update-compliance-perspectives.md b/windows/deployment/update/update-compliance-perspectives.md index 611b8a05df..641894f55a 100644 --- a/windows/deployment/update/update-compliance-perspectives.md +++ b/windows/deployment/update/update-compliance-perspectives.md @@ -32,12 +32,12 @@ The third blade is the **Deployment Status** blade. This defines how many days i | Update Completed | When a device has finished the update process and is on the queried update, it will display here as Update completed. | | In Progress | Devices that report they are “In Progress” are one of the various stages of installing an update; these stages are reported in the Detailed Deployment Status blade. | | Deferred | When a device’s Windows Update for Business deferral policy dictates that the update is not yet applicable due to deferral, it will report as such in this blade. | -| Compatibility hold | The device has been placed under a *cmpatibility hold* to ensure a smooth feature update experience and will not resume the update until the hold has been cleared, for more information see [Feature Update Status report](update-compliance-feature-update-status.md#compatibility-holds) | | Progress stalled | Devices that report as “Progress stalled” have been stuck at “In progress” for more than 7 days. | | Cancelled | The update was cancelled. | | Blocked | There is a hard block on the update being completed. This could be that another update must be completed before this one, or some other task is blocking the installation of the update. | | Unknown | Devices that do not report detailed information on the status of their updates will report Unknown. This is most likely devices that do not use Windows Update for deployment. | | Update paused | These devices have Windows Update for Business pause enabled, preventing this update from being installed. | +| Failed | {WHAT DESCRIPTION FOR FAILED?} | ## Detailed deployment status @@ -49,7 +49,7 @@ The final blade is the **Detailed Deployment Status** blade. This blade breaks d | Update paused | The device’s Windows Update for Business policy dictates the update is paused from being offered. | | Update offered | The device has been offered the update, but has not begun downloading it. | | Pre-Download tasks passed | The device has finished all necessary tasks prior to downloading the update. | -| Compatibility hold | The device has been placed under a *cmpatibility hold* to ensure a smooth feature update experience and will not resume the update until the hold has been cleared, for more information see [Feature Update Status report](update-compliance-feature-update-status.md#compatibility-holds) | +| Compatibility hold | The device has been placed under a *compatibility hold* to ensure a smooth feature update experience and will not resume the update until the hold has been cleared. For more information see [Feature Update Status report](update-compliance-feature-update-status.md#compatibility-holds) | | Download Started | The update has begun downloading on the device. | | Download Succeeded | The update has successfully completed downloading. | | Pre-Install Tasks Passed | Tasks that must be completed prior to installing the update have been completed. | From a4a39290f399bcd210b116ff6745b9b360302932 Mon Sep 17 00:00:00 2001 From: jaimeo Date: Mon, 20 May 2019 12:01:32 -0700 Subject: [PATCH 5/6] updated failure state description --- windows/deployment/update/update-compliance-perspectives.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/update/update-compliance-perspectives.md b/windows/deployment/update/update-compliance-perspectives.md index 641894f55a..e08be87ab9 100644 --- a/windows/deployment/update/update-compliance-perspectives.md +++ b/windows/deployment/update/update-compliance-perspectives.md @@ -37,7 +37,7 @@ The third blade is the **Deployment Status** blade. This defines how many days i | Blocked | There is a hard block on the update being completed. This could be that another update must be completed before this one, or some other task is blocking the installation of the update. | | Unknown | Devices that do not report detailed information on the status of their updates will report Unknown. This is most likely devices that do not use Windows Update for deployment. | | Update paused | These devices have Windows Update for Business pause enabled, preventing this update from being installed. | -| Failed | {WHAT DESCRIPTION FOR FAILED?} | +| Failed | A device is unable to install an update. This failure could be linked to a serious error in the update installation process or, in some cases, a [compatibility hold](update-compliance-feature-update-status.md#compatibility-holds). | ## Detailed deployment status From 6cfd8b11ae20d6ffd5cf360dae6041aec51b2de9 Mon Sep 17 00:00:00 2001 From: jaimeo Date: Tue, 21 May 2019 08:50:45 -0700 Subject: [PATCH 6/6] fixing a typo --- .../update/update-compliance-feature-update-status.md | 2 +- 1 file changed, 1 insertion(+), 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 c05f84ec04..d2b2333afa 100644 --- a/windows/deployment/update/update-compliance-feature-update-status.md +++ b/windows/deployment/update/update-compliance-feature-update-status.md @@ -34,7 +34,7 @@ Refer to the following list for what each state means: ## Compatibility holds -Microsoft uses diagnostic data to determine whether devices that use Windows Update are ready for an 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 *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. To learn how compatibility holds are reflected in the experience, see [Update compliance perspectives](update-compliance-perspectives.md#deployment-status).