No, this isn’t confusing at all — makes perfect sense.

First, the explanations (at least to a certain point as the article was written in December 2016 but can be extrapolated to current date) can be found at the link below:

Second, If you’ve been following the Windows 10 product since inception, or google Windows 10 Names and then visit the Wikipedia article here (https://en.wikipedia.org/wiki/Windows_10_version_history) then you will know that:

I will however agree with the Duplicate Creators Update and Later Servicing Drivers — that was/is an anomaly.

As for Lang packs, the urtech link contains a great link to the explanations of LPs vs LIPs — https://msdn.microsoft.com/en-us/goglobal/bb688177.aspx

Is it complicated? — NO; is it confusing? — At first maybe. It’s a thought process switch; different from the old methods. Once you learn the thought process switch, it becomes super easy; kind of like that Office Toolbar switch back in Office 2003>2007. Can or would you go back to the old way? 99.9999% of the people I interact with would say no way (there’s always the 1 who can’t or won’t change)

Change how you think; change your life!

Adam Marshall, MCSE: Security
http://www.adamj.org
Microsoft MVP — Windows and Devices for IT

Someone who is only deploying Win10 Anniversary in there network would want only the Win10 Anniversary updates but not creators edition updates (yet).

The easier way to think of this is Microsoft has said that ‘Windows 10″ is going to be the last version of Windows ever. From a marketing perspective, they are correct. From a technical perspective, all they have done is renamed «Microsoft Windows» to «Microsoft Windows 10»

Think of each update as a new ‘Windows XP’ or ‘Windows 7″. There are many updates that apply to specific versions, and then there are generic updates that apply to all versions.

Adam Marshall, MCSE: Security
http://www.adamj.org
Microsoft MVP — Windows and Devices for IT

You’re kidding, right? There are 25 Windows 10 products listed in WSUS and absolutely no details provided for any of them. Your smug attitude couldn’t be more misplaced.

That link you provided is completely useless. Please, fountain of all knowledge, explain to me which boxes I need to tick to keep my W10 Pro machines updated and have the bi-annually update releases available through WSUS.

Your comments trying to connect this nonsense to the Office ribbon are ludicrous as is your stupid «change how you think: change your life» troll statement.

Oh boy. you’re getting warmer now!

So let’s try putting just a *tiny* bit more effort into this, shall we?

Explain Windows 10 Dynamic Update vs Windows 10 GDR-DU vs Windows 10

Also, your smug (shitty) attitude would be somewhat tolerable if any of this information showed in the detail box in WSUS when someone’s trying to figure this out.

I feel your pain, mizzle! What I ended up doing was selecting all of the Windows 10 updates except for the following:

Feature on demand; all Language Packs (2), and all Windows 10 S (5 total).

We are not using Language Packs. We only have Windows 10 Pro, not ‘S’. And I have no idea what ‘Feature on demand’ is, but I don’t think we are using that either.

Of course, we have enough resources on our WSUS server to handle these updates — 12GB RAM and 300GB HDD space. If your WSUS server does not have enough resources, then you may need to dig a little deeper and find out which Windows 10 items you can remove. Sorry if this is not much help, but after finding out I could just add most of the Windows 10 options, I did it and just moved on! Good luck and post back if you find out any other information.

That link you provided is completely useless. Please, fountain of all knowledge, explain to me which boxes I need to tick to keep my W10 Pro machines updated and have the bi-annually update releases available through WSUS.

Your comments trying to connect this nonsense to the Office ribbon are ludicrous as is your stupid «change how you think: change your life» troll statement.

«You can’t please everyone.»

I’m not pleasing you. I volunteer my time. I’m not a fountain of all knowledge. You very well may be smarter than me, but not as polite.

Oh boy. you’re getting warmer now!

So let’s try putting just a *tiny* bit more effort into this, shall we?

Explain Windows 10 Dynamic Update vs Windows 10 GDR-DU vs Windows 10

Also, your smug (shitty) attitude would be somewhat tolerable if any of this information showed in the detail box in WSUS when someone’s trying to figure this out.

I will answer this for the benefit of others. not necessarily you.

This is MY interpretation of it.

Windows 10 Dynamic Update — «This includes only updates to the setup process that occurs when one build of Windows 10 is trying to update to a new build of Windows» (from Urtech) — My take: Servicing updates for Windows 10 for upgrading from one build to the next. MS finds an issue with a specific model of Dell or HP, fixes it and releases the new patch as a serving update that, when applied, allows for that specific issue that prevented the upgrade to be fixed allowing the upgrade to happen. These serving updates may span 1607>1803, 1511>1803, 1703>1803, etc.

Windows 10 GDR-DU — «Windows 10 GDR-DU: GDR = General Distribution Release, DU=Dynamic Update. These updates are only used by the current GDR build of Windows 10 when it is trying to perform a Dynamic Update (see item 5 above).» (Urtech) — My take: same as above, but ONLY for the GDR (ie 1709>1803)

Windows 10 — «Windows 10: These are the standard release patches that are may apply to any or all builds of Windows 10. Each one of these updates will have a KBase article for them.» (Urtech) — My take: These are where most of the updates come from — security, etc. All builds of Windows 10 get Edge updates. These in my opinion would be included in this set, as would the malicious software removal tool.

Adam Marshall, MCSE: Security
https://www.ajtek.ca
Microsoft MVP — Windows and Devices for IT

I feel your pain, mizzle! What I ended up doing was selecting all of the Windows 10 updates except for the following:

Feature on demand; all Language Packs (2), and all Windows 10 S (5 total).

We are not using Language Packs. We only have Windows 10 Pro, not ‘S’. And I have no idea what ‘Feature on demand’ is, but I don’t think we are using that either.

Of course, we have enough resources on our WSUS server to handle these updates — 12GB RAM and 300GB HDD space. If your WSUS server does not have enough resources, then you may need to dig a little deeper and find out which Windows 10 items you can remove. Sorry if this is not much help, but after finding out I could just add most of the Windows 10 options, I did it and just moved on! Good luck and post back if you find out any other information.

With WSUS Automated Maintenance, You don’t need much. Mine is using 8GB RAM (was 4, but I use that server for PDQ Deploy too, so that is why I increased it to 8GB) and my HDD usage with all products of Windows 10, Windows 7, Exchange 2013, Office 2013, Server 2012, Server 2012R2, and a bunch of other products, along with ALL classifications selected including drivers. my content folder is less than 100GB.

Adam Marshall, MCSE: Security
https://www.ajtek.ca
Microsoft MVP — Windows and Devices for IT

LOL, I am using PDQ Deploy on our WSUS also! Not sure what «Automated Maintenance» is but I go in about every month and run the server cleanup wizard. Our content hovers around 270GB.

Adam Marshall, MCSE: Security
https://www.ajtek.ca
Microsoft MVP — Windows and Devices for IT

Also see part 8 of my blog series

Adam Marshall, MCSE: Security
https://www.ajtek.ca
Microsoft MVP — Windows and Devices for IT

I found the same thing and totally agree. Their capitalizations and commas aren’t consistent as well as that duplicate line entry. I think we’re the only two in the world that noticed that. haha

It’s like this project was completely as minimally as possible and swept under the run. I need ALL these fields answered. I got a few from other blogs, but man is it lacking in the 2 categories I really need!

Need to know precisely what each and everyone of these «Products» Windows and Office subcategory fields do @ (WSUS —> Update Services —> Options —> Products and Classification —> Products —> Windows and Office). I’m unable to find any documentation specifically for these fields from Windows including WSUS PDFs such as 1) Ops Guide, 2) Deploy Guide or 3) Release Notes, which is kinda sad. :-/

