Solved Windows Update overrides the latest Intel Graphics Driver with an older version

As to not get things heated, I'd like to first thank each and every one of you for your hospitality and help.

I'll experiment and come to a conclusion on my own, but I'm glad I had a few members dedicate their time to the thread and help me pave the path which I should tread on.

Visiting this forum and asking out-right is a real time saver, and I'll always be happy to come back and read through or post about any troubles that I have.

hdmi said:

I already explained it twice. Also, when it comes to the (off topic) debate of keeping drivers always up-to-date, the typical-old "If it ain’t broke, don’t fix it" is just another myth. Worse, it's one of the most common rookie mistakes. Frequently updating drivers is a good practice because it improves performance, stability, compatibility and security. To you, it might mean squat. But personally, I, am still in the club of those who prefer not to take these added risks when there is no compelling reason to do so.

The pros of frequently updating drivers far outweigh the cons, as the risk of an update causing issues is small, these instances are rare and usually due to:

1. installing the wrong driver (e.g., if the right one is the one that has customizations from the manufacturer, but I will repeat myself saying for the third time that Asus does not customize this driver AFAIK...) or
2. a faulty update (the risk of which can be mitigated further, i.e. by waiting for Intel to release a new WHQL certified generic one some time after they have released a new non-WHQL certified generic one).

