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

Hi Brink, I should add a general caution for all others. Insider Review would not help this particular indiscriminate forced download of drivers. When the display is knocked blank, users cannot not "see" any subsequent updates, whether it be security fixes or Insider review build updates. And repeating the update process will not stop the driver downloads. The only way to get around this catch-22 is to re-install from DVD or USB Win10 media of a fixed public release (i.e., August anniversary update). I think I am correct on the syllogistic reasoning. If this is correct, you may want to publish an authoritative how-to.

Thanks for providing some hope.

 

Your blank display issue is not related to the tutorial.

You are still getting driver updates since you do not have build 14328 installed, or have the Windows 10 Anniversary Update on Aug 2nd. This is in the information at the top of the tutorial.

If this is not what you meant, then please clarify. *Smile

 

Insiders need to rely on automatic download in order to get build 14328 (or later). But, their prior builds will force driver download/install. It's not a show-stopper, if an insider can "see" and roll back the unwanted driver (or experience crashed system). As far as I know, Insider Review program does not provide intermediate iso for installation from DVD or USB.

People get Windows 10 Anniversary Update via (1) automatic update, or (2) installation from iso media. The first method would fall into the catch-22 category as the drivers are the first ones got installed before others. I repeated my tests at lest 3 time to confirm this sequence.

As to "This is in the information at the top of the tutorial.", I disagree for the reason above. Unless Microsoft manages driver updates download/installation separately for the Anniversary Update (or future Insider reviews), the automatic update will not work. This kind of catch-22 scenario will reoccur in other sequence-sensitive updates. Microsoft needs to handle it either in Window10, and/or in the update server side. Hope this clarifies.

 

Yes, until you have the supported build installed and use the policy, you will continue to have drivers included and installed in Windows Update.

 

We are in agreement that people must wait for Windows 10 Anniversary Update, and install the updated Win10 from the new iso media in order to select & block unwanted driver updates. And the current Win10 update (public version or insider versions) will not work for drivers in catch-22 scenarios. From the hindsight, Microsoft had disappointed/angered many customers in this free Win10 upgrade campaign. My G210M driver issue is not an isolated incidence. Many peripheral devices share the same issue.

Perhaps you can update this point.

 

Sorry if I'm being dense, but I'm not sure that it needs to be included in the tutorial since the tutorial is only to applied after you have already installed the supported build.

 

Ultimately it is your decision. What I've pointed out is that people cannot get to the supported build, if/when a disruptive device driver is in the same update download with the supported build. That device driver will be installed first, thus preventing the installation of the supported build. If people already got the supported build before whatever a disruptive device driver, the tutorial will work. Users need to logistically think through their own catch-22 scenario. The definition of a "disruptive device driver" is that its update will stop a PC from working (such as blind screen, or crash, or stop the application which deems mission-critical). As explained, this catch-22 scenario also applies to the on-line update for the upcoming Anniversary Update, but people can use the iso media to get around.

Again, it is your decision and thanks very much for your great post.

 

Here I had already been planning a clean install for the Redstone 1 Anniversary build coming August 2nd especially if it doesn't work out after first arriving as the WU update. First seeing if it will only require the reinstall of the drivers and possibly app for an older tuner card as well as sound card and run as well as some of the latest Insider builds.

Fortunately for some time I haven't been running into any problems since 2015 as the WU putting the wrong driver set on as it was at first last summer and fall where blocking those for a manual search was required. Since February when a 10 update became available but only by way of the software's own web updater the initial problems have disappeared except the fresh install of the software side for each newer build or update.

The recommendation for anyone now starting to run into any driver issues would be to at least follow the guide here as far as temporarily disabling the Windows Update functions until seeing a manual search at the needed supported sites for insuring the correct driver sets. That will avoid continual hangups with updates. Once the correct drivers go on the WU would then only go for the regular MS updates. This is how things should go once the correct drivers are on and things are working normally.

 

