Yes, Fox. I have used this setup as well with the Watermark Disabler. But I haven't done fully optimization of last tricks from Redmond Morons... Win 10 1803 April Joke Update. Not sure if I want it on my machine. I don't want put much into it before I know what I want.
I'm sure you have seen what Micro$h4ft Morons want you to use insted of the nice "bcdedit /set {default} bootmenupolicy legacy". And I don't know how many who strugged to find the correct way when they can't boot into windows and try go into safe mode to fix flaws. There is still reviewers/persons who say you can use F8 as normal in Win 10, LOOOL.
-
-
I will continue using Windows 7 and my older/better versions of Windows 10 until they cease to function. I view the updates and support form Micro$loth as being worthless, so when I say "when they cease to function" I mean exactly that. Maybe by then I will no longer consider computers a hobby worth being involved with, or Linux will evolve enough to actually be worth using as a Windows replacement.
Edit: Now that you mention it, I do remember @Mari1225 trying to implement these excellent old bcdedit tweaks on the latest trash from the Redmond Retards, only to find they would not work. We tried to help and it was futile because the newest product is castrated and broken.Last edited: May 17, 2018 -
Thanks @bloodhawk for the heads up. I tried that and it wouldn't work. Only thing it would let me do is boot to bios, then I changed my boot order to my CD/OS install disk. None of the other options would work. When pressed the other option keys, my screen would just flash/flicker once. Only option that would work was the ESC key/ boot to UEFI bios. It was a screen I've never seen before. If I see this screen again (hopefully I dont), I will take a quick pic of it.
@Mr. Fox , DDU version 17.0.8.5 is what I'm on now but there is an update. I just looked into DDU settings and it looks like my settings were reverted back to default (probably from the 3 week old system image)?
Anyway, I got some stuff to do tonight so I wont have time to mess with it. If I knew it wasn't going to crash on me, I would give it a go but the last couple nights have me a bit gun shy
Here is an example of the screen I got except I had a couple more options.
Last edited: May 17, 2018 -
-
...Thanks for that, now at least spamming F8 is an option for me.
Spamming F8 worked, just confirmed it. Reminds me of the good old Windows 7 daysLast edited: May 17, 2018hmscott, Vasudev, Papusan and 1 other person like this. -
-
@Mr. Fox I ran all disk checks and they came back with zero errors.
It's probably something I'm doing wrong I guess.
Not a big problem though, I can just run the Nvidia driver install and perform clean installs until I get the nerve up to try again
Here is a pic of secure boot option turned off in my bios.
-
Well I finally got up the nerve to give it another go. I updated to the latest version of DDU, downloaded driver 391.24, restarted, spammed F8 to get into safemode, ran ddu, restarted, installed new driver. No blue screens and no recoveries
.
Thank you once again @Mr. Fox for giving me the command line/F8 option to better this broken OS.
And thanks to everyone else who lended a hand in helping me with this.Last edited: May 19, 2018 -
Spartan@HIDevolution Company Representative
Display Driver Uninstaller v18.0.0.0
Now supports removal of Realtek Audio Drivers as well!James D, saturnotaku, KY_BULLET and 5 others like this. -
Donald@Paladin44 likes this.
-
Spartan@HIDevolution Company Representative
Secondly, yes it's always better to use driver specialized uninstallation tools to uninstall drivers, that's the sole purpose they were made for and developed.KY_BULLET, Donald@Paladin44, Vaeron and 3 others like this. -
Papusan and Donald@Paladin44 like this.
-
Vasudev, Spartan@HIDevolution, Papusan and 1 other person like this.
-
Wait so you guys dont run the installer when you first get on, do 17 other things, then remember to restart?
-
- Download the driver.
- Restart. Go to Safe Mode.
- Run Display Driver Uninstaller (DDU, restarts automatically).
- Install new driver.
-
Spartan@HIDevolution Company Representative
-
Spartan@HIDevolution Company Representative
-
Interesting that you bumped this today as I just did this this past weekend and had an observation. It appears that removal of the telemetry entries via autoruns now causes GeForce Experience to fail to start properly. Every time I try to open GeForce Experience I get the message "Something went wrong. Try restarting GeForce Experience" or something like that. Am I the only one?
-
Spartan@HIDevolution Company Representative
Vasudev likes this. -
Wireshark or Fiddler for debugging.
Adguard custom filtering rules:
://*xxxxxxx.com^$important,app=xxx.exe
@@||*$app=xxx.exe
or
xxx.xxx.xxx.xxx^$network,app=xxx.exe,important
@@||*$app=xxx.exe
or
Advanced FW...ESET etc.
e.g. PS (don't copy this) blocking proper Domains/IPs without breaking other functions.
crlog-crcn.adobe.com > 192.147.130.166
Adguard's plethora of features besides the obvious ones.
*.xxxxxx.com/*
or Firewall -> Deny -> Remote -> IPAttached Files:
Last edited: Feb 5, 2019 -
-
-
So what does doing this accomplish over just doing regular updating?
-
I've also been updating nvidia drivers by simply installing them over the existing ones, sometimes going the extra mile and checking the "clean install" option but not every time. Zero problems so far. All the games still run just fine.
Got a new machine now and I'm trying to find out if there's any actual benefit in running DDU everytime, doing a real clean install of new drivers. -
Thanks for the guide!
-
Incredibly helpful.
Moderators should make this a sticky so newcomers can see this
How to properly update your nVIDIA graphics card driver
Discussion in 'Gaming (Software and Graphics Cards)' started by Spartan@HIDevolution, Sep 21, 2017.