Anyone who added "Drivers" to their WSUS synchronization options may have noticed a large number of driver updates showing up in their WSUS server recently, and the majority of them have the same title. We wanted to let you know what's going on and what we are doing about it.
First lets talk about the root cause. Drivers can target one or more hardware IDs, and we have a limitation in our data-model so that each "update" can only support a single hardware ID. What that means is that a single driver is often implemented as multiple updates, all with the same title. What happened recently is a few drivers were released to WSUS that supported a very large number of hardware IDs.
It turns out the proper fix for this is not simple; it involves changes to WSUS, WUA, WU, and our driver publishing pipeline to allow a single driver update to support multiple hardware IDs. We have made a number of these changes already, but all this won't come online until some time after the next WSUS release. A number of folks have asked "can't you just do some quick change to the WSUS UI to group them together" and unfortunately that is an even more complex change to make (although in the WSUS 3 UI update view, we do have a "group by" feature that allows one to at least group the updates by title - but that's only a small part of update handling).
In the short term, we will be making some publishing policy changes to ensure that drivers with a large number of hardware IDs don't flow to WSUS through WSUS/MU server synch. This doesn't mean the drivers won't be available to WSUS - they can still be imported from the MU catalog site (from the WSUS 3 UI, go to the "Updates" node and select "import..."). It's just that they won't flow automatically and surprise those who have added drivers to their synch options.
WSUS Lead Program Manager
All you need to do is to blog ahead of time or during the nights of the 10,000 drivers that "yes, this is normal, we know" and then a lot of us (including me) will know that this is expected.
All I have asked for since WSUS first came out is one definitive listing of what is hitting my box that doesn't include the email notification "from" my box.
Communication...that's all I want.
I would prefer that, until WSUS and the other components are updated to NOT flood us, driver updates like this are not released through the normal channels unless they contain security fixes. I think this is what Marc indicates in his blog post above. Thanks.
I agree with Jay, this is a terrible experience today and should be fixed end to end before allowing us to get "spammed" by default.
Further, i would like improved user experience with WSUS for drivers so i can pivot or group by "vendor" type.
Will WU catalog also be updated????
System Center Essentials is built on top of Windows Server Updates Services (WSUS) technologies. This
I want to ask, Windows Vista and Windows Server 2008 can use the same drivers, but why can't I update the same drivers on Windows Server 2008 which can update on Windows Vista?
This must really be one heck of a problem for MS to fix, because this same thing was blogged about here more than 10 months ago (http://blogs.technet.com/wsus/archive/2007/09/07/ati-radeon-graphic-card-updates-3892.aspx). Looking forward to the fixed release of WSUS..
Why you don't publish the latest NVIDIA e ATI drivers via Windows Update? Microsoft signs these drivers so you should publish them on Windows Update
Also MS should release newer Intel WLAN Drv. by MU cause
old drivers (v10.5) will freeze XP installing SP3
Our WSUS server was already struggling and the thousands of duplicate updates has pretty much brought it to a stand still. It keeps timing out when viewing unapproved updates! Is there anykind of patch or script to decline or remove these updates from the backend?
hey the problem is driver publishing, WU generally is good for most things but drivers .. why???
Fix driver publishing or remove it from WU please!
As noted above, you've been talking about this almost a year ago: "We are changing the publishing process for the future btw so that multiple HWIDs will be associated to one update in the future. thnks - Bobbie". Well, guess what - it didn't move an inch further and now we see a nonsensical flood of Realtek drivers, more than three times bigger than the ATI one.
This whole drivers component of WSUS is plain unusable as it is, I'm strongly advising everyone to never enable this. And you know, "Also be assured that we really only have about 8MB total binary size for all these updates." - as noted at the time when the ATI smash came - absolutely doesn't help because this nonsense makes the DB size almost double and slows everything down in a horrible way.
IOW, make it usable or stop publishing crap in WSUS.
It would be nice if Microsoft would expire these 10000 Realtek audio drivers, it takes a lot of time to decline them manually! The WSUS management console times out and loose the connection when trying to decline too many updates at once!
It looks like a heap of video drivers have been dropped to WSUS today in the same way.
As you have removed your 'Contact Us' page and are rarely seen in the TechNet WSUS Forums here is a link to a post regarding the WSUS Silverlight update KB953838 that is being detected to be installed on Server Core 2008 machines.
Hello, my name is Joe Tindale and I am a Support Escalation Engineer with the WSUS team. As some of you