DriverStoreExplorer
DriverStoreExplorer copied to clipboard
lostindark
Removing Intel BT drivers causes corruption of Intel iGPU drivers - failing to boot Windows
This is the second time this has happened in a few months and at first I was very confused about the reason, but now I think I've narrowed it down to DriverStoreExplorer being the culprit.
I've been using DriverStoreExplorer succesfully for years and I love it, but this is a major issue:
At the end of April, Intel issued a regular Bluetooth driver update, version 23.130.0, here. After installing this - and then using DriverStoreExplorer after a reset - I was failing to boot into Windows 11, the display was flashing and bugging out at Windows load screen.
Safemode worked fine, and if I disabled iGPU in the bios, it would boot fine too. It became apparent that the iGPU drivers had seemingly become corrupt, and reinstalling them fixed the issue. DDU'ing them again and rebooting caused the boot failure once again. Reinstalling fixed again.
I wrote this off as a Windows bug, but now it has happened again!
Intel released another Blueooth update a few days ago, and what do you know, the exact same thing happened. I updated the BT drivers, restarted, then used DSE, and using DriverStoreExplorer resulted in it also messing with the existing Intel iGPU drivers (even though the logs show nothing like that) and Windows was failing to boot once again! I confirmed it messed with the iGPU drivers because after doing this, Device Manager showed an error with the iGPU whereas before that, it was fine.
Prior to all of this, I had been doing this same process with Bluetooth updates & then running DSE for several months and several updates beforehand with zero issues. So it must be either due to a recent update with DSE, or maybe Intel's drivers, or both.
I have attached logs of the two situations here:
[Information]: ---------------------------------------------------------------
2025-05-01 11:16:51Z [Information]: Rapr started
2025-05-01 11:16:51Z [Information]: Scanning driver store...
2025-05-01 11:16:55Z [Information]: Ready
2025-05-01 11:17:31Z [Information]: Selected 10 Driver(s). Total size: 66 MB.
oem16.inf - ibtusb.inf_amd64_98627392c54406cf - 6 MB
oem19.inf - ibtusb.inf_amd64_b46448e1bdb9ef9e - 6 MB
oem22.inf - ibtusb.inf_amd64_a6e3ddb941fffa36 - 17 MB
oem25.inf - cui_dch.inf_amd64_86fcac3729b8f2a0 - 21 MB
oem26.inf - mshdadac.inf_amd64_2a27c6b7b8211840 - 100 KB
oem29.inf - hdbusext.inf_amd64_9faca1e9dfada1d4 - 69 KB
oem6.inf - ibtusb.inf_amd64_f9cee72ffc8e6c9d - 2 MB
oem7.inf - ibtusb.inf_amd64_c8d2e1e81b8275be - 4 MB
oem8.inf - ibtusb.inf_amd64_715703e6b15a6fc5 - 9 MB
oem9.inf - ibtusb.inf_amd64_43e6d4f6b64ec5a8 - 2 MB
2025-05-01 11:17:47Z [Information]: Deleting driver package(s)...
oem16.inf - ibtusb.inf_amd64_98627392c54406cf - 6 MB
oem19.inf - ibtusb.inf_amd64_b46448e1bdb9ef9e - 6 MB
oem22.inf - ibtusb.inf_amd64_a6e3ddb941fffa36 - 17 MB
oem6.inf - ibtusb.inf_amd64_f9cee72ffc8e6c9d - 2 MB
oem7.inf - ibtusb.inf_amd64_c8d2e1e81b8275be - 4 MB
oem8.inf - ibtusb.inf_amd64_715703e6b15a6fc5 - 9 MB
oem9.inf - ibtusb.inf_amd64_43e6d4f6b64ec5a8 - 2 MB
oem29.inf - hdbusext.inf_amd64_9faca1e9dfada1d4 - 69 KB
oem25.inf - cui_dch.inf_amd64_86fcac3729b8f2a0 - 21 MB
oem26.inf - mshdadac.inf_amd64_2a27c6b7b8211840 - 100 KB
2025-05-01 11:17:48Z [Information]: Deletion of oem16.inf (ibtusb.inf_amd64_98627392c54406cf) succeeded.
2025-05-01 11:17:48Z [Information]: Deletion of oem19.inf (ibtusb.inf_amd64_b46448e1bdb9ef9e) succeeded.
2025-05-01 11:17:48Z [Information]: Deletion of oem22.inf (ibtusb.inf_amd64_a6e3ddb941fffa36) succeeded.
2025-05-01 11:17:48Z [Information]: Deletion of oem6.inf (ibtusb.inf_amd64_f9cee72ffc8e6c9d) succeeded.
2025-05-01 11:17:48Z [Information]: Deletion of oem7.inf (ibtusb.inf_amd64_c8d2e1e81b8275be) succeeded.
2025-05-01 11:17:48Z [Information]: Deletion of oem8.inf (ibtusb.inf_amd64_715703e6b15a6fc5) succeeded.
2025-05-01 11:17:48Z [Information]: Deletion of oem9.inf (ibtusb.inf_amd64_43e6d4f6b64ec5a8) succeeded.
2025-05-01 11:17:48Z [Information]: Deletion of oem29.inf (hdbusext.inf_amd64_9faca1e9dfada1d4) succeeded.
2025-05-01 11:17:48Z [Information]: Deletion of oem25.inf (cui_dch.inf_amd64_86fcac3729b8f2a0) succeeded.
2025-05-01 11:17:48Z [Information]: Deletion of oem26.inf (mshdadac.inf_amd64_2a27c6b7b8211840) succeeded.
2025-05-01 11:17:48Z [Information]: Removed 10 packages from driver store.
2025-05-01 11:17:56Z [Information]: Shutting down - reason UserClosing
[Information]: ---------------------------------------------------------------
2025-06-12 05:08:01Z [Information]: Rapr started
2025-06-12 05:08:02Z [Information]: Scanning driver store...
2025-06-12 05:08:04Z [Information]: Ready
2025-06-12 05:08:05Z [Information]: Selected 7 Driver(s). Total size: 41 MB.
oem11.inf - ibtusb.inf_amd64_c71affe061d44c25 - 6 MB
oem12.inf - ibtusb.inf_amd64_b99994b9e51958bd - 17 MB
oem2.inf - ibtusb.inf_amd64_0ca6cbb6fc262ba6 - 2 MB
oem4.inf - ibtusb.inf_amd64_1bfe5919602b86a4 - 4 MB
oem6.inf - ibtusb.inf_amd64_c4827b16f60380ab - 9 MB
oem7.inf - ibtusb.inf_amd64_56bdb87db7e683b1 - 2 MB
oem8.inf - ibtusb.inf_amd64_22fe950daa024237 - 2 MB
2025-06-12 05:08:25Z [Information]: Deleting driver package(s)...
oem11.inf - ibtusb.inf_amd64_c71affe061d44c25 - 6 MB
oem12.inf - ibtusb.inf_amd64_b99994b9e51958bd - 17 MB
oem2.inf - ibtusb.inf_amd64_0ca6cbb6fc262ba6 - 2 MB
oem4.inf - ibtusb.inf_amd64_1bfe5919602b86a4 - 4 MB
oem6.inf - ibtusb.inf_amd64_c4827b16f60380ab - 9 MB
oem7.inf - ibtusb.inf_amd64_56bdb87db7e683b1 - 2 MB
oem8.inf - ibtusb.inf_amd64_22fe950daa024237 - 2 MB
2025-06-12 05:08:25Z [Information]: Deletion of oem11.inf (ibtusb.inf_amd64_c71affe061d44c25) succeeded.
2025-06-12 05:08:25Z [Information]: Deletion of oem12.inf (ibtusb.inf_amd64_b99994b9e51958bd) succeeded.
2025-06-12 05:08:25Z [Information]: Deletion of oem2.inf (ibtusb.inf_amd64_0ca6cbb6fc262ba6) succeeded.
2025-06-12 05:08:25Z [Information]: Deletion of oem4.inf (ibtusb.inf_amd64_1bfe5919602b86a4) succeeded.
2025-06-12 05:08:26Z [Information]: Deletion of oem6.inf (ibtusb.inf_amd64_c4827b16f60380ab) succeeded.
2025-06-12 05:08:26Z [Information]: Deletion of oem7.inf (ibtusb.inf_amd64_56bdb87db7e683b1) succeeded.
2025-06-12 05:08:26Z [Information]: Deletion of oem8.inf (ibtusb.inf_amd64_22fe950daa024237) succeeded.
2025-06-12 05:08:26Z [Information]: Removed 7 packages from driver store.
2025-06-12 05:08:27Z [Information]: Shutting down - reason UserClosing
And additionally, here is a log showing me removing the iGPU drivers on a separate occasion, in between these two events:
[Information]: ---------------------------------------------------------------
2025-06-10 03:04:42Z [Information]: Rapr started
2025-06-10 03:04:42Z [Information]: Scanning driver store...
2025-06-10 03:04:45Z [Information]: Ready
2025-06-10 03:04:46Z [Information]: Selected 6 Driver(s). Total size: 2.3 GB.
oem12.inf - cui_dch.inf_amd64_390710eac6fdead0 - 21 MB
oem13.inf - mshdadac.inf_amd64_40ddf9929380c1d7 - 100 KB
oem14.inf - hdbusext.inf_amd64_79892ac42ccffa59 - 69 KB
oem2.inf - netwtw08.inf_amd64_66062b2ba0b1f9b7 - 81 MB
oem4.inf - netwtw6e.inf_amd64_e54b51f2feabd3c5 - 57 MB
oem9.inf - iigd_dch.inf_amd64_9db6816fe4d1e6f9 - 2.2 GB
2025-06-10 03:05:11Z [Information]: Deleting driver package(s)...
**oem9.inf - iigd_dch.inf_amd64_9db6816fe4d1e6f9 - 2.2 GB**
oem14.inf - hdbusext.inf_amd64_79892ac42ccffa59 - 69 KB
oem2.inf - netwtw08.inf_amd64_66062b2ba0b1f9b7 - 81 MB
oem4.inf - netwtw6e.inf_amd64_e54b51f2feabd3c5 - 57 MB
oem12.inf - cui_dch.inf_amd64_390710eac6fdead0 - 21 MB
oem13.inf - mshdadac.inf_amd64_40ddf9929380c1d7 - 100 KB
2025-06-10 03:05:12Z [Information]: Deletion of oem9.inf (iigd_dch.inf_amd64_9db6816fe4d1e6f9) succeeded.
2025-06-10 03:05:12Z [Information]: Deletion of oem14.inf (hdbusext.inf_amd64_79892ac42ccffa59) succeeded.
2025-06-10 03:05:12Z [Information]: Deletion of oem2.inf (netwtw08.inf_amd64_66062b2ba0b1f9b7) succeeded.
2025-06-10 03:05:13Z [Information]: Deletion of oem4.inf (netwtw6e.inf_amd64_e54b51f2feabd3c5) succeeded.
2025-06-10 03:05:13Z [Information]: Deletion of oem12.inf (cui_dch.inf_amd64_390710eac6fdead0) succeeded.
2025-06-10 03:05:13Z [Information]: Deletion of oem13.inf (mshdadac.inf_amd64_40ddf9929380c1d7) succeeded.
2025-06-10 03:05:13Z [Information]: Removed 6 packages from driver store.
2025-06-10 03:05:16Z [Information]: Shutting down - reason UserClosing
Everything was fine after removing the old iGPU drivers in that final log, it was only after both of the previous two Bluetooth removals that issues occurred with the iGPU. If that makes sense.
It seems like somehow, DSE is messing with iGPU drivers - or maybe something else? When it removes Intel BT drivers.
Hardware:
Motherboard: ASRock Z890 Pro-A Wifi CPU: Intel 245K GPU: NVIDIA 4070Ti Super RAM: 2x 16gb Windows: 24H2, latest version Chipset, drivers, etc: All latest versions.
Don't mess with intel drivers. They are horrible. You will also get this issue using windows builtin tools to remove the drivers. Use intel's own uninstaller instead.
Don't mess with intel drivers. They are horrible. You will also get this issue using windows builtin tools to remove the drivers. Use intel's own uninstaller instead.
But this process including using DSE for Intel BT and also iGPU drivers has been fine for many months and many updates prior to this event. So it's something recent surely.
Does Intel even have its own uninstaller for old drivers? That's the point of DSE - removing the leftover, old, unused crud. Intel only provides actual uninstallers, that remove current drivers, as far as I know.
corruption of Intel iGPU drivers - failing to boot Windows
Normal Intel install causes corruption of iGPU drivers. Not even bluescreen, it just dies. I have to update the Intel iGPU driver while booting using Nvidia GPU.
corruption of Intel iGPU drivers - failing to boot Windows
Normal Intel install causes corruption of iGPU drivers. Not even bluescreen, it just dies. I have to update the Intel iGPU driver while booting using Nvidia GPU.
What do you mean? Intel install of what exactly? I can install Intel iGPU drivers fine.
Try booting into safe mode I assume that should use the default display driver allowing you to install the intel drivers or boot to a windows usb / win pe and try adding the driver inf using dism to the offline windows image
Try booting into safe mode I assume that should use the default display driver allowing you to install the intel drivers or boot to a windows usb / win pe and try adding the driver inf using dism to the offline windows image
Thanks, but this has been mentioned in the original post (sorry if it got lost in the details) - yes, it did boot fine into safe mode and from there, the iGPU drivers could be installed again.
That's not the problem though. The problem is that DSE seemingly removed or corrupted the iGPU drivers - or even Window's driver stack itself - when removing the old Intel BT drivers. And it didn't remove them cleanly either - it resulted in Windows not even booting at all (even though the primary GPU is a dedicated Nvidia GPU and the iGPU should have no bearing on windows booting).
Using DSE to clean the old iGPU drivers works fine. It's just when DSE tries to remove old BT drivers that this occurs.
This has happened twice now, since May.
could you post a screenshot of what it looks like prior to hitting delete as im pretty sure you selected display driver inf's as well judging from the driver names and mb for not realizing you fixed it already
could you post a screenshot of what it looks like prior to hitting delete as im pretty sure you selected display driver inf's as well judging from the driver names and mb for not realizing you fixed it already
Many thanks.
It's pretty hard to provide a screenshot now as it's already happened. But I tried to highlight the iGPU driver in the 3rd log (the 3rd log is to show what a normal iGPU driver removal looks like, without removing BT drivers at same time):
oem9.inf - iigd_dch.inf_amd64_9db6816fe4d1e6f9 - 2.2 GB
That file there is the iGPU driver, or main part of it anyway.
I don't think I removed iGPU drivers during either of the previous two logs.
From what I’ve found, the cui_dch INF file seems to be related to graphics (just a quick observation, not implying anything negative). So, it’s likely the culprit in the second log. As for the first log, it appears all the entries are related to Bluetooth, based on their names. You could export the driver and check the device IDs in the INF file to see if they correspond to your graphics hardware, but it’s also possible that Intel is being quirky and unnecessarily relying on it. I don’t use Intel myself, so this is just speculation on my part.
Considering that RAPR uses native Windows components to remove drivers, I doubt this issue is related to RAPR itself. It's more likely something Intel changed since the last time you used RAPR to remove the drivers you wanted. Again, that's just speculation, as I have no insight into the specifics of Intel's updates.
Either way, it's good to hear that you're up and running now! If you run into issues in the future, you can always add the device’s hardware ID to the group policy to block new driver updates, which will prevent Windows Update from breaking your setup.
See: https://www.tenforums.com/tutorials/146562-prevent-windows-update-updating-specific-device-driver.html
Might be an idea for RAPR to include this even tho it might be outside the scope of the project
From what I’ve found, the cui_dch INF file seems to be related to graphics (just a quick observation, not implying anything negative). So, it’s likely the culprit in the second log. As for the first log, it appears all the entries are related to Bluetooth, based on their names. You could export the driver and check the device IDs in the INF file to see if they correspond to your graphics hardware, but it’s also possible that Intel is being quirky and unnecessarily relying on it. I don’t use Intel myself, so this is just speculation on my part.
Considering that RAPR uses native Windows components to remove drivers, I doubt this issue is related to RAPR itself. It's more likely something Intel changed since the last time you used RAPR to remove the drivers you wanted. Again, that's just speculation, as I have no insight into the specifics of Intel's updates.
Either way, it's good to hear that you're up and running now! If you run into issues in the future, you can always add the device’s hardware ID to the group policy to block new driver updates, which will prevent Windows Update from breaking your setup.
See: https://www.tenforums.com/tutorials/146562-prevent-windows-update-updating-specific-device-driver.html
Might be an idea for RAPR to include this even tho it might be outside the scope of the project
Many thanks for your input - all the knowledge and thoughts are welcome to help try and diagnose the actual issue here.
You're right, it could be that this is something Intel has done and they have somehow intertwined their drivers. If so - that might also be something that a program like DSE could/should be able to grapple with - either (best case) by implementing a workround, or worse case by implementing a warning before removing them, for example. I mean, DSE is somewhat failing its prime objective with the outcome from this (no offense to DSE - I love this app).
For future mishaps, I do have windows blocking drivers. FWIW I update the BT and the iGPU (both Intel) via the Intel Driver Assistant, manually, when it alerts me to new drivers. Ideally one shouldn't have to remain on old drivers indefinitely. But for now it might be the only option.
I should re-iterate though - I provided 3 logs above, and the first two didn't have (or at least, I don't think they had) the iGPU drivers removed. Only the 3rd one did IIRC. But I could be wrong.
corruption of Intel iGPU drivers - failing to boot Windows
Normal Intel install causes corruption of iGPU drivers. Not even bluescreen, it just dies. I have to update the Intel iGPU driver while booting using Nvidia GPU.
What do you mean? Intel install of what exactly? I can install Intel iGPU drivers fine.
Well, I can't.
Just as a suggestion - potentially, this conflict may be a result of Intel's addition/usage of oneAPI Level Zero, which I noticed appeared as an optional component in the iGPU drivers around the time this started.
Devs, do you have any thoughts about this?
Updating with some new info on this issue.
I just did a clean Windows reinstall and got the latest version of DSE. I installed the Intel Bluetooth drivers and did not install the iGPU drivers.
Despite having only just installed BT drivers for the first time, DSE still marks parts of the BT drivers as 'old'.
This is what DSE shows:
Surely this is a problem - these should not be 'old' files, right?
I'd like to ask a question here. My desktop processor has an Intel KF suffix. Does this mean I don't need to install the Intel Graphics Accelerator Driver? Or is it useless even if I install it?
KF means no integrated graphics. K are the ones with integrated GPU, KF are the ones without. So yeah, pointless to install integrated graphics drivers.
Best way you can see for yourself is to install Intel Driver Support Assistant which will scan your hardware and suggest any drivers needed. In your case, yeah, it won't suggest any graphics drivers.
On Fri, 1 Aug 2025, 2:19 am a1waysbeta, @.***> wrote:
a1waysbeta left a comment (lostindark/DriverStoreExplorer#353) https://github.com/lostindark/DriverStoreExplorer/issues/353#issuecomment-3140169565
I'd like to ask a question here. My desktop processor has an Intel KF suffix. Does this mean I don't need to install the Intel Graphics Accelerator Driver? Or is it useless even if I install it?
— Reply to this email directly, view it on GitHub https://github.com/lostindark/DriverStoreExplorer/issues/353#issuecomment-3140169565, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQ5WB52LDII72SVUWP2SRQD3LIQVXAVCNFSM6AAAAAB7GTROFOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCNBQGE3DSNJWGU . You are receiving this because you authored the thread.Message ID: @.***>
@lostindark I notice the latest version, 0.12.100, no longer checks/marks these Intel Bluetooth drivers as being "old" - thank you!!
I'm still confused about whether the drivers in question (see my previous image) are actually old/unused or whether they're still being used somehow - it seems very weird to me that there's a dozen BT drivers with the same version - but at least I can safely use the program again.
Do you have any thoughts about this?
Thanks so much for the update!
@lostindark I notice the latest version, 0.12.100, no longer checks/marks these Intel Bluetooth drivers as being "old" - thank you!!
I'm still confused about whether the drivers in question (see my previous image) are actually old/unused or whether they're still being used somehow - it seems very weird to me that there's a dozen BT drivers with the same version - but at least I can safely use the program again.
Do you have any thoughts about this?
Thanks so much for the update!
I'm not a driver expert and I don't know why Intel Bluetooth driver have so many entries (same version) and only one is associated with the actual device. For now, I updated the tool to keep them all if they're the same version.
I looked at above logs and noticed that both the bluetooth and iGPU driver used oem9.inf. oem9.inf - ibtusb.inf_amd64_43e6d4f6b64ec5a8 - 2 MB oem9.inf - iigd_dch.inf_amd64_9db6816fe4d1e6f9 - 2.2 GB
Maybe somehow it get mixed up. Not sure if it is an Intel driver bug, or Windows bug.
@lostindark I don't want to post this separately, so I'd like to ask here. My pnputil option is grayed out. Why?
@lostindark I don't want to post this separately, so I'd like to ask here. My pnputil option is grayed out. Why?
Current implementation of the pnputil doesn't work with the pnputil version on Windows 11, so it is been disabled as well.
@lostindark I notice the latest version, 0.12.100, no longer checks/marks these Intel Bluetooth drivers as being "old" - thank you!! I'm still confused about whether the drivers in question (see my previous image) are actually old/unused or whether they're still being used somehow - it seems very weird to me that there's a dozen BT drivers with the same version - but at least I can safely use the program again. Do you have any thoughts about this? Thanks so much for the update!
I'm not a driver expert and I don't know why Intel Bluetooth driver have so many entries (same version) and only one is associated with the actual device. For now, I updated the tool to keep them all if they're the same version.
I looked at above logs and noticed that both the bluetooth and iGPU driver used oem9.inf. oem9.inf - ibtusb.inf_amd64_43e6d4f6b64ec5a8 - 2 MB oem9.inf - iigd_dch.inf_amd64_9db6816fe4d1e6f9 - 2.2 GB
Maybe somehow it get mixed up. Not sure if it is an Intel driver bug, or Windows bug.
Many thanks!
I just noticed something; today there was another Bluetooth update for me, and after installing it, DSE didn't show any 'old' drivers (i.e - the previous version). All of the listed Bluetooth drivers are the current version, but none of the previous drivers/driver versions were visible or available to remove.
I even checked 'include boot critical drivers' but still didn't show up.
corruption of Intel iGPU drivers - failing to boot Windows
Normal Intel install causes corruption of iGPU drivers. Not even bluescreen, it just dies. I have to update the Intel iGPU driver while booting using Nvidia GPU.
What do you mean? Intel install of what exactly? I can install Intel iGPU drivers fine.
Well, I can't.
Just an update: last version on Intel iGPU driver from days ago installs without blackscreen now. This is fixed and this was unrelated to this issue, I think (?).
corruption of Intel iGPU drivers - failing to boot Windows
Normal Intel install causes corruption of iGPU drivers. Not even bluescreen, it just dies. I have to update the Intel iGPU driver while booting using Nvidia GPU.
What do you mean? Intel install of what exactly? I can install Intel iGPU drivers fine.
Well, I can't.
Just an update: last version on Intel iGPU driver from days ago installs without blackscreen now. This is fixed and this was unrelated to this issue, I think (?).
Good on you for providing the info anyway, but yes this is unrelated to this specific issue.