Display Driver Uninstaller Thread

Display Driver Uninstaller (DDU) V17.0.8.7 Released.

As always, see first post of this thread for download locations and other important information.

 

This is weird:

Why and for what reason? It was working very well, I'm confused why do you change that setting...

 

Because the previous solution was not perfect, didn't work for everyone, user would forget to set the option back to default with button on the right. Disconnecting the internet is the way to do it right.

It's not really hard to just disable the network card and reactivate it after installing the gpu driver.
I know the previous way was more appreciated but it wasn't the right thing to do. I did receive messages to remove it for various reason.
I hope you understand.

 

Ah that's why it didnt work for me, and all keep trollin me I'm doing it wrong

I know older versions worked ok though, thought its now new RS4 fault.

 

Nothing is in hard stone and I can maybe set this optional in the future if I have requests for it.

 

Forcing unwanted changes in os settings... really?

 

I was before (but it was mentioned and explained). One of the reason I'm setting this back to default is I didn't like either the idea of changing a user setting.
17.0.8.7 is sadly still doing it to revert previous changes made by previous version of DDU and the next version 17.0.8.8 will not change this setting anymore.
So if a user change it themself in the registry of group Policy, DDU won't do anything about it.

 

Kaspersky Internet Security doesn't seem to like your software @Wagnard Just a heads up but I guess you hear stuff like this from time to time.

 

It's from the PAExec included with it. I talked with Kaspersky about it and they said it's not a virus and more informatio than anything else. That it also what the name start with : not.a.virus
Until I find a way to avoid using PAExec, we are stuck with this warning.

 

Thanks for replying! You are quite right that it says "not.a.virus", I noticed it just now.

 

Really? This is ridiculous reason, so those users should buy consoles and stop using PC's because it's too difficult for them.

 

That's is what I'm thinking, pro users will change the registry key themselves or edit a GPO. An application like DDU should not make unwanted changes in OS setting as state by @Ancymon
And this will be the case in next version. I'll probably update the Readme on how to do it for the advanced user if they want.

I'm open to suggestions, if you have ideas that respect the "not make unwanted changes in OS setting" I'm full ears.

 

Wagnard, you can make this Windows update option back to ddu but as an option to tick in options menu

 

That is probably what I will do.
Thanks for the feedback.

Edit: A tickbox in the option menu has been added for the next version.

 

Hello
I need help, urgently!

The nvidia installer prevents me from installing the new driver!
I install this version for my nvidia 820M GPU model:
http://www.nvidia.es/download/driverResults.aspx/135759

It gives me Error: "This graphics driver could not find compatible graphic hardware".

Complete the steps to clean the installed driver (former Windows 10 nvidia driver) with DDU v17.0.8.7.
In safe mode started Windows 10.
Clean and restart.
https://www.dropbox.com/s/l5usgqm040io3xy/2018-07-02__14-29-20_DDULog.xml?dl=0
Start the installation of the new driver nvidia 398.36, support GeForce 820M ...

but I still return the same Error!

Help! What I can do?

 

Im checking your logs atm.
Tell me the exact name of the file you downloaded for the 398.36 driver.

 

398.36-notebook-win10-64bit-international-whql.exe - 493MB

 

If you want, I can do a teamviewer session with you and try to fix it directly.
Simply email me the ID and Password that TeamViewer will give you. (wagnard28@gmail.com)

Problem solved: User have a 820M (Fermi based card). Not compatible with latest drivers.

 

Display Driver Uninstaller (DDU) V17.0.8.8 Released.

As always, see first post of this thread for download locations and other important information.

 

Updated to v17.0.8.9 due to a little something I forgot to disable that broke the new option.