The product group released the February 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 February 2025 CU will be available at the following Location in a couple of hours:
- KB 5002678 – February 2025 Update for SharePoint Server 2019 (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 5002667 from January 2025 CU.
If this is not yet installed on your Farm, you need to install it together with the language independent fix.
The downloads for February 2025 CU are available through the following links:
- Download February 2025 Update for SharePoint Server 2019 (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 5002667 from January 2025 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 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 February 2025 CU Build Number:
Language independent fix: 16.0.10416.20050
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
Dear Stefan
Nintex workflow stopped after SharePoint CU 02-2025— KB5002678
workflow status = failed or stopped
Any Solution Please.
regards.
Permalink
we found the solution:
https://sharepointstuff.com/2018/09/27/sharepoint-workflows-failing-on-start/
Permalink
The issue got solved after executing below commands:
Add-PSSnapin Microsoft.SharePoint.PowerShell
$farm=Get-SPFarm
$farm.EnablePreParseSecurityCheckForWorkflow = $false
$farm.update()
iisreset –
Permalink
Hi Salil,
be careful! This setting should only be used for a very short time while implementing the final solution as it disables several historic and potential future security fixes.
This setting must not be used as a long term solution.
Cheers,
Stefan
Permalink
Hi Stefan, Could you please suggest what the final solution should be?
Permalink
Hi Vishnu,
evaluate the ULS log, identify the specific namespaces which need to be allow listed and add them to the web.config.
Cheers,
Stefan
Permalink
Due to limited resources I don’t update Sharepoint every month.
We have one Sharepoint 2010 approval flow. This broke with the September update and the solution was straightforward: adding 2 lines to the web.config.
With the February this broke again (Failed to start) but I’m at a loss how to solve this. As far as I understand Microsoft added the necessary authorizedTypes. Are the lines I added in September still in there and do I need to remove them? Is there another line I need to add?
For the moment I execute the command in the post above every time the flow is executed (max few times a week).
The log show this error: Legacy Workflow Infrastructure c42q0 High Potentially malicious xoml node:
Also thanks for this Blog Stefan, it’s a very important and helpful source for Sharepoint updates.
Permalink
Hi Thierry,
you need to extract the Assembly and Namespace information from the c42q0 error and add an entry to the authorizedTypes section that covers this assembly and namespace.
Cheers,
Stefan
Permalink
Stefan, what changes were made in the cumulative update that necessitated adding assemblies and namespaces to the web config file?
Permalink
Hello,
Since the installation all doc id links are redirected to the search page with sometime 2 results, sometime 4 of the same item and sometime just one.
Exemple with SearchQueryTool for a docset :
Total Rows: 4
Total Rows Including Duplicates: 4
Sometime the tool detect items as a duplicate and sometime not.