The product group released the May 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 May 2023 CU should be available at the following locations in a couple of hours:
- KB 5002397 – May 2023 Update for SharePoint Server 2016 (language independent)
This is also a security update! - There was no language dependent fix released this month.
The most recent language dependent fix is KB 5002370 from April 2023 CU.
The downloads for May 2023 CU are available through the following links:
- Download May 2023 Update for SharePoint Server 2016 (language independent)
This is also a security update! - There was no language dependent fix released this month.
The most recent language dependent fix is KB 5002370 from April 2023 CU.
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 May 2023 CU Build Numbers:
Language independent fix: 16.0.5395.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
Hi Stefan,
Whether this SP2016 Mat 2023 CU resolved the “Trending Issue: 503 response on SP2016 servers running on Windows Server 2012 R2 after installing April 2023 CU”?
Permalink
Hi Prabhu, the answer is no.
The fix is currently planned for June 2023 CU – but it will apply the same solution as outlined in this blog post:
https://blog.stefan-gossner.com/2023/04/14/trending-issue-503-response-on-sp2016-servers-running-on-windows-server-2012-r2-after-installing-april-2023-cu/
Cheers,
Stefan
Permalink
Hi Stefan,
Do you know whether this CU is considered Important or Critical?
Permalink
Hi Callie,
you can verify this easily yourself for each CU by checking the CVEs listed in the KB article.
May 2023 CU for SharePoint Server 2016 adresses three CVEs per the KB:
CVE-2023-24950: Important
CVE-2023-24954: Important
CVE-2023-24955: Critical
So the highest rating of the addressed security vulnerabilities is Critical
Cheers,
Stefan
Permalink
Do we have any further CU release for SP2013 ?,I knew that officially the SP2013 product support has stopped by MS.
Permalink
Hi Nixon – no further SP2013 fixes will be released.
Permalink
I have now patched two SP2016 (Windows Server 2016) farms with May 2023 CU and still have the issue where Subscription Settings database loses db_owner permissions for Farm Service account.
This was supposed to be fixed in April 2023 CU. I have confirmed that the permission was there before running psconfig.
To fix it I have to add that permission back to that database and run psconfig again….on all servers.
Permalink
Hi Kalvervo,
I would recommend to open a support ticket to get this analyzed if this is not fixed.
Cheers,
Stefan
Permalink
Hi Stefan,
We have not installed March and April CU on our SharePoint 2016 server. So now we are planning to install the May CU. As in May CU there was no language dependent fix released so please let me know if we can install the language dependent from April CU together with May CU language independent?
Thanks
Permalink
Hi Krishn,
yes you need to install the most recent language dependent fix which is the one from April 2023.
Cheers,
Stefan