The product group released the January 2025 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 January 2025 CU should be available at the following locations in a couple of hours:
- KB 5002672 – January 2025 Update for SharePoint Server 2016 (language independent)
This is also a security update! - KB 5002671 – January 2025 Update for SharePoint Server 2016 (language dependent)
This is also a security update!
The downloads for January 2025 CU are available through the following links:
- Download January 2025 Update for SharePoint Server 2016 (language independent)
This is also a security update! - Download January 2025 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 January 2025 CU Build Numbers:
Language independent fix: 16.0.5483.1001
Language dependent fix: 16.0.5483.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
hi Stefan
Is there any issues/bugs found so far with Jan 2025 CU for SP 2016?
This is because I am going to update my farm in next few weeks
Thanks
Permalink
Hi Ramen,
so far I did not see any trending issues with this CU.
But each farm is different and uses a different combination of features.
It is impossible to test all combinations of possible execution paths before releasing a fix.
That is the reason that we recommend to ALWAYS test each SharePoint fix in a test environment and verify that ALL CRITICAL FEATURES work correctly before installing the fix in production. And keep in mind that SharePoint fixes cannot be uninstalled.
Cheers,
Stefan
Permalink
Greetings,
Has there been any reported issues with workflow stemming from the January 2025 SharePoint Server 2016 patches? We patched our farm yesterday (1/30.2025) and our initial testing was good but we have received numerous reports of 2010 workflows failing to run. to run today on Jan 31. All of our 2013 Workflows and most of our 2010 workflows are fine, it’s just a few 2010 flows that have been reported. Rebuilding the workflow was the only way we could get them running again. I wasn’t able to find anything in the logs and the only messages I could find in Workflow History are that the workflow was cancelled by the system account. There also seems to be a new dialogue notice in SharePoint Designer 2013 regarding workflows and infopatch compatibility.
Thank you kindly,
Cory Voss
Permalink
Were you able to resolve this issue except rebuilding the workflow. My workflow is stuck at pause and does not resume sometimes after pause is complete. It is a SP2010 workflow. All sept and dec 2024 cu fixes are implemented on the farm.
Permalink
Hi
after installing Jan 2025 cu we are seeing SP 2010 workflows are failing and seeing issue as sept 2024 report as below. we already have entries but seeing issues.
You might experience an issue in which SharePoint workflows can’t be published because the unauthorized type is blocked. This issue also generates event tag “c42q0” in SharePoint Unified Logging System (ULS) logs.
To work around this issue, register the safe types in the Web.config file. You can look for event tag “c42q0” in ULS logs to find the blocked type. If the type and assembly are safe, add the type to the authorized list in the Web.config file. For example:
<System.Workflow.ComponentModel.WorkflowCompiler>
thanks
Praveen