Windows 10 still forcing driver updates even though I opted out.

Enhanced Interrogator

[H]ard|Gawd
Joined
Mar 23, 2013
Messages
1,428
Is this happening for anybody else that's done the opt-out via the System sub-menus?

I had AMD Catalyst 15.4 installed, because 15.7 introduced a bug for one of my games, but Windows still updated the driver to 15.7 yesterday. I guess maybe it wasn't correctly identified as a driver by somebody at Microsoft? Anyway, it's pretty damn annoying, I'm going to uninstall the driver and hope they don't try force it through again.
 
After I opted out I had to restart a couple times and it then tried to revert the driver back to the one that came bundled with windows, once I uninstalled that one it stopped.

So technically it did stop downloading new drivers via windows update right when I opted out, it just had another base driver up its sleeve and said hey you're missing a driver, here have this super old one!
 
Windows Update does not appear to respect that setting even though it still exists. You can use the "troubleshooter" that Microsoft released to hide driver updates so they don't install. It's a standalone executable, so you will need to keep it saved somewhere like your desktop and run it every time you need to hide an update, including when a new driver is made available.
http://download.microsoft.com/download/F/2/2/F22D5FDB-59CD-4275-8C95-1BE17BF70B21/wushowhide.diagcab

If your computer is connected to your network over WiFi you can trick Windows into not downloading driver updates by setting your internet connection to metered.
http://www.tenforums.com/tutorials/3162-wireless-network-metered-connection-set-windows-10-a.html

If you're on a Pro, Enterprise, or Education version of Windows 10, you can use the Group Policy Editor to access and change the Windows Update settings with the same options previously available in other versions of Windows.
http://www.tenforums.com/tutorials/...atic-updates-enable-disable-windows-10-a.html

Wanted to add as an extension to the thread above, a user posted a way to get similar behavior to the old Windows Update. But this only works if you have GPE.
http://www.tenforums.com/windows-up...till-no-option-install-single.html#post346134
http://www.tenforums.com/tutorials/...nable-disable-windows-10-a-15.html#post348979
 
Last edited:
Windows Update does not appear to respect that setting even though it still exists. You can use the "troubleshooter" that Microsoft released to hide driver updates so they don't install. It's a standalone executable, so you will need to keep it saved somewhere like your desktop and run it every time you need to hide an update, including when a new driver is made available.
http://download.microsoft.com/download/F/2/2/F22D5FDB-59CD-4275-8C95-1BE17BF70B21/wushowhide.diagcab

Yeah, I have this, but the crappy thing is that you have to use it before the update downloads, otherwise it will still install.
 
Its respecting that setting on my Pro install, it hasnt tried to update / download any drivers after a few restarts once I made the change.
 
I had AMD Catalyst 15.4 installed, because 15.7 introduced a bug for one of my games, but Windows still updated the driver to 15.7 yesterday. I guess maybe it wasn't correctly identified as a driver by somebody at Microsoft? Anyway, it's pretty damn annoying, I'm going to uninstall the driver and hope they don't try force it through again.


Where did you download the Catalyst 15.4 drivers from? Those are from before Windows 10 was released. Are they Windows 10 beta drivers, or are they Windows 8.1 drivers? Windows 10 drivers for hardware that supports DX12 are WDDM 2.0, whereas Windows 8.1 drivers are WDDM 1.3 (and won't work with DirectX 12 even if you get them to install on Windows 10). It does make sense that the OS would try to update a semi-incompatible WDDM 1.3 driver when it has a compatible WDDM 2.0 driver available. This isn't really directly comparable to if you were simply trying to install an older WDDM 2.0 driver, but I do agree that it should be less aggressive in that regard.
 
Yeah, they're for 8.1. Seems to me like someone just didn't label this as a "driver" and it got lumped in with the regular updates, instead of Windows just figuring out that my drivers were for a different OS.
 
Ok, this is bullshit, am I going to have to uninstall these every couple of days?
uKAVEx4.png
 
Back
Top