IGCIT / Intel-GPU-Community-Issue-Tracker-IGCIT

IGCIT is a Community-driven issue tracker for Intel GPUs.
GNU General Public License v3.0
113 stars 3 forks source link

Windows 11 update always rolls back Intel iGPU drivers after manual driver update through Intel driver setup #812

Closed makedir closed 1 day ago

makedir commented 6 days ago

Checklist [README]

Application [Required]

Windows

Processor / Processor Number [Required]

N100

Graphic Card [Required]

N100

GPU Driver Version [Required]

31.0.101.5594

Other GPU Driver version

No response

Rendering API [Required]

Windows Build Number [Required]

Other Windows build number

No response

Intel System Support Utility report

ssu.txt

Description and steps to reproduce [Required]

Update iGPU drivers. Next reboot Windows 11 update will download older drivers and rollback.

Tried the following workarounds, none are working:

https://www.elevenforum.com/t/enable-or-disable-include-drivers-with-windows-updates-in-windows-11.2232/

Solution as Option 2, does not work for Home edition.

https://www.intel.com/content/www/us/en/support/articles/000087834/graphics.html

Solution to make non clean intall in this post does not help.

Problem exists only in Windows 11 Home edition, if you have Windows 11 Pro, you can use gpedit to disable driver updates through Windows update.

Suggestions:

Please communicate with Microsoft to find a solution to this issue. Either make all driver updates optional, and user can decide which are installed. Or give an optional toggle button to disable drivers in Windows 11 settings, or/better, give more in detail options, for example to exclude GPU driver updates through Windows update, or give option, that newer installed drivers are never rolledback, also optional.

Only working workaround, is that you need to go into device manager after Windows 11 update rolled back, then go to Intel iGPU, and select, use last worked driver. Windows will now keep the driver and wont rollback, until you update again manually the driver. I had this issue now several times after I installed 5594, 5593. Maybe because these are not WHQL certified.

Device / Platform

No response

Crash dumps [Required, if applicable]

No response

Application / Windows logs

No response

IGCIT commented 6 days ago

hi @makedir,

this is a widespread issue with how Windows handle updates when OEM drivers are available in their repos, removing user installed drivers with no prompt, and, in many cases, breaking stuff while doing so.

you should probably open a ticket to MS for this, not intel drivers related per se.

the solutions you have tried, are all wrong for this kind of issue, online many still don't know how to properly stop this behaviour so you usually find ineffective solutions.

the correct steps:

download this tool wushowhide.zip (an old windows tool to enable/disable updates in windows update, still working as of today)

1 - run windows update and let windows downgrade your drivers (if you installed the new one and update is already pending) 2 - disconnect from internet 3 - install the new drivers (you may also want use DDU to clear any old drivers) 4 - reboot 6 - reconnect 7 - run the wushowhide tool and select "hide updates" and wait for it to grab the updates available for your device 8 - you should see the OEM drivers, select and hide the update

once done, windows will ignore OEM drivers, from personal experience, even if the OEM pushes a new driver

makedir commented 6 days ago

@IGCIT Yes, I know this is an issue since years with Windows Update. Me making a ticket at MS wont do or change anything. I am not intel. Obviously Intel could easily get someone at MS on the phone or other communication ways and easily solve this is in minutes. When Intel tells MS this is an issue, obviously MS is more open to change this. As a "nobody" it is kinda impossible to report issues to MS.

EstebanIntel commented 4 days ago

Hi @makedir,

We have communicated this issue to Microsoft, so they are aware of it. This is a change that needs to be done on the OS side, not on the driver side. So please raise the ticket to Microsoft.