Universal Intel Chipset Drivers Updater​

on an old gigabyte motherboard with Skylale chipset, version 2026.08.0017 totally disables internal audio (realtek), I had to use Windows 11 restore point

hitman72ita เขียน:

on an old gigabyte motherboard with Skylale chipset, version 2026.08.0017 totally disables internal audio (realtek), I had to use Windows 11 restore point



 

Thanks for reporting this. Just to clarify: `2026.08.0017` is the version of the Universal Intel Device Updater, not the Intel chipset INF version itself. On Skylake, the updater installs the applicable Intel chipset INF files such as `SkylakeSystem.inf`, `SkylakeSystemGMM.inf` and `SkylakeSystemThermal.inf`. These are chipset/system INFs; they do not contain Realtek audio or Intel SST audio drivers.

So the updater does not directly install or replace the Realtek audio driver. However, the fact that the audio stopped working immediately after the INF installation is worth investigating. Installing chipset INFs can trigger Windows Plug and Play re-enumeration and driver re-evaluation, so it is technically possible that something changed in the device state or driver binding.

If you can reproduce the issue, could you please collect the following?

1. Before running version `2026.08.0017`, when audio is working:

• Share your `C:\Windows\INF\setupapi.dev.log`

2. Immediately after installing the updater, when the Realtek audio is no longer working:

• Share your another copy of `C:\Windows\INF\setupapi.dev.log`
• Check Device Manager → Sound, video and game controllers and also System devices.
• Please note whether the Realtek/High Definition Audio device:
  • disappears completely,
  • appears with a yellow warning icon,
  • or remains present but reports an error (e.g. Code 10, 28 or 31).

3. If possible, after restoring the Windows restore point and getting the audio back:

• Share another copy of `C:\Windows\INF\setupapi.dev.log`

The before/after `setupapi.dev.log` files are particularly useful because they are Windows SetupAPI/PnP logs, not just Intel installer logs. They may show which devices were re-enumerated and which INF/driver packages Windows selected during the update.

If you can also provide the motherboard's exact Gigabyte model, that would be very helpful, because "Skylake" covers several different desktop platforms.

With those details we should be able to determine whether the chipset INF installation actually changed the audio device/driver state, or whether the timing was coincidental.

Something to consider, as far as which is the deciding factor: driver version vs. driver date? Driver Fusion opts for the newer DRIVER DATE, while Driver Genius opts for the newer DRIVER VERSION. So; for Intel Chipset drivers, the newer driver version may end up being dated JULY, 1968, when allowing Driver Genius to make the decision. If using Driver Fusion, the older driver by version number but newer by date will be picked for installation. 
Also note: Intel's own Chipset installation software will follow the same option path as Driver Fusion, so that the driver date is considered more important than the driver version number. 
If you compare the end result (installed using Intel's own latest version of Chipset software) after a brand-new fresh Windows installation, compared with the end result after first using Windows Update and other 3rd-party driver update software, you end up with a different list of Chipset driver versions.  
Note for audio ussues: there's a free software "Display Driver Uninstaller" that includes the option to clean out remnants of Realtek Audio drivers. Should be run while booted into Safe Mode. Then reboot into Normal Mode, & then run the full "Setup.exe" Realtek Audio installer.

I forgot to mention that the updater now supports the latest Intel Chipset Device Software installer ( v10.1.20658.8883 )

Additionally, I've created a tracking issue on GitHub for the audio problems reported after Intel chipset INF updates: github.com/FirstEverTech/Universal-Intel...et-Updater/issues/31
It covers both the Realtek issue on Gigabyte Skylake and the Creative Sound Blaster issue on EVGA X299 Dark. If you have any additional details or logs to share, please post them there – it will help me investigate and resolve these conflicts more effectively.