Windows 10: Enable or Disable Driver Updates in Windows Update in Windows 10

Thank you very much. Yes it is being updated through Windows Update.

 

Chris,

You might also turn off automatic device driver installation to see if that may help.

https://www.tenforums.com/tutorials/1...dows-10-a.html

 

I believe I tried that during the first go round I had with this machine and it didn't help. I've since "refreshed" it and started again so I'll give it a try. I disabled that setting but it already had the updates downloaded and ready to be installed. I'll install them, install the old driver so it's working again and keep an eye on it. I'll get back to you all once I have something to report. Thanks for the help.

 

You might simply end up needing to replace the 383 build itself in favor of the Redstone 1 update or latest 14905 Insider build. Since you are running the now older build the WU is looking to update everything to satisfy that need. Tweaks to disable the WU are mainly geared for the RTM builds(that includes original 10240, Threshold 2 update, Redstone 1 update) over the long term while each Insider developer build looks to be totally replaced in a much shorter period of time.

 

That has been my experience. Do not include drivers with Windows Updates keeps most drivers out of WU, but it cannot be relied upon to keep all drivers out of WU. Hopefully they will fix this at some point.

 

From what I found here when first seeing 10 go on last summer was the 10 installer automatically located the correct drivers for two separate now discontinued expansion card first being an old PCI type XP driven tuner card that finally saw Vista drivers available when 7 was already in RC form before that previous version launched! The app was then borrowed from a new PCIe model that used the same chip and worked out fortunately.

The other would be expected to have far more support even at this time being the Creative PCIe sound card where the available update features it's own web updater tool. So not every driver update will become a problem. Plus you can later remove a problem driver by way of the Device Manager with a right click on the effected hardware once the correct driver set is looked up.

What MS has done is expanded on backward compatibility to an extent to where even some Vista/7 especially 64bit drivers will work in some cases on 10 in order to see 10 work on more older systems. Unfortunately the installer may tend to find the incorrect rather correct device driver on some occasions where the manual search is something you have to see taken care of.

 

I'm cautiously optimistic. No new driver updates since Friday.

 

Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB3176934) requires a restart is about one of the few loose updates you can expect following the Redstone 1 Anniversary update on the 2nd of August unless being in the Insider program. Device drivers are generally something the 10 installer finds either during an update to newer build or especially upon a clean install when all hardwares are being detected. MS is the one who is constantly pushing out frequent cumulative updates while other manufacturers tend to see periodic updates only.

 

I jumped the gun. Came in today and the machine I've been testing is using the incorrect driver again. Night Hawk, are you saying that I need to be running an Insider build instead of what MS is offering through WU? If so, that's cool just want to clarify.
Thanks

 

Insider builds are an option not a neccessity. In fact the only reason I was continuing to run them on the main desktop was the Threshold 2 from last fall suddenly went buggy on me back in February. On the other hand if you are curious about each new change coming with 10 and have multiple systems you can opt to see one or two running the developer preview type builds while keeping you own main running the Redstone 1 Anniversary update.

Now for the buggy driver problem you need to look at what that is for in particular and research the manufacturer's support site in order to look up the correct version. Once you have that downloaded and saved you can opt to defer updates to prevent that from being altered all over again by following the steps in the guide here. Sometimes that will become a necessity however and why the guide is here.

If you need help looking that up give me a pm with the specifics for the system you are having the problem with. The find here with 10 is often an 8.1 update will often work out the best.

 

When I go to Nvidia's site and search for the driver it shows the same one that I'm using. WU just keeps installing a different one. I'll try the Insider build and see how that goes. I believe that's the only option that I haven't tried so far.
Thanks again

 

Ok guys i had the same problem with amd gpu drivers. I was installing the latest 16.... and windows update was forcing installation older driver every time i was checking for updates 15.... The solution i found was this article https://support.microsoft.com/en-us/kb/3073930 from ms. In my situation worked like this, i made the driver update with the utility from the guide hidden but at windows update was present again so i left it to update the driver and after i rolled back to my driver and after this i checked again and the driver update had disappeared this time.
Sorry for bad English.

 

That simply points out what I have previously mentioned about first locating the correct update for any stubborn driver problem and going into the Device Manager to locate the hardware or item being effected and see the driver is uninstalled. Once taken care of you then manually install the correct update from the manufacturer's support site.

Allow the machine to run a few days or see a couple of full restarts before going to check for updates or when seeing them re-enabled again. That will Windows to see the correct driver(s) already being on. So far that has been working out quite well here for the few older expansion card type devices where the WU would otherwise get the drivers but not correct app to go with them.

The driver you had there for GPU would otherwise have been likely the Catalyst driver problem some have run into.

 

You need to wait for WU to refresh itself after you hide a driver with the WUShowHide tool. If it's still listed in WU, and you click "download", it will get installed whether it was hidden with the tool or not. WU will eventually refresh itself and the hidden driver will no longer be listed. The geniuses at MS provided no manual way to refresh WU/check for updates only ("check for Updates" actually means "Check for and immediately install all updates/drivers"), so you just have to wait for it to refresh itself. You can at least speed up the process by setting update checks to happen every hour in gpedit.
---------------
Just to sum up the current Windows 10 situation when it comes to preventing automatic driver installations:

The Device Installation Settings Yes/No setting is a waste of time. Setting it to No doesn't appear to do squat. In the AU, the wording of this setting has been changed to support the notion that it doesn't relate to drivers at all.

SearchOrderConfig (regedit)/Do not search Windows Update1 (gpedit) will stop instant on-connection driver installations (usually for things like USB peripherals, not GPUs), but those drivers will then end up in WU.

The new Do not include drivers with Windows Updates2 (gpedit) setting seems to stop most drivers from appearing in WU, but not all.

So the only way to make 100% sure that no drivers are automatically installed from the web is still to use gpedit Configure Automatic Updates3 to disable automatic WU updates completely, monitor the WU updates as they come in, and hide the drivers that appear there with the wushowhide tool (being careful not to accidentally install drivers that have been hidden but are still in the WU list - wait for it to reflect the drivers you hid before you try to apply the rest of the updates).

When (if) they fix the Do not include drivers with Windows Updates GP setting, that should eliminate the need for messing around with the wushowhide tool and make controlling drivers in Windows 10 that much easier.
---------------
1 Local Computer Policy/Computer Configuration/Administrative Templates/System/Device Installation/Specify search order for device driver source locations: Enabled, Do not search Windows Update

2 Local Computer Policy/Computer Configuration/Administrative Templates/Windows Components/Windows Update/Do not include drivers with Windows Update: Enabled (defective)

3 Local Computer Policy/Computer Configuration/Administrative Templates/Windows Components/Windows Update/Configure Automatic Updates: Enabled, Notify for download and notify for install.

Above mentioned GP for speeding up WU refresh:

Local Computer Policy/Computer Configuration/Administrative Templates/Windows Components/Windows Update/Automatic Update detection frequency: Enabled, 1 hour

If anyone knows of a manual way to trigger a WU refresh/check for updates without immediately installing, please let me know.

 

Besides running with Insider builds if so the latest WU should be showing if not already installed would be the "Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB3176938)." for the 64bit 10 that is.

Typically following any WU check a full system restart to clear off any loose updates like that should then show the latest check was seen at.... (specified time) with nothing else presenting itself on the next check to follow. Once you see that indicated you know you got past the other situation.