The product group released the November 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 November 2024 CU should be available at the following locations in a couple of hours:
- KB 5002654 – November 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 November 2024 CU are available through the following links:
- Download November 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 November 2024 CU Build Numbers:
Language independent fix: 16.0.5474.1001
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
Hello Stefan, All
After Installing November month patch Does any one experienced any bug on your SharePoint farm?
If yes what is the workaround.
Thanks
Durga
Permalink
The description of the KB5002654 security update is extremely vague:
The KB page links to a Microsoft Advisory page, where the only information available is:
“The update provides a defense in depth enhancement regarding redirections.”
..and then just links back to the KB page (!).
What’s going on? 🙂
Permalink
Hi Will,
descriptions security fixes are often vague to avoid giving information away which would enable malicious users from exploiting the resolved issue.
My assumption is that this is also the case here.
Cheers,
Stefan
Permalink
Thanks for replying, Stefan!
I know and I thought the same, but this is beyond vague compared to other Microsoft MSRC security advisories: there is no Impact, no Max Severity rating, no CVSS scores, no nothing. It’s like the MSRC team made a mistake when they filled in the advisory? Or alternatively, this is an Extra Top Secret vulnerability, but in that case they should at least have given it a Severity rating of “Very Important”. 🙂
Anyway, it makes it very hard for us to make an informed decision about the importance and priority of applying Nov 2024 CU for SP2016. I know the recommendation is to apply CUs at once, but this Advisory is just so very atypical that it made me react.
Thanks for keeping up your blog, it’s invaluable!