The product group released the October 2024 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 October 2024 CU should be available at the following locations in a couple of hours:
- KB 5002645 – October 2024 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 5002524 from December 2023 CU.
If this is not yet installed on your Farm, you need to install it together with the language independent fix.
The downloads for October 2024 CU are available through the following links:
- Download October 2024 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 5002524 from December 2023 CU.
If this is not yet installed on your Farm, you need to install it together with the language independent fix.
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 October 2024 CU Build Numbers:
Language independent fix: 16.0.5469.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.
The same situation I already reported in another thread: this new security update is offered through Windows Update, despite of so-called “Microsoft Update” is turned off in WU Settings. It’s not big issue but I am curious if others are experiecing the same behaviour.
With best wishes.
Ladislav Kokeny
Permalink
Hi Stefan
This CU didn`t solve event ID c42q0 issue
Permalink
Does anyone know if opt’ing not to install the Sept. 2024 patch clears you from having to worry about the same workflow issues when installing Oct. 2024 CU?
Permalink
Hi Jon,
any future CU will include the same code change as SharePoint fixes are cumulative.
Cheers,
Stefan
Permalink
Yes, Microsoft does not plan to fix this issue.
Permalink
Any other issues identified after applying this October patch? we put the September patch on hold after installing on one lower environment and fixing the Nintex workflow issue by following the below:
https://blog.stefan-gossner.com/2024/09/13/trending-issue-problems-with-workflows-after-applying-september-2024-cu-for-sharepoint-2016-2019-se/
Any trending issue blog or url for this patch? kindly let us know.
Permalink
Hi Raja,
the issue described in this link will not only be in September CU but in every single CU going forward as it is a side effect of a security fix.
Cheers,
Stefan
Permalink
Thanks for the response. please let us know any new issue reported with this patch.