Again, if an update does cause issues, it can be rolled back. Like I also already said (in my post #8), I haven't had any problems using the latest generic one from Intel.

Click to expand...

HDMI, I completely agree with you on this topic.

Just in case there is a problem with a new driver, I always keep a copy of the previous version until I have lived with a new driver for a while and found no problems. That way I have quick and easy access to the old driver "just in case".

d1ggo_ said:

I'll experiment and come to a conclusion on my own

Click to expand...

That's a perfectly fine answer! Different people will come to different conclusions, but experimenting to see what works best for you is great. Far better than simply "winging it".

hsehestedt said:

That's a perfectly fine answer! Different people will come to different conclusions, but experimenting to see what works best for you is great. Far better than simply "winging it".

Click to expand...

I would like to ask if you could provide your solution as to preventing Windows from overriding the driver though...

d1ggo_ said:

I would like to ask if you could provide your solution as to preventing Windows from overriding the driver though...

Click to expand...

Here is the procedure that I use:


NOTE: This procedure shows you how to accomplish this task using the group policy editor or the registry editor. Be aware that the group policy editor requires the Pro edition of Windows or higher. If you are on Home, use the registry method. This method works for both Win 10 and 11.

In my case, I have a display adapter for Windows constantly insists on installing an older driver. Like you, this is an Intel Display Adapter so this should work perfectly for you. This resolves that issue for me. Just be aware that this will block all updates for the device for which you set it up. Even manual updates will be blocked. As a result, to update the driver, you will need to undo the change, update the driver, then re-do the group policy or registry entry.

d1ggo_ said:

The thing is, it isn't, haha.

There are 3 variations for this driver:
- The MS Update catalog one, the oldest, which is from 2023
- The OEM (ASUS) provided one, which is from December of 2024
- The generic Intel driver, the newest, from Jan of this year

Click to expand...

Version...not year...big difference. OEM drivers often don't follow normal versioning conventions.

I had a similar situation a couple of days ago with the Audio driver when I upgraded to 24H2 only in reverse. In 24H3 I had an older version of the RealTek audio driver installed as the newer/latest version has problems. 24H2 installed the latest version and I installed the older version. When I ran Windows Update the latest version was reinstalled and I had to RollBack to the older version. Sometimes you have to do this several times and run WU until it gets the message. I find you have to juggle install new version/Windows Update/install old version/Rollback to get the version you want to stick. I had to keep notes about what I had done to avoid getting confused.

hdmi said:

I already explained it twice. Also, when it comes to the (off topic) debate of keeping drivers always up-to-date, the typical-old "If it ain’t broke, don’t fix it" is just another myth. Worse, it's one of the most common rookie mistakes. Frequently updating drivers is a good practice because it improves performance, stability, compatibility and security. To you, it might mean squat.

Click to expand...

You didn't really answer my question, even in this reply.

But anyways...latest is simply not always the greatest. Never has been and never will be. As a software developer myself, I can tell you that much.

I have plenty of examples where updating to latest drivers has NOT improved performance (more likely decreased), has made system unstable and broken compatibility and in some cases even rendered system completely unbootable. But I'm not going to address those here. What has improved in many cases is security though, but only when there has been an actual need and fix for that. Many driver updates don't contain any kind of security fixes at all.

I do agree that it is important to keep drivers updated if a newer version improves security, but here again some security fixes don't apply to everyone and are sometimes fixes for some very uncommon scenarios.

What I would be more worried about is what one does online and that your network is made safe.

Things aren't always that black and white. That is also the main reason I don't always run after the latest when there is absolutely NO need to do that. First I read through the changelogs to see what the update will fix, then I decide what to do and whether it's worth it or not.

I can give you one example...just for the sake of having one. Doing an nVidia GPU driver update weekly(or whatever schedule they have) is completely useless, because most updates ONLY contain game optimizations which most often nerf older/other games. This has happened time after time and will continue to do so.

hsehestedt said:

Even manual updates will be blocked. As a result, to update the driver, you will need to undo the change, update the driver, then re-do the group policy or registry entry.

Click to expand...

This is exactly why I wrote the PowerShell batch script. It works by simply hiding the older Intel Display driver update in Windows Update if it finds one. Hiding = the same way you could choose to hide an update manually, i.e. by using the wushowhide.diagcab tool from Microsoft.

1. Install the latest generic driver from Intel
2. restart the computer
3. run the script
4. after Intel has released a new generic driver, go to step 1.

hdmi said:

This is exactly why I wrote the PowerShell batch script. It works by simply hiding the older Intel Display driver update in Windows Update if it finds one. Hiding = the same way you could choose to hide an update manually, i.e. by using the wushowhide.diagcab tool from Microsoft.

1. Install the latest generic driver from Intel
2. restart the computer
3. run the script
4. after Intel has released a new generic driver, go to step 1.

Click to expand...

wushowhide.diagcab is deprecated. W11 does not have the replacement troubleshooter in the public channel (IDK if it is in another ring).

I use the above file as a workaround as I too have had the same issue as @d1ggo_ , since approximately the same time.

5 security advisories apply to the graphics driver (mainly privilege escalation via local access, but still) the series 30 driver from WU should not overwrite a series 32 driver.

wushowhide.diagcab works at present but MS advised posting in community to seek an answer. The rep I contacted seemed to think it was an ASUS issue; well I don't concur, they may supply a driver for distribution in WU to MS but it is an MS update problem as far as I can see. With no idea as to how long my workaround will last.

I also prefer to use IDSA as it often updates other drivers on a faster cadence than MyASUS or WU.

JacksonS said:

wushowhide.diagcab is deprecated. W11 does not have the replacement troubleshooter in the public channel (IDK if it is in another ring).

I use the above file as a workaround as I too have had the same issue as @d1ggo_ , since approximately the same time.

5 security advisories apply to the graphics driver (mainly privilege escalation via local access, but still) the series 30 driver from WU should not overwrite a series 32 driver.

wushowhide.diagcab works at present but MS advised posting in community to seek an answer. The rep I contacted seemed to think it was an ASUS issue; well I don't concur, they may supply a driver for distribution in WU to MS but it is an MS update problem as far as I can see. With no idea as to how long my workaround will last.

I also prefer to use IDSA as it often updates other drivers on a faster cadence than MyASUS or WU.

Click to expand...

Yes, I already know that wushowhide.diagcab is deprecated. My script doesn't depend on it, though. Instead, my script uses the Windows Update Agent (WUA) API via PowerShell 5.1 so my script can be run on Windows 11 right out of the box if PowerShell 5.1 is enabled (which, by default, it is) and Windows Update has internet access (and is working like normal).

P.S., for further reading on how the WUA API can be used to search for available updates:

hdmi said:

Yes, I already know that wushowhide.diagcab is deprecated. My script doesn't depend on it, though. Instead, my script uses the Windows Update Agent (WUA) API via PowerShell 5.1 so my script can be run on Windows 11 right out of the box if PowerShell 5.1 is enabled (which, by default, it is) and Windows Update has internet access (and is working like normal).

P.S., for further reading on how the WUA API can be used to search for available updates:

IUpdateSearcher::Search (wuapi.h) - Win32 apps

Performs a synchronous search for updates. The search uses the search options that are currently configured.

learn.microsoft.com

Click to expand...

The MS rep couldn't give a timeline on when the new tool would be active or available, nor when the wushowhide.diagcab will stop working (if it does, it may simply work but be unsupported). As soon as it is unsupported and ceases to work, that's when I'll look at alternatives.

More worryingly, the fact is it was fine until just recently and MS don't seem to care. I'm becoming a bit resigned to the fact that whenever there is a new version of Windows; and it is likely there will be one before the year is out; that we will go through all this again.

Upgrading to Windows 11 caused driver reversions with in-place upgrades (which were overcome by simply reinstalling the existing driver, just an irritation and little bit time consuming) plus issues with microcode patch levels not being the same as existing Microsoft patches in Windows 10.

So that status quo was fine since 2021, until just recently.

Microsoft do have history with Intel mainboard drivers where they reverted the date so that they wouldn't install over newer. I just don't see why it isn't the same here....always seeemingly laptop/iGPUs are suffering. I use reference drivers for my discrete GPU, but ensure I don't have an internet connection whilst I install mainboard and GPU drivers at least. I literally pull the plug out of the Ethernet.

hdmi said:

This is exactly why I wrote the PowerShell batch script. It works by simply hiding the older Intel Display driver update in Windows Update if it finds one. Hiding = the same way you could choose to hide an update manually, i.e. by using the wushowhide.diagcab tool from Microsoft.

1. Install the latest generic driver from Intel
2. restart the computer
3. run the script
4. after Intel has released a new generic driver, go to step 1.

Click to expand...

Could you pass over the script?

hdmi said:

After the latest Intel Display driver has been installed and the computer has been restarted to finalize the install, you can run my batchfile below to prevent an outdated Intel Display driver update from showing up in Windows Update.

This will effectively prevent Windows Update from automatically downloading/installing that update (if available).

Batch:

<# ::
@echo off
"%windir%\System32\WindowsPowerShell\v1.0\powershell.exe" -NoProfile -ExecutionPolicy Bypass -Command ^$fp = '%~dpnx0'; Invoke-Expression ((Get-Content '%~dpnx0') -join [Environment]::NewLine); Elevate
goto :eof
#>
$Command = "`$fp = '$($fp)'; Write-Host 'Processing: ' -ForegroundColor Yellow -NoNewline; Write-Host `$fp; Invoke-Expression ((Get-Content `$fp) -join [Environment]::NewLine); if (`$fp -ne '') { Main }"
function Elevate {
  if (([Security.Principal.WindowsPrincipal][Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole] "Administrator")) {
    Start-Process "$env:windir\System32\WindowsPowerShell\v1.0\powershell.exe" "-NoProfile -ExecutionPolicy Bypass -Command `"$Command`""
  } else {
    Start-Process "$env:windir\System32\WindowsPowerShell\v1.0\powershell.exe" "-NoProfile -ExecutionPolicy Bypass -Command `"$Command`"" -Verb RunAs
  }
}
function Main {
  if (([Security.Principal.WindowsPrincipal][Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole] "Administrator")) {
    $Updates = (New-object -ComObject Microsoft.Update.Session).CreateUpdateSearcher().Search("IsInstalled=0 and Type='Driver' and IsHidden=0").Updates
    if ($Updates.Count -gt 0) {
      $Found = ($Updates | Where-Object { $_.Title -match '^Intel Corporation - Display - ' })
      if ($Found.Count -gt 0) {
        $Found | ForEach-Object {
          Write-Host "Found update: " -ForegroundColor Yellow -NoNewline
          Write-Host $_.Title
          $_.IsHidden = 1
        }
      } else { Write-Host "No Intel Display driver updates available in Windows Update." -ForegroundColor Yellow }
    } else { Write-Host "No driver updates available in Windows Update." -ForegroundColor Yellow }
  } else { Write-Host "Couldn't elevate the script." -ForegroundColor Yellow }
  pause
}

Click to expand...

Nevermind, lol, I forgot you already posted it!

d1ggo_ said:

The thing is, it isn't, haha.

There are 3 variations for this driver:
- The MS Update catalog one, the oldest, which is from 2023
- The OEM (ASUS) provided one, which is from December of 2024

Click to expand...

I'm currently having the same problem. I want to update my Acer Nitro AN515-57 intel display driver to
Version: 32.0.101.7076 Release date: September 19, 2025

But the OEM version keeps being reinstalled. 30.0.100.9864 from 20/08/2021. As they say OEM is better, but that's quite a gap, so debating if it's worth it.

I'm currently after installing two 16gb ram sticks up from two 8gb ram sticks getting "Core power limit Exceeded" in HWinfo which is bothering me. It's maybe causing fps drops to 3-5fps. And I just fixed that before due to horrible thermal throttling by installing ram from 8 to 16 and cleaning it all out and putting thermal pads. It could then run at 50-60 on full graphics.

So now having gone to 32gb total ram I seem to have another problem. I think installing this driver would maybe fix some wattage or draw? Hopefully not trip it over the ps limit.

Your issue is that your running a laptop. There's a power limit envelope. Only sane option to keep power limits in check is to NOT run games at full FPS and max graphics. Find a good balance for your desired FPS and lock that in.

For example, if you're on a 120Hz display, there's no point in trying to run the game at 300FPS, rather lock the game at 120 and adjust graphics accordingly, so it stays constant. You'll run games more stable and you avoid overheating.

JAcked said:

But the OEM version keeps being reinstalled.

Click to expand...

This happens when the OEM makes modifications to the driver. It's usually best to use the OEM version. In fact, sometimes using the non-OEM version can cause problems such as the computer not being able to wake up from sleep or if you have fast startup enabled it can cause the system to boot with a black screen where you see no video and various other problems.

JAcked said:

I'm currently having the same problem. I want to update my Acer Nitro AN515-57 intel display driver to
Version: 32.0.101.7076 Release date: September 19, 2025

But the OEM version keeps being reinstalled. 30.0.100.9864 from 20/08/2021. As they say OEM is better, but that's quite a gap, so debating if it's worth it.

I'm currently after installing two 16gb ram sticks up from two 8gb ram sticks getting "Core power limit Exceeded" in HWinfo which is bothering me. It's maybe causing fps drops to 3-5fps. And I just fixed that before due to horrible thermal throttling by installing ram from 8 to 16 and cleaning it all out and putting thermal pads. It could then run at 50-60 on full graphics.

So now having gone to 32gb total ram I seem to have another problem. I think installing this driver would maybe fix some wattage or draw? Hopefully not trip it over the ps limit.

Click to expand...

Hi,

look for some Acer software installed on your computer that may reinstall the OEM driver and uninstall it. Also follow the above posts to disable Windows Update from overriding it. If you have a specific issue, please open a new thread.

Good luck,
werty

I updated to 25H2 and was reverted as I guess it removed the previous block.

I got the latest update via the IDSA. Can't see the older driver in the optional driver updates. Took the update script and saved it.

Will update the thread if issues / rollback occurs.