DriverStoreExplorer icon indicating copy to clipboard operation
DriverStoreExplorer copied to clipboard

Newer (beta versions) not able to delete drivers, despite success message

Open achtchaern opened this issue 10 months ago • 10 comments

Hi there, I'm using the latest pre-release version to remove HP drivers and software components from a HP laptop. DSE says it successfully removed the component, but in reality, it didn't remove anything. Forcing the removal doesn't help. Tried with both interfaces (DISM and native driver store).

However, the latest stable version (v0.11.114) was able to remove these components.

achtchaern avatar Feb 10 '25 11:02 achtchaern

There is no change in DISM logic in beta versions. Also, the native driver store still uses the same method to delete drivers from store. It is possible that it takes some time for the driver store to reflect the change (usually instant).

lostindark avatar Feb 10 '25 16:02 lostindark

I didn't want to submit an issue based off the same thing, but I feel like it may be leading up to something and I felt like it would be a good opportunity before you tweak it to the point where you might lose track of what this "bug" is. The most recent stable version instantly removes the drivers, but all the latest pre-release versions do not, the all 3 of them.

Versions: 0.12.4, 0.12.12, 0.12.14.

Native/Local store/DISM... A refresh does not resolve it and neither does a reboot.

I even tried using take ownership context menu registry tweak against the target folders and even then, it doesn't remove the drivers.

The test I came up with that subjectively worked was taking ownership of the target folder and deleting it manually through explorer file manager. Eeeh..

Anyway. I confirm OP's statement.

BubbleSquish avatar Feb 14 '25 22:02 BubbleSquish

That's very weird. The new beta version uses native driver store API to list/export drivers. But delete driver part is not changed. It is the same code as the latest stable version. Also, if you select use DISM, it uses the same code as the latest stable version.

Anyway to reliably repro the issue?

lostindark avatar Feb 15 '25 03:02 lostindark

Hi @lostindark, I have the same problem as described above. After removing the driver, closing the app, reopening it, and scanning from the beginning, the 'deleted' driver is still there.

PS: This happens with both DISM and the Native Store Driver.

CoodyCZ avatar Feb 16 '25 08:02 CoodyCZ

I didn't want to submit an issue based off the same thing, but I feel like it may be leading up to something and I felt like it would be a good opportunity before you tweak it to the point where you might lose track of what this "bug" is. The most recent stable version instantly removes the drivers, but all the latest pre-release versions do not, the all 3 of them.

Versions: 0.12.4, 0.12.12, 0.12.14.

Native/Local store/DISM... A refresh does not resolve it and neither does a reboot.

I even tried using take ownership context menu registry tweak against the target folders and even then, it doesn't remove the drivers.

The test I came up with that subjectively worked was taking ownership of the target folder and deleting it manually through explorer file manager. Eeeh..

Anyway. I confirm OP's statement.

weird. on my Win10 LTSC 2021 x64 computer, versions 0.12.4 & 0.12.12 can properly remove/delete the old drivers. versions 0.12.17, 0.12.30 & 0.12.40, on the other hand, do not remove the old drivers. I haven't tested these under Win11 though.

OP & others need to mention what Windows version & DriverStore versions they're using when trying to reproduce this problem

epman100 avatar Mar 04 '25 00:03 epman100

Please try 0.12.55 and see if that works.

lostindark avatar Mar 06 '25 17:03 lostindark

Please try 0.12.55 and see if that works.

this one works great and correctly removes the drivers. time to close this issue

epman100 avatar Mar 07 '25 17:03 epman100

Maybe it only affected drivers (or software components associated to a driver) that are still in use. I'll report back as soon as I get another opportunity to test.

achtchaern avatar Mar 10 '25 09:03 achtchaern

@achtchaern any update on this?

dreamsyntax avatar Apr 17 '25 21:04 dreamsyntax

No new opportunity to test it yet, unfortunately. The issue was not easily reproducable, it just happened with drivers / software components that were in active use. Sorry!

achtchaern avatar Apr 23 '25 09:04 achtchaern