The product group released the December 2023 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 2023 CU should be available at the following locations in a couple of hours:
- KB 5002535 – December 2023 Update for SharePoint Server 2016 (language independent)
- KB 5002524 – December 2023 Update for SharePoint Server 2016 (language dependent)
The downloads for December 2023 CU are available through the following links:
- Download December 2023 Update for SharePoint Server 2016 (language independent)
- Download December 2023 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 2023 CU Build Numbers:
Language independent fix: 16.0.5426.1001
Language dependent fix: 16.0.5426.1000
To understand the different version numbers please have a look at my article which explains the different SharePoint build numbers.
Please ensure to have a look at the SharePoint Patching Best Practices before applying new fixes.
Related Links:
- Technet: Updated Product Servicing Policy for SharePoint Server 2016
- Blog: SharePoint Patching Best Practices
- 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
FYI
In the text above there is a minor typo: both hotfixes are designated as ‘(language independent)’ where KB5002524 is ‘(language dependent)’.
Permalink
Thanks for the hint! I fixed it!
Permalink
Hello Stefan,
Small error on your article: kb5002524 is language dependent fix, not independent.
Thanks.
Permalink
Thanks for the hint! I fixed it!
Permalink
I am getting this error after installing the updates and running psconfig.. Prior to this update the Web.config file was 876kb and there were no issues.
Detailed Error Information:
Module IIS Web Core
Notification Unknown
Handler Not yet determined
Error Code 0x80070032
Config Error Cannot read configuration file because it exceeds the maximum file size
Config File \?\C:\inetpub\wwwroot\wss\VirtualDirectories\6536\web.config
d
Permalink
Hi Lee,
see here for a fix:
https://blog.stefan-gossner.com/2022/10/17/trending-issue-cannot-read-configuration-file-because-it-exceeds-the-maximum-file-size-on-sharepoint-server-2013/
You might need to increase the maximum size of the web.config file.
Cheers,
Stefan
Permalink
Hi Stefan, we faced the same issue last month and increased the web config file size limitation in the registry settings. But that’s just a work around. The root cause for the problem is not yet addressed. The main reason for the growth of the web.config file is the duplicate entries getting added under “Authorized Types” during patching. We patched our test servers this month and confirmed that this is an issue during patching. Could you please escalate this issue to your product team and provide us the solution to stop this duplication?
Permalink
Hi Karthikeyan,
I haven’t seen a hotfix request to get this addressed.
If this is important for you I would suggest to open a support case with Microsoft to get this investigated.
Cheers,
Stefan
Permalink
Thanks very much, that fixed the issue.