Nov 19 2020 09:40 AM
Nov 19 2020 09:40 AM
We have people stuck on 1909 because of Conexant drivers. Dell is no help in letting us know what is going on. When will this be resolved? https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-2004#377msgdesc in the patching community we have a lot of people stuck with no info as to when and how this will be resolved
Dec 09 2020 09:58 AM
Dec 15 2020 11:14 AM
@Susan Bradley Thanks for bringing this question to the office hours for IT professionals here on Tech Community. Please check latest update on this known issue published on the Windows release health dashboard last Friday (12/11): Windows 10, version 2004 and Windows Server, version 2004 | Microsoft Docs.
Let me know if have additional questions.
Dec 17 2020 09:21 AM
Access Safeguard hold details with Update Compliance Access safeguard hold details with Update Compliance - Microsoft Tech Community
What are Safeguards?
Safeguard holds prevent a PC with a known compatibility issue from being offered a new OS version. The offering will proceed once a fix is issued and is verified on a held device. The aim of safeguards is to protect the device and user from a failed or poor upgrade experience.
The safeguard holds protection is provided by default to all devices trying to update to OS version 1903 or higher via Windows Update. IT Pros can opt-out their devices from safeguard protection using the DisableWUfBSafeguards policy that can be implemented via a GP (Group Policy) or CSP (Configuration Service Provider).
Commercial customers can opt-out of Safeguards beginning in 9C by setting the DisableWUfBSafeguards policy. Content will be posted on docs after 9C, please refer to section “UpdatePolicyReader support for DisableWUfBSafegaurds”.
This policy will be added in Windows 10 version 2004. This policy will be applicable to all Windows Update for Business devices. Enabling the DisableWUfBSafeguards policy will disable the safeguards so that devices will install the update without the protection, thereby allowing IT Pros to deploy the feature update to devices without blocking on Safeguards. After an update, all devices are protected by safeguards by default, even if the policy was enabled prior to an update. We do this to protect the devices from any new compatibility issues specific to the new OS version. To turn off the protection post an update, the policy will have to be enabled/set.
Enterprise users can now gain information on the safeguards that block their devices from upgrading to a new OS version with the help of IDs displayed in the Update Compliance report and on the Windows Release health dashboard for known issues.
Up until now, the enterprise users were aware of the devices that were blocked from upgrades due to safeguard holds but they was no way to know exactly which individual safeguard was impacting devices. This new feature enhancement addresses this customer pain point. Now onwards, with access to safeguard related information, enterprise customers will be more informed of why Microsoft blocked their devices from upgrading and will be in-control to opt-out of this protection should they choose to do so.
Update Compliance reporting additions
The Update Compliance report now has queries specific to safeguard holds. The query result shows Safeguard Hold IDs impacting enterprise customers' devices.
The Update Compliance report now has the IDs of all safeguards that impact enterprise devices. These IDs are a part of the “Deployment Error Code” column. The report has other information such as device details including device name and ID, the error description and OS version and OS build for every device listed.
Addition to Windows release health dashboard
The Safeguard IDs are now also a part of all safeguard hold related information content shown on the Windows release health dashboard. Enterprise customers will be able to look up safeguard details on the Windows dashboard via IDs listed in the Update Compliance reporting solution.
Dec 17 2020 12:20 PM