Display Driver Uninstaller Thread

Do you mean the devcon restart?
If so, I tried but it didn't work
Only true fix is cleaning In safemode
Or use the option to auto restart the computer after cleaning.
It's a driver bug not releasing ressources correctly and sadly can't do anything about it (I think) but I'm still checking what I could possibly do... But as far as I know people are almost always cleaning with the restart option. So no problem

 

Yea, that's what I meant.

 

Yeah I tried but nope.. Not working. Do you encounter the bug often on nvidia or AMD?
Personally I only encountered it with old 306.x driver

 

Actually the last time I saw the bug was when the new buttons for DDU were implemented.

 

Coincidence. The code that clean was not changed. Just some bad luck

N next version I'll also clean all the old monitor that never get removed. Maybe it will help who knows.... I had like over 60 pnp/non pnp monitor .

 

Well so long there is no conflict when installing a new monitor I don't see a problem with cleaning up drivers left behind.

 

They are mostly hidden and disabled device anyway. Windows just never throw them away... it will probably do no impact.

TO see how much you have you can have a look at : "devcon findall =monitor"

without the quote.

You may be surprised....

 

Yea, I already know about them, saw them in the registry and also in device manager.

The Findall Command displayed 64 Hidden monitor drivers.

 

5.1.1 Released
-Fix a crash for those with Binary keyvalue in registry

 

Hi Wagnard, tried your uninstaller v.5.1.1 yesterday during Catalyst 13.8 beta 2 upgrade (unable to update driver via CIM directly, some errors occured) without any issue and with great results .

Great tool, keep up the good work mate

 

Eh. did you mean you had problem before and now after using DDU its fixed?

 

I think he meant it resolved the issues he was having after using DDU.

Other Thoughts
While the cleaner works as it should, it's missing a cleaning path in which the
driver version also gets removed. This is necessary because an existing driver version left behind by a previous uninstall can cause users to not be able to re-install the same driver. Therefore they would either have to upgrade or downgrade their driver.

 

Cleaning path? more details please.
I dont know where is this existing driver version left you are talking about and never had a problem reinstalling the same driver over and over after using DDU.
Care to explain and point me to the right direction ?

 

Yes, sometimes driver installation gets broken in which it displays the following error "Driver Install: the installation failed." This is due to the driver version not being cleaned therefore the driver install fails. The only way to get around it is either by changeing the driver version or through removal which I am currently not aware of so I can't quite say where you should look.

 

It does not get broken after using DDU right?

Normally DDU should remove any trace of earlier driver.

 

Of course not, it was mention to further the cleaning process of DDU so Users can have a better experience when installing their Graphic Driver.

 

I would have to find this missing part. But it may be quite hard as the issue is pretty vague.

DO you known when this issue arise if the Catalyst install manager show that an earlier version was there?
if so I may have a little idea of what can be clean to remove this.

 

Here, is another piece of info. Installing the driver through device manger then removing again through device manger resolves the the issue.

 

SO it seem its the AMD installation software that is picky about it...
Is this a problem you known how to reproduce? so I can test on my system.

 

This is a right thought dellon.....something like that happened to me when installing for the first time the hdmi driver (do you remenber the .7702 that gives the sound tab in CCC ??) in kevs 13.1 R......the system prevented his installation because existing same driver version left behind (and even broken) in a previous uninstall.

EDIT: right dellon, now I remember, even for me there was the following error "Driver Install: the installation failed." poped up after installation failer.