New
#40
Another option to tend with problematic driver updates as mentioned earlier would be a quick trip to the manufacturer(s)'s support site(s) to look things up. If the WU downloads and installs the wrong driver the next stop is the Device Manager to manually remove the incorrect with a fast right click on the item(s) there and then followup by running the correct update(s)'s installer(s).
It's not as complicated as some may think. The guide here shows how to temporarily disable the Group policy or registry entry that more or less controls the WU actions as far as automatically looking things up and getting it wrong at times. The "gpedit.msc" as well as reg mod combined will simply insure nothing wanted goes on over the long term when both options are deployed.
The most common type of mix up as far as the 10 installer going for the wrong driver set would be for those older hardwares that won't be seeing any active 10 support while might be seeing a 3rd party type web update tool look up the correct drivers for use on 10. The discontinued sound card model here on the oldest build ran into that.