System Requirements:
The Problem:
Microsoft’s descent into Apple design and general irrelevancy continues unabated with design time decisions for Windows 10. Obviously when drivers get released onto Windows Update, they’re going to work for everyone. Obviously.
In my experience the main issue is with integrated chips from the large PC OEM’s (Dell, HP etc). The subtle modifications that they make in their own proprietary releases of their “2010” driver when do not necessarily directly map onto the generalised driver with the same PnP ID’s being detected from Windows Update.
In the last week I’ve had to deal with this no less than 8 time on 6 separate occasions. I, like most people in IT, have encountered this many times before however it has usually been with fairly large driver updates that require a reboot – prolific Windows 10 dual screen problems with Windows Update Intel HD Graphics drivers anyone?
So unlike previous Windows versions, there is no longer a way to stop Windows Update automatically installing updates immediately using the UI, you have to resort to group policy to have any chance of delaying it. In Windows 10 there is also no way to block certain updates if you do not want them / they don’t work.
Of course Microsoft’s business decision behind this end user horror is quite simple: Too many people blocked or are blocking KB3035583 (the Windows 10 installer update for Windows 7 and 8.x) preventing them from force feeding you Windows 10. They also want to de-fragment their ecosystem (I can empathise with this) and consequently they want to ensure that people are being spoon fed the latest feature updates as soon as possible under the new Windows feature release cycle.
Of course, if you get a bad update or a bad driver, now that there is no way to block it, you will uninstall it and it will simply come back.
The problem is exacerbated with small driver downloads (in the kilobytes range) that do not require reboots. In my most recent cases a 2009 HP Laptop Webcam. a 2010 HP Laptop Fingerprint reader and a 2008 Toshiba laptop touch screen driver. By the time that you have uninstalled the bad driver, rolled back to ‘no driver’/a working driver, run Windows Update to make Windows aware that there is a bad one available and then in turn run the Window Update Show/Hide Tool. Windows has already reinstalled the bad driver and as a consequence the WU Show/Hide tool is unable to give you the option to block the driver.
Bravo Microsoft. Bravo!
More Info
As eluded to above, the issue is one of timing. Windows 10’s brutal and where possible immediate desire to install anything that comes down the update channel is breaking the sequence necessary to correctly use the WU Show/Hide tool.
The required sequence is:
- Uninstall defective device, deleting the old driver
- Run Windows Update so that the local Windows Update Available Updates Catalogue shows an available driver update for that device
- <Windows Update should NOT do anything at this point>
- Run the Windows Update Show/Hide Tool
- Block the bad driver update
- Re-scan Windows Update to clear the update from the Available Updates Catalogue
- Install updates manually / after a sensible delay
In practice, at step 3 Windows Update – now aware that there is a driver waiting – is simply installing the bad driver again. This prevents you from running the WU Blocker tool. The problem is exacerbated by small updates (or fast Internet connections) because there isn’t a delay between Windows realising that there is an update and taking the time to download it before executing the Install.
This delay is useful for things like the Intel HD Graphics problem because the driver files is over 120MB and in many cases this gives you enough time to run the WU Blocker tool successfully.
The Fix
Yes, you can mess around with Group Policy to fix this – unless of course you are on a home edition. Yes, you can also modify the driver installation policy, however again this isn’t always desirable. So I present a simple way to solve this.
- Download the Windows Update Show/Hide (blocker) tool from KB3073930
- Open Windows Explorer at C:\Windows\SoftwareDistribution\Download
- Open en elevated command prompt and type:
net stop wuauserv
- Return to C:\Windows\SoftwareDistribution\Download and delete everything in the folder (but not the folder itself) – this deletes the installer cache for the driver
- Right click on the C:\Windows\SoftwareDistribution\Download folder itself, choose properties
- Open the security tab
- Click Edit to change permissions
- Select the SYSTEM account from the accounts list
- In the Deny column next to the permission for “Write” place a tick – JUST place a tick next to Write, that is all that is needed!
- Click OK twice to return to Windows Explorer – accepting any messages and warnings about Deny actions and system folders
- Go to device manager, uninstall the defective device – ensuring that you select the option to delete the driver along with it
- Run Windows Update
- Windows Update will now attempt to install the device, however it will fail with error code 0x80246007
- Now run the Windows Update Show/Hide Tool, block the update
- Return to Windows Update and re-scan for the update to flush it out of the available update list
- Go back to setup 5 and REMOVE the Deny Write permission tick to undo your changes
- Return to Windows Update and re-scan for updates. Windows Update should inform you that your device is up to date and will not attempt to install the driver
View: Windows Update Show/Hide Tool
