Display Driver Uninstaller (DDU) V17.0.8.3 Released.

[Wagnard]

Display Driver Uninstaller (DDU) V17.0.8.3 Released.

Requirement:
-Windows XP up to Windows 10 Fall Creator update 1709 (16299.xx) (anything higher is at your own risk)
-NVIDIA, AMD, Intel GPUs
-Microsoft .NET Framework 3.0 or higher

ChangeLog:

-Added a safety measure that prevent DDU doing the registry cleaning and files/folders removal if a problem with the Windows SETUPAPI is detected.
-Additional NVIDIA cleanup
-Small fixes
-Many translations updates from contibutors (Thanks)

Known issues:
-Translations need updating.

SHA1: 05E914B72880DD60FF149460AA1DE2F9990A7AFC


For a guide , check : https://www.wagnardsoft.com/content/ddu-guide-tutorial

Recommended usage:
-You should disconnect your internet or block Windows Updates.
-DDU should be used when having a problem uninstalling / installing a driver or when switching GPU brand.
-DDU should not be used every time you install a new driver unless you know what you are doing.
-The tool can be used in Normal mode but for absolute stability when using DDU, Safemode is always the best.
-If you are using DDU in normal mode, Clean, reboot, clean again, reboot.
-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.
Note: If you have issues for downloading the file, it could be one of your extension interfering with our hotlink protection.

Official Download Here
If you wish to help DDU, you can make a Donation.
Or
Support us over our PATREON page.


Here is an interesting application from 1 of my partner. It is a useful tool that may help you update outdated drivers.

[vasudev1]

@Wagnard
A wildcard entry for you. I actually found Intel GPU shader cache in this location C:\ProgramData\Intel\ShaderCache
So I just deleted some stuffs except locked process like dwm.exe,explorer.exe, so you might need Nsudo or similar to unlock it and perform deletion at boot. One thing that struck me, why Intel does this silently.
So if anybody noticed stutters or freezes they can try this.
Another important thing I found on Optimus(Intel+Nvidia) or Switchable GFX option (AMD) strange freeze issue can be minimised (If you're using newer hardware like Kepler and above(for Nvidia) OR AMD adrenalin edition desktop GPU drivers for max performance and stability.
I noticed notebook drivers were holding back the performance intentionally and after installing desktop drivers I can Overclock the GPU more w/o hitting TDP limit.

[Wagnard]

@Wagnard
A wildcard entry for you. I actually found Intel GPU shader cache in this location C:\ProgramData\Intel\ShaderCache
So I just deleted some stuffs except locked process like dwm.exe,explorer.exe, so you might need Nsudo or similar to unlock it and perform deletion at boot. One thing that struck me, why Intel does this silently.
So if anybody noticed stutters or freezes they can try this.
Another important thing I found on Optimus(Intel+Nvidia) or Switchable GFX option (AMD) strange freeze issue can be minimised (If you're using newer hardware like Kepler and above(for Nvidia) OR AMD adrenalin edition desktop GPU drivers for max performance and stability.
I noticed notebook drivers were holding back the performance intentionally and after installing desktop drivers I can Overclock the GPU more w/o hitting TDP limit.

For 'C:\ProgramData\Intel\ShaderCache" I'll have a look I do not often check for Intel stuff.
Normally in safe mode, there should not be any issue with lock.

[vasudev1]

Ok Good.
So far, I searched Intel regedit entries and I haven't found Shader cache functionality being explicitly exposed in their UI, so they're doing it w/o letting users know.

[vasudev1]

Wagnard: I ran DDU to directly clean Intel driver instead of Control panel/settings app.
It seems DDU missed these locations

• C:\Program Files\Intel\Media Resource
  C:\Program Files\Intel\Media SDK

[Wagnard]

Wagnard: I ran DDU to directly clean Intel driver instead of Control panel/settings app.
It seems DDU missed these locations

• C:\Program Files\Intel\Media Resource
  C:\Program Files\Intel\Media SDK

Thanks I'll have a look, I don't often check Intel.

[vasudev1]

Wagnard: I ran DDU to directly clean Intel driver instead of Control panel/settings app.
It seems DDU missed these locations

• C:\Program Files\Intel\Media Resource
  C:\Program Files\Intel\Media SDK

Thanks I'll have a look, I don't often check Intel.

Yesterday WD flagged DDU 17.0.8.3 as PUP when I activated PUP detection. Strange thing is, WD didn't flag 17.0.7.2 as PUP. Is it a false +ve?

[Wagnard]

Wagnard: I ran DDU to directly clean Intel driver instead of Control panel/settings app.
It seems DDU missed these locations

• C:\Program Files\Intel\Media Resource
  C:\Program Files\Intel\Media SDK

Thanks I'll have a look, I don't often check Intel.

Yesterday WD flagged DDU 17.0.8.3 as PUP when I activated PUP detection. Strange thing is, WD didn't flag 17.0.7.2 as PUP. Is it a false +ve?

Ya it's false, you can confirm by using www.virustotal.com

[vasudev1]

Thanks I'll have a look, I don't often check Intel.

Yesterday WD flagged DDU 17.0.8.3 as PUP when I activated PUP detection. Strange thing is, WD didn't flag 17.0.7.2 as PUP. Is it a false +ve?

Ya it's false, you can confirm by using www.virustotal.com

Thanks!