I'm not sure if the following information serves a purpose in this thread; however, there is a way to selectively stop Windows update from downloading specific drivers. This would be beneficial if you know a certain driver is causing issues and you don't want an "all or nothing" option. See here: https://support.microsoft.com/en-us/kb/3073930

Example of how it works:

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





Again, I apologize if this post has no meaning in this thread. Please remove if it is not applicable.

 

You brought up an interesting point. Suppose a newer automatic updated version caused problem, and a user removed it and manually reinstalled the correct (older) version. (1) Will WU repeat the automatic update of the offending driver because it is newer? (2) "temporarily disabling" registry KEY is for "all" driver updates. Therefore, if (1) will repeat the process, this new temporarily disabling method will become permanent, thus defeating its intended purpose. This is the scenario of one bad apple spoil the whole bunch. Wonder if there is any discussion on this among the expert Inside Reviewers?

 

Hi https://www.tenforums.com/tutorials/8...dows-10-a.html." only works when a system survives a disruptive driver update. I just questioned whether this new KEY is still an "all or nothing" option. I kept referring to Registry key, because Windows Home does not have the GPEDIT.msc capability for dealing with specific drivers. Great majority of Windows 10 users are in the Home edition category. That's why I spent so much time verifying and testing it.

 

Windows 10 Home users will be able to use OPTION TWO in the tutorial on the first page here, but only if they have at least build 14328 installed. Luckily this will also work in the Windows 10 Anniversary Update on Aug. 2nd.

 

Generally the trend seen for each newer version over the years coming up from Legacy days was to see 3rd party updates arrive by WU as optional at first with XP while 10 you now simply have the check box when first upgrading or performing a clean install which stops all updates until Windows is up and running. The idea of first researching for correct driver sets at this time being a year after launch is about when OEM manufacturers will finally be putting out drivers for the newest version of Windows.

The success 7 saw was largely due to not only the close 7/Vista compatibility as the 10/8.1 reflects but also saw MS pressing OEMs to have 7 drivers ready in time for 7! not just the usual "use Vista drivers until...." such time 7 drivers were finally out. With 10 on the other the WU grabs the first drivers it comes across and slaps those on which is often older not the latest drivers when finding the listing in MS data base for OEM support pointing up until earlier this year at 8, 8.1 drivers.

Actually for the older Creative X-Fi series XtremeAudio card here the 10 WU had downloaded 7 x64 drivers! It did find the correct driver for the long time discontinued tuner card there while the old Vista app was now doa being for the PCI form of the card while the PCIe or PCI Express model being newer saw 8.1 support. That app and driver proved to be for the exact chip on PCIe instead of PCI card long dead. The Creative web updater tool however is what tool the Support 1.2 package and then downloaded the Support 1.5(February release only by web tool however) which is correct for 10. But that isn't available as a separate download.

That is a good example of the need for improvision and not simply assume you can't get the correct, working updates to go on. As for problems with any just out driver version stepping from a possible 10 update to the next closest 8.1 update after disabling the WU might seem harsh while manually screening updates not simply running everything auto would be the option to re-enabled the WU once the correct driver(s) are on.

 

Thanks for that info!

 

I think Microsoft should consider this general philosophy for treating auto updates. (but maybe difficult to implement). From Microsoft's perspective, Auto Update function "should be" in line with "Windows-as-a-service" - beyond merely protecting the integrity of a functioning Windows 10. In enterprise environment, IT support can use Group Policy to manage what device drivers gets deployed. But in the consumer environment, the scope and depth of drivers must cover the legacy left behind by Microsoft's own versions of Windows and technology innovation which made Windows useful.

So, we are really talking about "freezing" a device driver "as-a-service" in Windows 10. To demonstrate this "freezing a device driver", I installed VMware Player and created a WinXP virtual machine to run my very old Canon scanner which has a rare feature for scanning 35 mm slides. I took a lot of slides over the last 40 years all over the world, and some are probably historical. I am sure there are other devices or apps in this category. The VM works flawlessly and intuitively. However, Microsoft Hyper-V needs Windows 10 Professional and dropped WinXP support. What if Auto Update can take on this vision? And what should Microsoft do?