OFFICE
—
Dictionary updates for Microsoft IMEs

New Dictionaries for Microsoft IMEs

Office 365 Client

WINDOWS
—
OOBE ZDP
Designed to allow “must have” updates to be installed during OOBE, before the user reaches the Start Screen. These updates are meant to fix security holes and functional issues that block core experiences in Blue as early as possible. IDP driver and firmware updates can also be delivered through this mechanism. This update mechanism should *not* be confused with the GDR-DU process (store upgrade). OOBE ZDP update should not require more than one reboot. The combined size of all available OOBE ZDP updates should be less than 5MB. The combined install time of all OOBE ZDP should be less than 4 minutes.

Windows 10 and Later Driver
These are drivers that will be offered to all builds of Windows 10 all the time, excluding upgrade scenarios (i.e., via Orchestrator, DSM, or Device Manager). They will not download during a Dynamic Update (i.e. Windows 10 upgrading itself from build 1511 to 1607). They should only include KBs for the current Win10 version.

Windows 10 and Later Upgrade & Servicing Drivers
These are drivers that are offered in all Win10 scenarios (i.e., via Orchestrator, DSM, Device Manager, or during DU). They may include some KBs later win10 version and enable current win10 version to upgrade.

Windows 10 Anniversary Update and Later Servicing Drivers
These drivers apply only to Windows 10 1607 Anniversary and will not contain later upgrade. It also includes servicing drivers as “Windows 10 and later upgrade & Servicing drivers”

Windows 10 Anniversary Update and Later Servicing Drivers
These drivers apply only to what is now named Windows Server 2016 and will not contain later upgrade. It also includes servicing drivers as “Windows 10 and later upgrade & Servicing drivers”

