The product group released the May 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 May 2025 CU will be available at the following Location in a couple of hours:
- KB 5002708 – May 2025 Update for SharePoint Server 2019 (language independent)
This is also a security update! - KB 5002706 – May 2025 Update for SharePoint Server 2019 (language dependent)
This is also a security update!
The downloads for May 2025 CU are available through the following links:
- Download May 2025 Update for SharePoint Server 2019 (language independent)
This is also a security update! - Download May 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 May 2025 CU Build Number:
Language independent fix: 16.0.10417.20010
Language dependent fix: 16.0.10417.20010
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, I really appreciate your blog. If you regularly install SharePoint CU, you simply have to know your blog. Even after extensive research, I haven’t found a solution to the following problem. I hope you can help me… We install SharePoint CU in our SharePoint 2019 farm 3-4 times a year (depending on the criticality of the security fixes). Everything’s working perfectly so far. Immediately after installing the CU (including the Config Wizard), the upgrade sessions for the individual farm servers are visible in Central Administration under “Check upgrade status” (with the status “Success”). When I access the “Upgrade Status” again a few weeks later, before the next update, the entries from the last update have disappeared (“There are no items to show in this view.”). Can this be changed (e.g. retention time for these records can be configured or deletion of these records can be switeched off)?
Permalink
Hello Reto.
From the technical side I am also interested in this, why these upgrade session records are being lost.
On the farm I manage I noticed that upgrade records “disappear” if they are older than 120 days.
However, on the previous architecture (SharePoint 2016) this does not happen, all of them are visible in the history.
I help myself by taking a screenshot of the page in question (/_admin/UpgradeStatus.aspx) after the upgrade, when I casually check various settings within CA.
I also make a copy of the upgrade log (Upgrade-YYYYMMDD-.log) from the ULS folder.
I assume that the data for these records may be in some hidden list within the CA website, and in the background, perhaps either in the config db, or in the CA content db.
Their deletion may not be processed by some timer job (I couldn’t find one in their overview), but perhaps by some stored procedure in the corresponding db.
Or all of this, let’s say, is hard coded in server application code… but these are just my assumptions, maybe Stefan will shed more light on the case.
Permalink
Hi Stefan,
On 2 exact setups We ran the sharepoint 2019 Cumulative updates:
Download May 2025 Update for SharePoint Server 2019 (language independent)
Download May 2025 Update for SharePoint Server 2019 (language dependent)
We ran Configuration Wizard after the language dependent update.
Now our SharePoint 2019 Backup get’s stuck and will not backup as it did before the update.
Permalink
Hi Keever,
I would recommend to open a support case with Microsoft to get assistance.
Cheers,
Stefan