Microsoft plans cloud driver rollback

Microsoft said on May 12 that it is adding a Cloud-Initiated Driver Recovery feature to Windows Update, giving the company a way to automatically roll back drivers it later determines have quality problems. The change was outlined in a Hardware Dev Center post aimed at partners that publish drivers through Windows Update. Microsoft said the rollback can be triggered from its Driver Shiproom process and delivered through the existing Windows Update pipeline, without a new client agent. The company published the change alongside a separate graphics-driver targeting update and as some Windows 11 users reported trouble installing the May cumulative update KB5089549. ### How would the rollback work once a bad driver is identified? Microsoft said the recovery flow starts when a driver already distributed through Windows Update is later found to have quality issues during shiproom evaluation. In that case, Microsoft can create a recovery action from the Hardware Dev Center Driver Shiproom and target the affected shipping labels, according to the company’s May 12 post. (techcommunity.microsoft.com) The rollback instruction is then sent through Windows Update, Microsoft said, and affected devices are moved back to the previously installed driver or the next best version available on Windows Update. Devices for which a shiproom-approved replacement cannot be found will not attempt the cloud-initiated recovery, the post said. (techcommunity.microsoft.com) ### Why is Microsoft changing graphics-driver targeting at the same time? Microsoft said on May 12 that one of the most common complaints in the graphics-driver area was that “Windows Update downgrades my drivers.” In a second Hardware Dev Center post, the company said display drivers for new devices will be allowed to use 2-Part hardware IDs together with Computer Hardware IDs, or CHIDs, instead of the broader 4-Part targeting used today. (techcommunity.microsoft.com) That narrower targeting is meant to scope updates to the systems they are intended for, Microsoft said, and let devices that are not locked to a 4-part hardware ID keep a user-installed display driver rather than being replaced by an older Windows Update choice. Microsoft’s documentation describes CHIDs as hardware identifiers created by OEMs or ODMs and used to target the correct driver to the correct system. (techcommunity.microsoft.com) ### When does the new graphics policy take effect? April 2026 through September 2026 is the pilot window for the new 2-Part HWID plus CHID targeting model, Microsoft said. During that period, the company said partners should share feedback with their Microsoft representative if the new targeting is insufficient for a specific scenario. (techcommunity.microsoft.com) September 2026 is the general-availability milestone, according to Microsoft’s timeline. At that point, Microsoft said it will enforce 2-Part HWID plus CHID targeting for display-driver submissions on new devices that have not previously had a 4ID Windows Update driver installed. (techcommunity.microsoft.com) ### What is happening with KB5089549? Microsoft released KB5089549 on May 12 for Windows 11 versions 25H2 and 24H2, with OS builds 26200.8457 and 26100.8457. The support page says the cumulative update includes May 2026 security fixes and non-security changes from the prior optional preview release. (techcommunity.microsoft.com) Microsoft’s support note highlights Secure Boot certificate targeting, startup reliability after boot-file updates, SSDP reliability and Egypt daylight-saving-time support. The same page tells users to check the Windows release health dashboard for the latest status on the release. (support.microsoft.com) ### Has Microsoft acknowledged the install-failure reports? Microsoft’s public KB5089549 support page did not show an installation-failure notice in the material reviewed on May 15. At the same time, Microsoft Q&A threads posted on May 13 and May 14 included users reporting repeated install failures and restart errors for KB5089549, including one report citing error code 0x800f0922. (support.microsoft.com) Microsoft’s release-health hub says it is the place to track known issues, safeguards and resolutions for Windows updates. The company’s next visible milestones on these servicing changes are the September 2026 enforcement date for the graphics-driver targeting policy and any release-health updates tied to KB5089549. (learn.microsoft.com) (support.microsoft.com)