Display Driver Uninstaller Thread

Driver Uninstaller (DDU) / Cleaner made for Display Drivers.(NVIDIA/AMD/INTEL)

Display Driver Uninstaller is a driver removal utility that can help you completely uninstall AMD/NVIDIA/Intel graphics card drivers and packages from your system, without leaving leftovers behind (including registry keys, folders and files, driver store).

The AMD/NVIDIA video drivers can normally be uninstalled from the Windows Control panel, this driver uninstaller program was designed to be used in cases where the standard driver uninstall fails, or anyway when you need to thoroughly delete NVIDIA and ATI video card drivers.

The current effect after you use this driver removal tool will be similar as if its the first time you install a new driver just like a fresh, clean install of Windows. As with any tool of this kind, we recommend creating a new system restore point before using it, so that you can revert your system at any time if you run into problems.

This tool act similar to what Driver sweeper do + the extra mentioned above.

If you have problem installing older driver or newer one, give it a try as there are some reports that it fix theses problems.


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 also recommended to put the DDU folder in your antivirus/protection software exclusion list.


-You do NOT need to uninstall the driver before using DDU.

- I would like to gather feedback from you guys. Tell me if it was success or not.
Make a backup or a system restore point , DDU does massive changes to your files / registry

-For people with driver problem, if this tool gave you any success into fixing some issues your are currently experiencing, please share your result.



Keep note that NVIDIA/AMD did not have anything to do with this, I do not work at or for NVIDIA/AMD and they should not be held responsible for anything that may go wrong with this application.


Requirement:
-Windows 7 up to Windows 11 (anything higher is at your own risk)
-NVIDIA, AMD, Intel GPUs
-Also support basic Realtek audio driver cleanup.
-Microsoft .NET Framework 4.8 or higher

DOWNLOAD :

Official DDU Download Website:
wagnardsoft

Official DDU Download Mirror:
Guru3D.com (Official mirror)

SOURCE : Github



USEFUL TIP:

To solve the infinite boot loop issue that some users are having when they select to go into Safe Mode, you must boot with the DVD/USB (Windows installation disk) in recovery with Command prompt and type :

Option 1 (recommended) : bcdedit /deletevalue {default} safeboot

If option 1 is not working,

Option 2 : bootrec /rebuildbcd

There may need to be some adjustment if you have a dualboot system. but if not , it should work correctly.

 

keep it up i might use it someday if you can perfect it, as of now nvidia clean install works wonders to me

 

I get:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ComponentModel.Win32Exception: The system cannot find the file specified
at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
at WindowsApplication1.Form1.Button1_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5472 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
Display Driver Uninstaller
Assembly Version: 1.6.0.0
Win32 Version: 1.6.0.0
CodeBase: file:///H:/Installfiles/Display%20Driver%20Uninstaller.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5468 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.DirectoryServices
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.DirectoryServices/2.0.0.0__b03f5f7f11d50a3a/System.DirectoryServices.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

 

You got that with 1.6.2?
Oh and what's your o. s

 

Yes, win 7 64x, build 7601.

 

Thanks.
I got a small idea what might have done this crash.

Just to be sure, you did uncompress the driver uninstaller and the folder x86 and x64 too?
From the error it sound like it failed to find a file.

Is your o.s. English or another language?

Anyway I'll check that after work today. Thanks for feedback.

 

Did you just run the .exe by it's self? Or as Wagnard said extract it all? I believe it failed to fine the "devcon" program that the program uses.

 

Yeah that's what I think. But it could be others things too. I'm calling cmd.exe and also taskkill. Exe

If systems path are wrong it may fail to find those. But I think more it's like shady said.

Anyway I'm gonna handle error better in the future and will have more detailed logs to help pin point those issues.

 

V1.6.3 Released.

Change for Nvidia users. More logs and a crash fix if devcon is not found with a more proper message.

 

What are you using taskkill and cmd for?
I think what you use those for can be directly in your program instead.

Code:

 
For Each proc as Process In Process.GetProcesses
If proc.ProcessName = "[process you want to kill]" Then
proc.Kill()
End if
Next

 

Depends. For amd I must kill explorer.exe at some point to free holding on some files.
For nvidia, process like the system tray icon for geforce experience.Stuff like that .If I do not, I would not be able to delete all nvidia files/folders because they would still be in-use.

And I will implement it directly into my program at some point.
Do you know if there is also a service stop/kill programatically?
As im doind the same cmd.exe and "sc stop" "sc delete"

 

When I upgrade to my next drivers I will give this try and see if how it goes, I might replace driver sweeper with this. When Doing so I will run driver sweeper in analyze mode to see if it missed anything that driver sweeper would get. As of now I am waiting till nvidia gets out of the 32x.xx series before i decide to upgrade drivers or I get a game that need something newer then 314.07

 

It will miss some. Its not complete yet
For the moment im cleaning what driver sweeper does not and driver sweeper is cleaning what I does not. But this will change

 

so driver sweeper being so old is actual missing stuff I not really surprised by this being its so old at this point. Either way im keep an eye on this cause I have no installed single driver in 10+ years with out using driver sweeper. And never had driver issue as a result unless the issue was literally the driver it self.

Out of curiosity Does your program need to be used in safemode to remove driver like driver sweeper recommends? or can it be used in normal mode??

 

Safe mode is not required.

From my knowledge driver sweeper clean only files. My program actually uninstall the driver , clean the driver store, clean registry key, clean a user account created by geforce experience, clean all nvidia folders /settinngs except the files in windows directory.(will do in the future)

 

driver sweeper does clean registry to

 

tried 1 6 2 but not work for me....still on "unistalling" for 15 minutes..will try the new version..

 

If it does not work, show me the log.

 

Ah weird last time tried on my system,there was only files. Maybe I ran my cleaner before and driver sweeper didnt found reg entry.

 

very nice from you that you provide all this help and fast.really thank you.