For the first time since 2018, Microsoft held a Windows Hardware Engineering Conference in Taipei this week. What came out of it is the most aggressive driver quality overhaul the company has ever attempted.
The Driver Quality Initiative (DQI) is an ecosystem-wide effort spanning four pillars: Architecture, Trust, Lifecycle, and Quality Measures. Corporate vice presidents Robin Seiler and Ian LeGrow described it as a push to "fundamentally raise the bar on driver quality, reliability and security across Windows." The initiative is notable not just for its scope, but for the fact that Microsoft is finally treating bad drivers as a structural problem, not a series of isolated incidents.
Under the Architecture pillar, the company is investing heavily in hardening kernel-mode drivers and pushing third-party drivers out of the kernel entirely. The goal is to transition third-party kernel-mode drivers to either user-mode drivers or Microsoft-authored class drivers.
User-mode driver investments include performance updates to PCIe devices with DMA support plus a Wi-Fi stack update coming soon. Class driver work covers Soundwire Device Class for Audio (SDCA), the I3C class driver, and NCM USB ethernet class driver improvements. The Trust pillar raises the bar for hardware partners through stronger verification, expanded automated analysis, and updated Windows Hardware Compatibility Program requirements. Partners who consistently ship low-quality drivers will face consequences. A new quality scorecard for each IHV will be visible in a partner portal, aggregating crash data, power consumption telemetry, and user feedback. Those scoring low will receive direct engineering support from Microsoft or risk losing their WHCP privileges.
Starting in late 2026, drivers must pass more reliability and security tests before earning a WHQL signature. Hardware partners who ship without the updated WHQL stamp will see those drivers blocked from automatic installation via Windows Update. The Lifecycle pillar tackles the driver catalog directly, which the company acknowledged is cluttered with outdated, abandoned, and low-quality drivers that have been breaking PCs for years. The system has been downgrading graphics drivers, replacing optimized versions with older, unstable ones. Microsoft is now committing to "better Windows Update catalog hygiene, including deprecating outdated or low-quality drivers." By permanently removing problematic files from the repository, the OS will stop automatically downloading software known to cause system instability, hardware conflicts, or severe performance drops.
Microsoft is also overhauling how graphics drivers are targeted to devices, shifting from a four-part hardware identification system to a simplified two-part model combining Hardware ID (HWID) and Computer Hardware ID (CHID).
This change, expected between late 2026 and early 2027, aims to fix the long-running issue of Windows Update delivering mismatched GPU drivers to systems. The Quality Measures pillar expands how driver quality is tracked beyond simple crash monitoring. The company will now measure stability, functionality, performance, and power and thermal impact, giving partners clearer signals on real customer experience.
Separately, Microsoft detailed Cloud-Initiated Driver Recovery, a feature that lets the company trigger automatic driver rollbacks from the cloud. When a driver is flagged during internal shiproom evaluation, a rollback instruction can be pushed through Windows Update, uninstalling the problematic driver and replacing it with the last working version.
No user interaction required. The feature is being tested with hardware partners and will begin rolling out gradually in September.
"Delivering high-quality drivers and resilient platforms isn't owned by any one company, it's a shared commitment."
AMD's David Harmon, Director of Software Engineering, framed the effort as a collective responsibility. "Through our close collaboration with Microsoft, AMD is focused on building a culture of joint accountability." The revival of WinHEC after an eight-year gap signals Microsoft understands that software optimization alone won't fix Windows 11's stability problems. True system reliability requires deep hardware-level collaboration. By bringing engineers from Dell, AMD, HP, and ASUS into direct contact with the Windows development team, the company is establishing joint accountability for driver quality.
"The work we do together over the coming year will define the Windows experience for more than a billion users."
Seiler and LeGrow wrote.
