The product group released the September 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 September 2023 CU should be available at the following locations in a couple of hours:
- KB 5002494 – September 2023 Update for SharePoint Server 2016 (language independent)
This is also a security update! - KB 5002501 – September 2023 Update for SharePoint Server 2016 (language dependent)
This is also a security update!
The downloads for September 2023 CU are available through the following links:
- Download September 2023 Update for SharePoint Server 2016 (language independent)
This is also a security update! - Download September 2023 Update for SharePoint Server 2016 (language dependent)
This is also a security update!
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 September 2023 CU Build Numbers:
Language independent fix: 16.0.5413.1001
Language dependent fix: 16.0.5413.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
I installed the September 2023 CU and now none of my sites or admin center will open
Open a ticket with Microsoft and have them review the logs
Permalink
Hi Michael,
would be great if you could share what response (http status code) you got when trying to browse to the sites.
Cheers,
Stefan
Permalink
HTTP ERROR 500
Permalink
Hi Michael, please let me know which antivirus solution (product and version) you have in place.
Permalink
Try deactivating AMSI integration on affected web applications.
Disable-SPFeature -Identity 4cf046f3-38c7-495f-a7da-a1292d32e8e9 -Url
Permalink
I also had to disable the AntimalwareScan feature to avoid the 500 error. IIS showed 500.0.2 and nothing helpful was found in ULS and event logs. Strangely this happened only on one of eight SP16 farms.
Permalink
Hi Samson,
a support case should be raised to allow us to analyze why that happens.
Disabling this security feature will avoid the issue – but it also means that a security functionality Microsoft provided is no longer active in your SharePoint farm.
Cheers,
Stefan
Permalink
Hi Samson, please let me know which antivirus solution (product and version) you have in place.
Permalink
That Worked !!!!! Thank you
Permalink
I got all the SharePoint sites working, except for Central admin. And good ideas?
Permalink
Ok – Figure it out ran SharePoint configuration wizard, and now Central admin working again.
Permalink
My search crawl was infinitely growing the gthrsvc folder as well, psconfig on the search servers fixed it.
Permalink
I first installed Language Dependent fix. Than ran SharePoint Products Configuration Wizard but version number didn’t change.
Then I installed Language Independent fix and after running wizard, version number changed to 16.0.5413.1000 which is actually for language dependent fix. No idea what happened.
Permalink
Hi Ali,
I’m not sure which way you checked the version as there are various different places to look for version numbers in SharePoint
See here for details on how to correctly identify if a fix is installed:
https://blog.stefan-gossner.com/2016/08/23/sharepoint-does-not-have-a-build-version-full-stop/
Cheers,
Stefan
Permalink
Hi,
I am getting issue in blog site ‘system.web.UI.HtmlControls.HtmlGenericControl’ not allowed on this this, i have tried with MS provide solution but didn’t work
Permalink
Hi Abdul,
I would recommend to open a ticket with Microsoft support if you need assistance with this issue.
Cheers,
Stefan