From c24e93753c9c66333c686cdef74beadf8010c8ae Mon Sep 17 00:00:00 2001 From: jaimeo Date: Mon, 20 May 2019 10:55:42 -0700 Subject: [PATCH] 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. |