Windows 10 Creators Update and Later Servicing Drivers

Windows 10 Creators Update and Later Upgrade & Servicing Drivers

10 Dynamic Update: This includes only updates to the setup process that occurs when one build of Windows 10 is trying to update to a new build of Windows 10 (i.e. 1511 to 1607).wsus-windows-10-features-on-demand

Windows 10 Fall Creators Update and Later Servicing Drivers

Windows 10 Fall Creators Update and Later Upgrade & Servicing Drivers

Windows 10 Features On Demand: This loads the items listed on any Windows 10 PC’s PROGRAMS AND FEATURES > TURN WINDOWS FEATURES ON AND OFF into the WSUS server. That would mean that when a .NET 3.5 install is required on a Windows 10 PC, it will pull the files from the WSUS server rather than making you install it via command line using a Windows 10 DVD to solve errors 0x800F0906 and 0x800F081F

Windows 10 GDR-DU FOD

Windows 10 GDR-DU LP: GDR = General Distribution Release, DU=Dynamic Update, LP = Language Packs. These updates are to Languages used by the current release version of Windows 10 (in December 2016 that is build 1607) during a Dynamic Update (see item 5 above).

8.Windows 10 GDR-DU: GDR = General Distribution Release, DU=Dynamic Update. These updates are only used by the current GDR build of Windows 10 when it is trying to perform a Dynamic Update (see item 5 above).

Windows 10 Language Interface Packs: Windows Language Interface Pack (LIP) is a high-quality, localized “skin” for emerging or minority language markets. LIP provides the desktop user with an approximately 80% localized user experience by translating a reduced set of user interface (UI) elements. LIP has a dependency on a base Language Pack of Windows. Languages are offered as a LIP or a LP depend on the level of investment Microsoft has in a specific country/region. It is possible for a LIP market to grow into a LP market between the current and future Windows rollout. See THIS article for more details on LIP and LP’s.

Windows 10 Language Packs: Language Packs contain full blown languages. Remember that at it’s core Windows 10 is language agnostic. It comes with no default language and one has to be loaded for it to function.

Windows 10 LTSB: LTSB = Long Term Servicing Branch. Updates in this category are for a special long life version of Windows 10 that is promised to exist for 10 years with minimal updates. See THIS for more details on Windows 10 LTSB.

Windows 10 S and Later Servicing Drivers

Windows 10 S Version 1709 and Later Servicing Drivers for testing

Windows 10 S Version 1709 and Later Upgrade & Servicing Drivers for testing

Windows 10 S Version 1803 and Later Servicing Drivers

Windows 10 S Version 1803 and Later Upgrade & Servicing Drivers

Windows 10 S, version 1809 and Later, Servicing Drivers

Windows 10 S, version 1809 and Later, Upgrade & Servicing Drivers

Windows 10 Version 1803 and Later Servicing Drivers

Windows 10 Version 1803 and Later Upgrade & Servicing Drivers

Windows 10, version 1809 and Later, Servicing Drivers

Windows 10, version 1809 and Later, Upgrade & Servicing Drivers

Windows 10: These are the standard release patches that are may apply to any or all builds of Windows 10. Each one of these updates will have a KBase article for them.

Windows 8 Dynamic Update

Windows 8 Embedded

Windows 8 Language Interface Packs

Windows 8.1 and later drivers

Windows 8.1 Drivers

Windows 8.1 Dynamic Update

Windows 8.1 Language Interface Packs

Windows 8.1 Language Packs

Windows Dictionary Update

Windows Embedded Standard 7

Windows GDR-Dynamic Update

Windows Internet Explorer 7 Dynamic Installer

Windows Internet Explorer 8 Dynamic Installer

Windows Media Dynamic Installer

Windows Next Graphics Driver Dynamic update

Windows RT 8.1 and later drivers

Windows RT 8.1 Drivers

Windows RT Drivers

Windows Safe OS Dynamic Update

Windows Server 2003, Datacenter Edition

Windows Server 2003

Windows Server 2008 R2

Windows Server 2008 Server Manager Dynamic Installer

Windows Server 2008

Windows Server 2012 Language Packs

Windows Server 2012 R2 and later drivers

Windows Server 2012 R2 Drivers

Windows Server 2012 R2 Language Packs

Windows Server 2012 R2

Windows Server 2016 and Later Servicing Drivers

Windows Server 2016

Windows Server 2019

Windows Server Drivers

Windows Server Manager — Windows Server Update Services (WSUS) DYnamic Installer

Windows Server Technical Preview Language Packs

Windows Server Technical Preview Language Packs

Windows Ultimate Extras

Windows Vista Dynamic Installer

Windows Vista Ultimate Language Packs

Windows XP 64-Bit Edition Version 2003