December 2016 CU for SharePoint Server 2016 is available for download

15 Comments

1. 

   James DeLisa
   On 14. December 2016 Permalink

   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.

   Reply
   1. 

      Stefan Goßner
      On 15. December 2016 Permalink

      Thats correct.

      Reply
2. 

   speedydaniel84
   On 15. December 2016 Permalink

   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.

   Reply
   1. 

      Stefan Goßner
      On 15. December 2016 Permalink

      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.
      Cheers,
      Stefan

      Reply
      1. 

         speedydaniel84
         On 16. December 2016 Permalink

         Thank you very much. This info is very helpful

         Reply
      2. 

         SP_Admin
         On 20. December 2016 Permalink

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

         Reply
         1. 

            Stefan Goßner
            On 20. December 2016 Permalink

            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.
            Cheers,
            Stefan

            Reply
3. 

   Harry Keith
   On 28. December 2016 Permalink

   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!

   Reply
   1. 

      Stefan Goßner
      On 28. December 2016 Permalink

      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.
      Cheers,
      Stefan

      Reply
      1. 

         Elton Oliveira
         On 29. December 2016 Permalink

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

         Reply
         1. 

            Stefan Goßner
            On 29. December 2016 Permalink

            Correct. 🙂

            Reply
4. 

   MP
   On 9. January 2017 Permalink

   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 ?
   Thanks
   MP

   Reply
   1. 

      Stefan Goßner
      On 10. January 2017 Permalink

      Hi MP,
      you can find the explanation in the article I released today:
      https://blogs.technet.microsoft.com/stefan_gossner/2017/01/10/sharepoint-server-2016-patching-using-side-by-side-functionality-explained/
      Cheers,
      Stefan

      Reply
5. 

   Sven
   On 29. March 2017 Permalink

   Is it true that the missing feature in the MySite onet.xml (SPSPers) is still unfixed?
   Reference: https://thesharepointfarm.com/2016/03/unable-to-provision-social-features-in-sharepoint-server-2016/

   Reply
   1. 

      Stefan Goßner
      On 29. March 2017 Permalink

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

      Reply