Microsoft and its partners are rebuilding how Windows 11 talks to hardware to save your PC from itself

An outdated or buggy driver can ruin a day at your desk. From not being able to connect to a printer to your PC not recognizing a device, a faulty driver can stop even otherwise reliable PCs and hardware from working.

One of the pillars of the Windows K2 initiative is to improve OS, driver, and app reliability. At the WinHEC 2026 (Windows Hardware Engineering Conference), Microsoft worked with PC makers, hardware vendors, chip makers, and designers to build a better ecosystem.

Microsoft introduced the Driver Quality Initiative (DQI) at the conference, which aims to "fundamentally raise the bar on driver quality, reliability and security across Windows."

“Delivering high-quality drivers and resilient platforms isn’t owned by any one company—it’s a shared commitment," said David Harmon, Director, Software Engineering, AMD. "Through our close collaboration with Microsoft, AMD is focused on building a culture of joint accountability to ensure security, stability and predictable performance for our customers at scale.”

The DQI is split into four pillars: Architecture, Trust, Lifecycle, and Quality Measures. Microsoft's Robin Seiler breaks down the key parts of each pillar in a blog post:

• Architecture: We are heavily investing in hardening kernel mode drivers and enabling the third-party kernel mode driver transition to either user mode driver or Microsoft authored class drivers. This is to ensure higher driver security, reliability and resiliency. User-mode driver investments include performance updates to PCIe devices with DMA support as well as Wi-fi stack (coming soon). Class driver investments include Soundwire Device Class for Audio (SDCA), introduction of the I3C class driver, NCM USB ethernet class driver as well as continuous enhancements to existing first-party class drivers on Windows 11.
• Trust: We are raising the bar for trusted partners and trusted drivers, including stronger partner verification, expanded automated analysis and updated Windows Hardware Compatibility Program requirements.
• Lifecycle: We are improving driver lifecycle management through better Windows Update catalog hygiene, including deprecating outdated or low-quality drivers, advancing SBOM alignment and enabling faster issue analysis through driver symbols.
• Quality Measures: We are expanding how driver quality is measured beyond crashes to include stability, functionality, performance, and power and thermal impact, giving partners clearer signals to improve the real customer experience.

Since drivers connect Windows to chips, peripherals, and other components, a poor driver can drag down an entire computing experience.

Third-party drivers typically run in the Windows Kernel for maximum performance, but this allows a single failure to crash the entire OS. Moving these drivers to User Mode isolates them from the system core. If a User Mode driver fails, it can restart independently without affecting the rest of your PC.

Microsoft recently rolled out Cloud-Initiated Driver Recovery, which lets users revert to a known-working driver following a faulty update. While that's a welcome addition, it would be even better to run into fewer driver issues at all rather than having better ways to fix problems.

At WinHEC, Microsoft presented a keynote and held workshops to discuss its new driver initiative. Hands-on labs and demos were also available to engineers to help give experience and showcase tools.

Join us on Reddit at r/WindowsCentral to share your insights and discuss our latest news, reviews, and more.