Display Driver Uninstaller (DDU) V17.0.0.2 Released.

[Wagnard]

Display Driver Uninstaller (DDU) V17.0.0.1 Released.

ChangeLog:

(17.0.0.0)
-Additional Nvidia cleanUP (based on 372.74)
-DDU can now fix registry key permissions that is preventing it to opening it.(Should not happen on healthy system)
-Show Windows 10 warning only on W10
-Commandline Arguments should be fixed.
-DDUDR is now removed in favor of SetupAPI
-Faster starting will less ressources usage.
-Fixed a possible DDU freeze after launch in Safemode
-Fixed : DDU window is always on top and can't be minimized #31
-Fixed : GetFiles/GetDirectories getting Access Denied on some System dirs
-Fixed : Check update status message when changing language.
-Fixed : GPU Name identification on launch for some driver version.
-Many little fixes and enhancements.

(17.0.0.1)
-Fixed the links.

(17.0.0.2)
-Fixed an OS detection issue that were causing DDU to missed some items.

Important note: Most of these change wouldn't have been possible without the help of a fantastic coder: "devmltk"

SHA1: 15905084A02B10E18EE9069AC0C159BA45C0AC3F

Recommended usage:
-The tool can be used in Normal mode but for absolute stability when using DDU, Safemode is always the best.
-Make a backup or a system restore (but it should normally be pretty safe).
-It is best to exclude the DDU folder completely from any security software to avoid issues.

Official Download Here
If you wish to help DDU, you can make a Donation.

[ShadowFur]

Used 17.0.0.1 to remove Nivida 369.09 from windows 10 annicersary update x64 here is what it missed.

P1.JPG (364.92 KiB) Viewed 21756 times

P2.JPG (385.81 KiB) Viewed 21756 times

P3.JPG (388.63 KiB) Viewed 21756 times

[Wagnard]

Used 17.0.0.1 to remove Nivida 369.09 from windows 10 annicersary update x64 here is what it missed.
P1.JPG
P2.JPG
P3.JPG

Hum this is anormal, can you email me the DDU logs

[ShadowFur]

Sure. and this was the driver from windows update 369.09

[Wagnard]

Sure. and this was the driver from windows update 369.09

I have identifiéled the issue and will fix it as soon as possible when I have some free time.

Edit: Should be fixed with 17.0.0.2

[ShadowFur]

Sure. and this was the driver from windows update 369.09

I have identifiéled the issue and will fix it as soon as possible when I have some free time.

Edit: Should be fixed with 17.0.0.2

Update on that registry keys you asked me to test. It works fine now. nothing left over. Good Job!