December 2016 CU for SharePoint Server 2016 is available for download

The product group released the December 2016 Cumulative Update for SharePoint Server 2016 product family.
This CU also includes Feature Pack 1 which was released with November 2016 CU.

The KB articles for December 2016 CU are available at the following location:

  • KB 3128014 - Update for SharePoint Server 2016 December 2016 (language independent)
  • KB 3128017 - Update for SharePoint Server 2016 December 2016 (language dependent fixes)
  • No fixes released for Office Online Server 2016

The download for December 2016 CU is available through the following link:

It is irrelevant which language you pick on the drop down in download center. Even the language dependent fixes are all in the same package for all languages.

After installing the fixes you need to run the SharePoint 2016 Products Configuration Wizard on each machine in the farm. If you prefer to run the command line version psconfig.exe ensure to have a look here for the correct options.

SharePoint 2016 December 2016 CU Build Numbers:

Language Independent fix: 16.0.4471.1000
Language Dependent fix: 16.0.4471.1000

To understand the different version numbers please have a look at my article which explains the different SharePoint build numbers.

You can use the SharePoint Server 2016 Patch Build Numbers Powershell Module to identify the patch level of all SharePoint components.

Related Links:

Comments (15)

  1. James DeLisa says:

    So at this point we can apply the December PU 2016 for SharePoint 2016 and skip the November PU 2016 update correct? I normally test in a development first than move to production on a weekend.

  2. What’s the difference between the “language independent” (smaller file size) and the “language dependent fixes” (bigger file size)?
    When I check the KB articles, the content is different.
    Which package should I download and install? Using the English RTM Installation with German language pack at the moment.

    1. Hi Daniel,
      SharePoint consists of language Independent components and language dependent components (resource files, …).
      When you install SharePoint you always install the language independent components and components for one language. You can see it like a built in language pack. On top of this you Can install additional language packs.
      The language independet fix updates the language independent files, the language dependent fix the language dependent components.
      You always have to install both.
      Why do we have to packages? Simple: if you install a language pack later you only have to apply the language dependent fixes again, not the language Independent one.

      1. Thank you very much. This info is very helpful

      2. SP_Admin says:

        If no language packs have been installed, do you still need to install the language dependent fixes?

        1. Yes. SharePoint ships with the language independent core component and one language which is similar to an integrated language pack.
          You can then install additional language packs on top.

  3. Harry Keith says:

    Hi Stefan,

    one of my SP farms runs currently on september 2014 CU. Is it possible to just install the dec 2016 CU to be up to date?

    Thanks in advance!

    1. Hi Harry,
      this is not possible. There is Sept 2014 CU for SharePoint 2016.
      If you are talking about SP2013 I would appreciate if you would post your comments into the right posts to ensure that others can benefit from the Response as well.

      1. Elton Oliveira says:

        There is *NO* Sept 2014 CU for SharePoint 2016 you mean, right?

  4. MP says:

    After applying December 2016 CU , I see 16.0.4471.1000 folder under \template\layouts. Is this by design ? what will happen to \layouts\1033?? Does this mean all our new solutions need to be deployed to this folder ?

  5. Sven says:

    Is it true that the missing feature in the MySite onet.xml (SPSPers) is still unfixed?

    1. Hi Sven,

      I’m not familiar with this issue. Did you open a support case for this to request a fix?


Skip to main content