The thing that crashed your PC was probably not written by Microsoft

When Windows falls over, the code that pushed it usually came from somewhere else. A graphics driver, a Wi-Fi driver, something a security product buried deep in the system. Those pieces run in kernel mode, where there is no safety net at all. A mistake in an ordinary app closes the app. A mistake down there takes the whole machine with it, and the user sees a blue screen with Microsoft's name on it.

Microsoft has stopped pretending that is somebody else's problem. The Driver Quality Initiative, announced at WinHEC in May, rests on four pillars. Architecture is the one that counts: harden kernel-mode drivers and move third-party code out of the kernel altogether, either into user mode or onto class drivers Microsoft writes itself. The rest cover tighter vetting of who is allowed to publish a driver, clearing stale and low-quality entries out of the Windows Update catalogue, and grading drivers on battery drain and heat instead of crash counts alone.

The first results are showing up now. Intel's Arc graphics driver 32.0.101.9034 landed this month as its first release supporting Windows 11 26H2, and Intel's Wi-Fi and Bluetooth drivers have already been built along the new lines. Nothing about this is a download you go and get. It is an industry changing how it writes code, which means it arrives slowly and you only notice it by what stops happening.

In the meantime the old rule still applies: a driver update can fix your machine or ruin your week, and you want a way back. Tendvane backs up the drivers currently on your PC to a folder of your choosing and can put them back later, so trying a newer one is a decision you can reverse.