If you are trying to decide what Products to include in your WSUS settings, this is the article for you.  SCOM and WSUS currently have a dozen Windows 10 “products” listed but the descriptions are useless.  After several hours of reading and asking Microsoft Partner Support about the various settings, this is what I have deduced:wsus-windows-10-products-explained

  1. Windows 10 and Later Drivers: 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.
  2. 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.
  3. 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”
  4. Windows 10 Anniversary Update Server 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”
  5. 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 10 (i.e. 1511 to 1607).wsus-windows-10-features-on-demand
  6. 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
  7. 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).
  9. 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.
  10. 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.
  11. 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.
  12. 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.

In addition to the assistance of “Sherry” from MS Partner Support on this thread, I also found the following articles useful and you might too:

General vs Limited vs Quick Fix Patch Releases

Differences between GDR, LDR and QFE

SOLVED: Cannot Install .NET 3.5 On Windows 10 Error 0x800F0906 and 0x800F081F

Dynamic Update Communication Explained

Windows 10 LTSB

What is Missing from the Long Term Servicing Branch (LTSB) Version of Windows 10

Language Interface Packs vs Language Packs


Diego · March 14, 2023 at 9:53 am

This is very good!!

art · September 19, 2019 at 7:31 pm

H, my win10 pc’s are have no windows security update.

HITMAN · July 12, 2019 at 9:11 am

Thank you

Mike · April 24, 2019 at 6:42 am

The irritating thing about this is that there is not a single explanation to clear up the confusion generated directly from Microsoft! Thanks to this article I understood a lot, but still, this is something Microsoft has to say, not a vendor or a blog or a third-party site. With all the due respect of course to the post author, but this makes my blood boil!

Jazz · September 5, 2017 at 3:51 am

Thanks for helping out.

Manuel · May 16, 2017 at 9:31 am

My Man!

Vandrey Trindade · January 31, 2017 at 5:21 am


SOLVED: Cannot Install .NET 3.5 On Windows 8.1 Error 0x800F0906 and 0x800F081F - Up & Running Technologies Calgary · May 24, 2017 at 4:48 pm

[…] UPDATE: Dec 2016 – While the process below works very well, you can eliminate future .NET install problems by installing FEATURES ON DEMAND on your companies WSUS server. […]

Windows 10 V1703: Updates KB4020001 and KB4020002 | Born's Tech and Windows World · April 27, 2017 at 12:25 am

[…] Privacy: Dynamic Update and Resulting Internet Communication What do the Windows 10 Product names mean in WSUS Clarifications of Windows 10 Updates through […]

Leave a Reply

Avatar placeholder

Your email address will not be published. Required fields are marked *