The product group released the January 2025 Cumulative Update for SharePoint Server 2019 product family. SharePoint Server 2019 is patched with a language dependent and a language independent fix.
The KB article for January 2025 CU will be available at the following Location in a couple of hours:
- KB 5002666 – January 2025 Update for SharePoint Server 2019 (language independent)
This is also a security update! - KB 5002667 – January 2025 Update for SharePoint Server 2019 (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 2019 (language independent)
This is also a security update! - Download January 2025 Update for SharePoint Server 2019 (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 2019 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.
Please ensure to have a look at the SharePoint Patching Best Practices before applying new fixes.
SharePoint 2019 January 2025 CU Build Number:
Language independent fix: 16.0.10416.20041
Language dependent fix: 16.0.10416.20041
Related Links:
- Technet: Updated Product Servicing Policy for SharePoint Server 2019
- Blog: SharePoint Patching Best Practices
- 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 Zero-Downtime Patching Demystified (applies also to SharePoint Server 2019)
- Blog: SharePoint does not have a build version. Full Stop.
Permalink
Let’s hope that installing the KB ending in 666 goes smoothly and doesn’t give us a taste of the underworld. It’s considered a bad omen, after all. Fingers crossed!
Permalink
Anyone noticing a problem with Workflows after installing this update? For me specifically, Nintex Workflows.
Permalink
Hi Corbett,
which CU was installed earlier?
Might be you are running into this issue which was introduced with September 2024 CU and potentially amplified with December 2024 CU:
https://blog.stefan-gossner.com/2024/12/11/resolved-trending-issue-problems-with-workflows-after-applying-september-2024-cu-for-sharepoint-2016-2019-se/
It is now required to manually enable all customer workflow actions (like workflow actions coming from Nintex) through updates to the web.config and the owstimer.exe.config.
Cheers,
Stefan
Permalink
Hi Stefan,
The updates for the web.config were added as part of PSconfig as documented, but not for owstimer config. We have 2010 workflows that are failing with the declare a record action and resume from pause. Will these be added to owstimer config or should we add the 4 lines to our owstimer configs?
Thanks,
Rob
Permalink
Workflows seems to be broken…again!
I noticed three new additions to web-config:
And lots of “c42q0” – events iin ULS-log.
Legacy Workflow Infrastructure c42q0 High Potentially malicious xoml node:
🙁
Permalink
Workflows seems to be broken…again!
I noticed three new additions to web-config:
”
”
And lots of “c42q0” – events iin ULS-log.
“Legacy Workflow Infrastructure c42q0 High Potentially malicious xoml node: ”
🙁
Permalink
authorizedType Assembly=”Microsoft.SharePoint.WorkflowActions, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” Namespace=”Microsoft.SharePoint.WorkflowActions” TypeName=”*” Authorized=”True”
authorizedType Assembly=”Microsoft.SharePoint.WorkflowActions, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” Namespace=”Microsoft.SharePoint.WorkflowActions.WithKey” TypeName=”*” Authorized=”True
authorizedType Assembly=”Microsoft.Office.Workflow.Actions, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” Namespace=”Microsoft.Office.Workflow.Actions” TypeName=”*” Authorized=”True”
Permalink
0x1630 SharePoint Foundation Legacy Workflow Infrastructure c42q0 High Potentially malicious xoml node: ns0:RootWorkflowActivityWithData x:Class=”Microsoft.SharePoint.Workflow.ROOT”
namespace:Microsoft.Office.Workflow.Actions;Assembly=Microsoft.Office.Workflow.Actions, Version=15.0.0.0, Culture=neutral, PublicKeyToken=null” namespace:Microsoft.SharePoint.WorkflowActions.WithKey;Assembly=Microsoft.SharePoint.WorkflowActions, Version=15.0.0.0, Culture=neutral, PublicKeyToken=null” namespace:Microsoft.SharePoint.WorkflowActions;Assembly=Microsoft.SharePoint.WorkflowActions, Version=15.0.0.0, Culture=neutral, PublicKeyToken=null”>
Permalink
Did you have December 2024 CU installed already?
Permalink
Yes. That CU didn’t break workflows after they were broken in September 2024 CU and fixed with web.config tweaking.
Permalink
yeesh. December CU caused us workflow issues for 3rd party workflow extensions. See my comments on Stefan’s December CU post. December CU hasn’t been an issue for farms that aren’t using 3rd party assemblies.
Thanks for replying!
Permalink
We are not using any 3rd party workflows. We will open a ticket with Microsoft Support – thatks for answers 🙂
Permalink
Hi Taavi,
if you need assistance to get the issue analyzed, please ensure to open a ticket with Microsoft Support.
Cheers,
Stefan
Permalink
For us, simple workflows continue to work without any problems. Only complex workflows, e.g. with impersonation steps, do not start. We have republished these workflows in the Sharepoint Designer. Now it seems to be working again.
Permalink
Hello Ronald and thank you for posting 🙂 Can you tell what error you got? We have a customized approval workflow that does not have impersonation steps but is otherwhise slightly complex. It is only saying “failed on start”
Permalink
Republishing fixed our customized workflows as well but OOTB approval workflows seem to remain broken and new approval workflows cannot be created via SharePoint GUI…
Permalink
Installed the 2025 Cumulative Updates, now Nintex workflows are not running. Did anyone find a resolution to this?
Permalink
Please find https://blog.stefan-gossner.com/2024/12/10/december-2024-cu-for-sharepoint-server-2019-is-available-for-download/#comment-27814
Permalink
Nintex released a fix on 22/01/2025: NW 2019 v5.2.12.0.
https://help.nintex.com/en-US/platform/ReleaseNotes/NintexSharePoint2019.htm