The product group released the December 2019 Cumulative Update for SharePoint Server 2016 product family.
This CU also includes Feature Pack 1 which was released with December 2016 CU and Feature Pack 2 which was released with September 2017 CU.
The KB articles for December 2019 CU are available here:
- KB 4484178 – December 2019 Update for SharePoint Server 2016 (language independent)
- KB 4484181 – December 2019 Update for SharePoint Server 2016 (language dependent)
The download for December 2019 CU is available here:
- Download December 2019 Update for SharePoint Server 2016 (language independent)
- Download December 2019 Update for SharePoint Server 2016 (language dependent)
Important: It is required to install both fixes (language dependent and independent) to fully patch a SharePoint server. This applies also to servers which do not have language packs installed. The reason is that each SharePoint installation includes a language dependent component together with a language independent component. If additional language packs are added later (only) the language dependent fix has to be applied again.
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 2019 CU Build Numbers:
Language independent fix: 16.0.4939.1000
Language dependent fix: 16.0.4939.1000
To understand the different version numbers please have a look at my article which explains the different SharePoint build numbers.
Related Links:
- Technet: Updated Product Servicing Policy for SharePoint Server 2016
- Blog: Common Question: What is the difference between a PU, a CU and a COD?
- Blog: SharePoint Patching demystified
- Blog: Why I prefer PSCONFIGUI.EXE over PSCONFIG.EXE
- Technet: Update Center for Microsoft Office, Office Servers, and Related Products
- Blog: SharePoint Server 2016 Patch Build Numbers Powershell Module
- Blog: SharePoint Server 2016 Zero-Downtime Patching Demystified
- Blog: SharePoint does not have a build version. Full Stop.
Permalink
I maybe early, however I am getting https://www.microsoft.com/en-us/download/details.aspx?id=100723 We are sorry, the page you requested cannot be found.
The URL may be misspelled or the page you’re looking for is no longer available.
Permalink
Same on the KB link – https://support.microsoft.com/en-us/help/4484181/december-10-2019-update-for-sharepoint-enterprise-server-2016-kb448418 same error. Maybe too early / fast. 🙂
Permalink
Hi Matthew,
the links were working for me when I published the post and they are also working for me right now.
Permalink
calendar overlay fix included?
Permalink
No. The fix is currently planned for January CU.
Permalink
you would have thought microsoft would have been eager to fix a issue they caused! 🙂
Permalink
Hi Matt,
of course – but please understand that proper testing of code changes is required to ship a fix.
The cut of date for fixes going into a CU is 4 weeks before the CU to allow complete testing of the CU.
The issue was introduce with October CU and reported first around a week after the release through a support case.
Reproducing the issue, isolating it as a problem in the CU, involving the product group to request a hotfix, identifying the root cause and a possible and stable fix and performing the necessary tests was not possible in the short timeframe before the cut of date for December CU.
Cheers,
Stefan
Permalink
Hi Stefan,
I have installed both December CU for SharePoint server 2016. Everything ran successfully, but the configuration database version number is “16.0.4936.1000” while in the upgrade status it shows “16.0.4939.1000” How can I fix it. I tried to clear the SP cache to rerun the configuration wizard PowerShell but nothing has fixed it
Permalink
Hi Shaikha,
this is not the configuration database version. This is the configuration database SCHEMA version.
The last time the schema was changed was with version 16.0.4936.1000. We never guarantee that the database schema version is identical to the version of the patch and you should not use this number as an indicator that a patch was installed correctly.
See here for details:
https://blog.stefan-gossner.com/2014/10/23/common-question-why-does-the-version-number-on-the-servers-in-farm-page-not-change-after-installing-october-cu/
https://blog.stefan-gossner.com/2016/08/23/sharepoint-does-not-have-a-build-version-full-stop/
Cheers,
Stefan
Permalink
Hi Stefan,
i’m also getting the same version numbers as Shaikha and i’m patching my farm using ZDP approach. which version number should i use to complete the side by side file copy process? should i use 16.0.4936.1000 or 16.0.4939.1000?
Permalink
Hi Stefan,
Microsoft Common Vulnerabilities and Exposures were not added in this release to learn about the vulnerability.
Permalink
Hi Sowmya,
as there were no security fixes released in December there was nothing to add here.
Cheers,
Stefan
Permalink
Hi Stefan,
This December there is no Office online Server update?
Thanks
Praveen
Permalink
Hi Praveen,
there is one. You will find the info in my SP2019 blog post.
Cheers,
Stefan
Permalink
Thanks Stefan.
Permalink
I have installed below CU on SharePoint 2016 (16.0.4834.1000)
December 10, 2019, update for SharePoint Enterprise Server 2016 (KB4484178)
December 10, 2019, update for SharePoint Enterprise Server 2016 (KB4484181)
I am facing issue with Search Crawl failure with below error
The content processing pipeline failed to process the item. ( ExpandSegments; ; SearchID = 6A552908-0C86-4876-84E7-FDC01FB582B3
This error is showing in both UAT and PROD Environment I have installed DEC 2019 CU
Permalink
Hi Gautam,
This does not seem to be a known issue.
I would recommend to open a support case with Microsoft support to get this analyzed.
Cheers,
Stefan
Permalink
Me too facing the same issue after installing KB4484178. The content processing pipeline failed to process the item. ( ExpandSegments; ; SearchID ****)
Permalink
Hi Manivannan, did you run PSConfig after installing the patch?
Permalink
Hi Stefan,
running the PSConfig solve my “ExpandSegments;” Crawl Error.
Thank a lot.
Permalink
Hi Stefan,
thank you first for your detaild informations and instructions about SharePoint Pachting.
Is the Security Vulnerability CVE-2019-1491 Fix inclueded in the december 2019 CU’s, i need a reliable statement for our Companys CISO.
Thank you.
Best regards
Philip
Permalink
Hi Philip,
the answer is yes.
The security fix was released in November 2019 and as SharePoint fixes are cumulative all fixes released in November are also included in our December CU.
Cheers,
Stefan
Permalink
Thank you!
Permalink
Hi,
Seems the peoplepicker fix about resolving users from external domains isn’t working.
Error:
The property ‘NoUpnResolveWhenResolvingEmailAddress’ cannot be found on this object. Verify that the property exists and can be set.
Info:
https://support.microsoft.com/en-us/help/4484178/december-10-2019-update-for-sharepoint-enterprise-server-2016-kb448417
Permalink
Hi Kaspar,
did you run the SharePoint configuration wizard after installing the fix?
Cheers,
Stefan
Permalink