Windows will finally stop corrupting video drivers: how they did it

Microsoft has officially admitted what gamers and system administrators have been shouting about for years: Windows Update is quietly replacing the latest video card drivers with versions that were two or three years old. The company announced that it was rewriting the very logic of hardware recognition — and this became possible only after a petition with twenty thousand votes and a wave of public irritation.

Driver that was not asked for class=»notranslate»>__GTAG8__

A familiar situation: you download the latest video card driver directly from the NVIDIA website, install it, enjoy the increase in FPS in the new game — and a couple of weeks after the scheduled Windows update you find a two-year-old version on your system. And without a single notification. According to the Windows Latest service, in some cases, Windows Update replaced drivers from April 2026 with assemblies from 2024.

The problem did not concern some exotic product, but the three largest manufacturers of graphics chips at once — NVIDIA, AMD and Intel. And it hit not only gamers: game optimizations disappeared, energy consumption profiles broke, and some users even received visual bugs that were not observed before the rollback.

Why it was useless to complain

Formally, Windows Update has its own logic: the system tries to slip in a “tested” driver, marked by the manufacturer as stable through the compatibility program (WHCP). But hardware identification was based on a cumbersome four-component scheme, due to which Windows periodically confused which version of the driver for a particular video card was really newer. As a result, the custom, manually installed driver did not “seem” new to the system, and it rolled it back to its own archived version.

In the Windows Insider feedback section, a topic about driver rollbacks has been collecting complaints for years, and one of the threads received more than 20,000 upvotes—by Feedback Hub standards, this is the level of real public pressure. Users essentially demanded a simple thing: give the option to ignore the update if I already have a newer version. Microsoft ignored this request for several years.

What has changed

The turning point happened in May 2026 at the Windows Hardware Engineering Conference (WinHEC). Microsoft for the first time publicly acknowledged the scale of the problem and announced a change in the very principle of matching drivers with hardware.

Instead of a four-component identification, a simplified two-component model is introduced: a combination of Hardware ID (HWID) and Computer Hardware ID (CHID). In fact, the system will more accurately understand what kind of hardware a particular user has, and will stop confusing “newer” with “older” — which means it will stop replacing a fresh driver with an archived one simply because it could not recognize it correctly.

In parallel, the company announced a second measure — the Cloud-Initiated Driver Recovery (CIDR) cloud mechanism. The logic is the opposite: if, after an automatic update, graphics, sound or Wi-Fi begin to malfunction, the system will be able to receive a command from the cloud and roll back the problematic driver to the latest stable version — without user intervention and without digging into the “Device Manager”. Testing of the function with hardware partners is already underway, mass implementation is planned for September 2026.

There is a nuance that is worth remembering for those who install drivers manually: CIDR only works with drivers installed through Windows Update itself. If you, like many enthusiasts, download the distribution directly from the NVIDIA or AMD website, the cloud mechanism will not roll back and “rescue” it — Microsoft simply does not have control over this driver here. On the one hand, it’s inconvenient, on the other hand, it’s for the better: hardly anyone will be happy if the system is taught to arbitrarily touch something that the user has consciously configured.

At the same time, the second problem was revealed

While Redmond was sorting out the rollback of drivers, another detail surfaced: faulty drivers have been affecting the autonomy of laptops for years — it’s just that previously this was not considered a reason for a driver recall. Microsoft has announced that third-party software will now be assessed not only on the number of system crashes it causes, but also on how the driver impacts the day-to-day experience — including battery consumption. Previously, such things simply were not a criterion for verification.

It is significant that even after the May announcements, old surprises continue to resurface: in August, Reddit users discovered that Windows 11, under certain conditions, can completely remove the video card driver, considering it an “unused” device — simply because the laptop was running for some time on the integrated graphics in energy-saving mode. So it’s too early to say that the topic is closed: Microsoft is eliminating specific symptoms, but the driver management system is clearly not yet fully debugged.

What does this mean for users

While the changes have not affected every computer, the transition to the new identification system will occur gradually, and CIDR is just preparing for the September release. But the very fact that the company officially documented the problem and named specific technical reasons for the failure is a rare case when a massive complaint to Feedback Hub actually led to a revision of the internal architecture, and did not remain in the “under consideration” status.

Sources:

• windowslatest.com
• itc.ua
• ixbt.com

Xrust Windows will finally stop corrupting video drivers: how they did it