Windows Update’s Driver Purge: Smoother Updates, or Hidden Headaches?

Microsoft has begun implementing server-side measures to purge outdated drivers from the Windows Update catalog. According to the company, this policy is primarily aimed at Original Equipment Manufacturers (OEMs); once an OEM submits a newer version of a driver, Microsoft will automatically remove the older version from its update database.

These obsolete drivers refer to outdated or deprecated versions that are no longer necessary when a newer, fully compatible alternative is available on a given PC. While such drivers were previously retained, Microsoft has now opted for their direct removal.

For most users, this cleanup process will bring minimal change. However, in certain edge cases, the new policy could potentially lead to unexpected issues—challenges that will require coordinated resolutions between Microsoft and the respective OEMs.

For example, if a newly released driver from an OEM introduces compatibility issues with specific hardware, and the older driver has already been purged by Microsoft, the OEM must manually resubmit the previous version to Microsoft along with a justification for its reinstatement.

In the past, when multiple versions of a driver for the same product were present, users might have seen both versions listed in Windows Update. Even after installing one, the other might reappear during a subsequent check for updates.

Under the revised policy, users will only be offered the most recent version of a driver. Legacy versions will neither appear nor be installed, and the confusion of dual installations will be eliminated. This streamlining may ultimately enhance the overall user experience.

It is worth noting, however, that this policy adjustment does not resolve a commonly reported issue—namely, that drivers manually installed from OEM websites are sometimes overwritten by older versions delivered via Windows Update.

This problem stems from the prioritization system: OEM-submitted drivers typically carry WHQL certification, granting them higher installation precedence. As a result, Microsoft may replace a newer locally installed driver with an older WHQL-certified one in the name of stability.

Of course, users retain the ability to manage driver updates through the system settings—for instance, by disabling driver updates during Windows Update. Doing so ensures that automatic update checks will bypass any changes to driver configurations.

Related Posts:

• Google Chrome scans files on users’ computers
• Google will force OEMs to regularly push Android security updates
• Android’s Future: 8 Years of Security with Qualcomm & Google
• France Leads International Effort to Eradicate PlugX Trojan from 3,000 Systems
• ChatGPT and Sora Go Offline: OpenAI Scrambles to Restore Service Amid Global Outage