Welcome to Microsoft Q&A!
Thank you for the additional information and for sharing the results of your testing with driver version 31.0.101.2145.
You make a valid point regarding wushowhide.diagcab. While it could temporarily hide a specific update, it should not be considered a permanent or currently supported long-term solution. I appreciate you taking the time to clarify this.
It's also worth noting that Windows does not select drivers based solely on the visible version number. Driver applicability and selection depend on several factors defined within the driver package, including hardware ID matching, driver ranking, targeting metadata, digital signatures, and other installation attributes. Because of this, an OEM-targeted driver may continue to be offered even when a newer generic Intel driver is already installed.
Based on your observations, version 31.0.101.2121 is not actually replacing the installed 31.0.101.2141 or 31.0.101.2145 driver. However, I completely understand your concern that Windows Update continues to download an unnecessary package that consumes approximately 1.3 GB of storage. That behavior can certainly be frustrating.
At present, Windows does not provide a supported setting that allows users to permanently block only a single driver update while continuing to receive all other driver updates automatically. The supported policy available on applicable Windows editions is:
Computer Configuration > Administrative Templates > Windows Components > Windows Update > Do not include drivers with Windows Updates
When enabled, this policy excludes driver updates delivered through Windows Update as a whole rather than blocking only version 31.0.101.2121. In that scenario, drivers can be obtained through Lenovo Vantage, Lenovo Support, or by manually installing a compatible Intel driver. Since this is a Lenovo device, Lenovo-provided drivers generally remain the preferred option when OEM-specific customizations are involved.
For managed enterprise environments, Windows driver update policies in Microsoft Intune can provide more granular control by allowing administrators to review, approve, or pause individual driver updates before deployment.
If Windows Update continues to offer or download version 31.0.101.2121 while retaining version 31.0.101.2145, the underlying targeting and publication metadata cannot be modified locally on the device. That information is controlled by the driver publisher through the Windows Update publishing process.
Given what you have described, I would recommend submitting feedback through Feedback Hub and if possible, reporting the behavior to Lenovo with the following details:
- Exact Lenovo model and machine type
- Windows edition, version, and OS build
- Intel UHD Graphics 600 hardware IDs from Device Manager
- Currently installed graphics driver version
- Screenshot of the offered update
- Relevant Windows Update history entries
- Confirmation that the package is downloaded but not installed
- Approximate additional disk space consumed
This information can help determine whether the driver targeting or publication metadata should be reviewed by Lenovo or Intel.
Since version 31.0.101.2145 is installed successfully and no incompatibility warnings are being reported, it is reasonable to continue using that driver as long as the system remains stable. At the same time, I would encourage monitoring Lenovo's support channels for future model-validated driver releases, as generic Intel drivers may not always include device-specific optimizations provided by the OEM.
For additional information, please visit:
How Windows Ranks Driver Packages - Windows drivers | Microsoft Learn
Understanding driver updates | Microsoft Support
Manage additional Windows Update settings | Microsoft Learn
Configure Windows Driver Update Policies - Microsoft Intune | Microsoft Learn
Manage Windows Driver Updates - Microsoft Intune | Microsoft Learn
Automatically get recommended and updated hardware drivers | Microsoft Support
If you find it useful, please click Accept Answer.
Thank you for choosing Microsoft Q&A.