Microsoft to fix Windows 11 driver auto-downgrade issue

🔑 Enhanced Key Takeaways

•The existing Windows Update driver ranking system prioritizes OEM-approved drivers in the Windows Update Catalog based on a broad 4-part Hardware ID (HWID) match, often leading to the installation of older versions over newer, manually installed drivers from chipmakers like Nvidia, AMD, or Intel.
•The new 2-part HWID combined with Computer Hardware ID (CHID) targeting mechanism will be applied at the 'shipping label' level within Microsoft's Hardware Dev Center, rather than being embedded in the driver's INF file. This change specifically targets new display driver submissions for new devices, meaning existing devices with a history of 4-part HWID drivers will not be immediately affected.
•Microsoft is also implementing a 'Cloud-Initiated Driver Recovery' (CIDR) feature, which will enable the company to remotely roll back faulty drivers distributed via Windows Update to a previously known-good version without requiring user intervention or OEM action. This feature is undergoing validation and testing until August 2026, with a broader rollout planned for September 2026.
•The issue of Windows Update overriding manually installed drivers has been a long-standing source of frustration for users, with many resorting to disabling automatic driver updates through Group Policy or using third-party tools like Display Driver Uninstaller (DDU) to prevent unwanted downgrades.
•In addition to driver targeting improvements, Microsoft is unifying the Windows Update experience to reduce system reboots. This involves coordinating driver, .NET, and firmware updates to align with the monthly quality update, aiming for a single monthly restart.

🛠️ Technical Deep Dive

Windows' driver selection process involves building a list of candidate driver packages that match a device's hardware IDs and then assigning a rank to each. The operating system prioritizes drivers with a lower rank, indicating a better match.
The current driver ranking system considers several factors in order of importance: digital signature trust, Plug and Play (PnP) ID match, driver date, and driver version. An older driver package can outrank a newer one if it has a better PnP ID match or signature.
Computer Hardware IDs (CHIDs) are used by the Windows Update service to narrow down the applicability of a driver to specific systems *before* the PnP ranking process occurs. CHIDs are generated from System Management BIOS (SMBIOS) values, which can include details like Manufacturer, Product Name, Family, and Baseboard information.
For the new policy, CHIDs are not to be included within the driver's INF file but are applied by partners at the 'shipping label' level in the Microsoft Hardware Dev Center portal, allowing for more precise targeting to specific computer models or hardware configurations.
Microsoft also implemented a security hardening measure in April 2026, shifting kernel driver trust to rely by default on Windows Hardware Compatibility Program (WHCP)-signed drivers or an explicit Microsoft allow list, thereby phasing out the legacy cross-signed driver program.

🔮 Future ImplicationsAI analysis grounded in cited sources

Reduced instances of unwanted GPU driver downgrades for new devices.

The more precise 2-part HWID + CHID targeting will ensure driver updates are scoped to specific systems, preventing broad OEM driver overrides for newly released hardware.

Enhanced system stability and user experience due to automatic faulty driver rollbacks.

The Cloud-Initiated Driver Recovery (CIDR) feature will allow Microsoft to remotely revert problematic drivers to known-good versions without requiring manual user intervention, reducing downtime and troubleshooting efforts.

Improved security posture for Windows kernel drivers.

The phasing out of legacy cross-signed kernel drivers in favor of WHCP-signed drivers or Microsoft's allow list will close long-standing security vulnerabilities associated with less stringent signing processes.

⏳ Timeline

2021

Microsoft removed the old cross-certificate trust path from the active driver program, maintaining a compatibility tail.

2023-07

Microsoft Intune introduced driver update management as part of the Windows Update for Business deployment service.

2024-09

Microsoft Learn documentation updated on how Windows Update uses CHID to reduce driver applicability before PnP ranking.

2025-10

Microsoft issued KB5070538 to explain why Windows Update sometimes installs older drivers, clarifying the selection logic.

2026-04

Microsoft began a pilot program for the new 2-part HWID + CHID targeting for display drivers and started phasing out legacy cross-signed kernel drivers.

2026-05

Microsoft announced Cloud-Initiated Driver Recovery (CIDR) for remote rollback of faulty drivers, with testing commencing.