For more details check this article: Trending Issue: SharePoint fixes fail to install after installation of September 2025 CU
The product group released the February 2026 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 2026 CU will be available at the following Location in a couple of hours:
- KB 5002834 – February 2026 Update for SharePoint Server 2019 (language independent)
This is also a security update! - KB 5002836 – February 2026 Update for SharePoint Server 2019 (language dependent)
This is also a security update!
The downloads for February 2026 CU are available through the following links:
- Download February 2026 Update for SharePoint Server 2019 (language independent)
This is also a security update! - Download February 2026 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 February 2026 CU Build Number:
Language independent fix: 16.0.10417.20097
Language dependent fix: 16.0.10417.20097
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
Improvements and fixes section in https://support.microsoft.com/en-us/kb/5002836 does not seem right (SPSE, STSADM)
Permalink
Hi Atis,
the information is correct.
Up till January 2026 CU SPSE had a dependency on stsadm.exe to recycle the timer services.
As stsadm.exe no longer exists the timer service recycling job was not functional.
February CU has now implemented the functionality differently and removed the dependency on stsadm.exe
Cheers,
Stefan
Permalink
Are you saying the timer job in SharePoint Server 2019 also no longer depends on stsadm.exe now?
Permalink
Ah! Now I see the problem.
The KB for SP2019 language pack contains the incorrect information.
No of course not. This is a SPSE only change – and the other details also need to be reviewed.
Let me talk to the relevant team to get this updated.
Cheers,
Stefan
Permalink
H Atis,
the KB article has been corrected.
Thanks for the heads-up!
Cheers,
Stefan
Permalink
Thank you, Stefan!
Permalink
CVE‑2026‑20948 lists SharePoint Server 2019, but the KB article doesn’t.
Permalink
Hi Atis,
CVE-2026-20948 was already fixed in January CU.
You will find it in this KB article:
https://support.microsoft.com/en-us/topic/description-of-the-security-update-for-sharepoint-server-2019-january-13-2026-kb5002825-58fc2a89-ca42-465e-8659-cfea5acb3918
Cheers,
Stefan
Permalink
Hi Atis,
the CVE information in the KB article has been corrected.
Cheers,
Stefan
Permalink
Hi Stefan,
I’ve noticed that since installing this update on our DEV environment, we can no longer create new list forms using SharePoint Designer. We receive an error stating: Could not save the list changes to the server
I’ve already raised this with Microsoft Support to investigate, but wondered if anyone else has reported the same issue? Or experienced this issue in the past?
Kind regards,
Calum
Permalink
Hi Calum,
my suggestion would be to take a fiddler trace and check the error message returned from the server. In case it is talking about an unsafe control – we have a fix available. If it is something different it might require more investigation. Feel free to provide details from fiddler response here.
Cheers,
Stefan
Permalink
Hello Laur,
I do not know if Microsoft will take much effort into any fixes for SharePoint Designer anymore – even if there should be still some support until July this year:
https://mc.merill.net/message/MC1230891
https://learn.microsoft.com/en-us/lifecycle/products/sharepoint-designer-2013
What I want to say is the following: for middle term purposes I would not rely on SharePoint Desginer at all.
Best regards
Gerald
Permalink
I have this issue as well and I’m still on January update, SharePoint 2019.
Permalink
Hi Laur,
which issue do you mean?
You did not reply to a previous comment.
Cheers
Stefan
Permalink
I see, sorry. I have the same issue as Calum; We can no longer create new list forms using SharePoint Designer. We receive an error stating: Could not save the list changes to the server. We use SharePoint 2019 with January patches applied.
Permalink
Hi Laur,
Thanks for mentioning this. Glad to know that we’re not alone with this issue!
I made a mistake in my previous comment: we actually have the January 2026 patches installed on our SP2019 DEV environment. So it sounds like something has changed recently as the last set of patches we installed was October 2025.
Out of curiosity, what was the last set of patches you installed when you didn’t have this issue?
Permalink
Hi Laur,
did you open a support case for this?
If yes, it would be great if you could send me the SR number using the “Contact the blog author” option at the top right of this page.
Cheers,
Stefan