Something really odd about Win10 WU driver updates

[mikeymikec]

I'm in the middle of a Win7 to Win10 upgrade for a customer, just installed Win10. During the last stages of setup the resolution was still super low so logically it was on the basic driver. Soon after it logged in, the resolution went up, and sure enough Device Manager then listed an Intel HD Graphics driver, dated 2016. Admittedly I didn't get to verify the before-and-after in Device Manager, but what happened next was interesting. I noticed the standard Realtek gigabit LAN driver it had auto-installed and figured that the one that comes with the 1607 installer is probably older and that a newer one was available via WU, so I told it to auto-search for updates and sure enough it found one. Out of curiosity, I did the same thing for the Intel graphics driver, and that picked up a new driver as well.

- edit - I just checked the events list and it was definitely on the basic driver before it updated via WU the first time.

I wonder what the logic is for not getting the most up-to-date driver from WU the first time it tried.

PS: I use the 1607 installer partly because that's what I have on USB and partly because I figure that a bit of system exercise and observing it do a feature update itself is a valid part of the testing process.

 

[crashtech]

Seems that it would make sense to use a working driver contained in the install to begin, that way there's something to fall back on if something goes wrong with the driver update. It's also faster, especially if the Internet connection is not so good.