February 2026 CU for SharePoint Server 2019 is available for download

Important: If your current farm patch level is September 2025 CU, remove the NT Authority\system account from WSS_WPG and IIS_IUSRS local security groups of the SharePoint machines – otherwise installing the SharePoint fixes will fail.

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:

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:

17 Comments


    1. 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

      Reply

      1. Are you saying the timer job in SharePoint Server 2019 also no longer depends on stsadm.exe now?

        Reply

        1. 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

          Reply

        2. H Atis,
          the KB article has been corrected.
          Thanks for the heads-up!
          Cheers,
          Stefan

          Reply

          1. Thank you, Stefan!


    2. CVE‑2026‑20948 lists SharePoint Server 2019, but the KB article doesn’t.

      Reply

      1. Hi Atis,
        the CVE information in the KB article has been corrected.
        Cheers,
        Stefan

        Reply

  1. 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

    Reply

    1. 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

      Reply

  2. I have this issue as well and I’m still on January update, SharePoint 2019.

    Reply

    1. Hi Laur,
      which issue do you mean?
      You did not reply to a previous comment.
      Cheers
      Stefan

      Reply

      1. 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.

        Reply

        1. 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?

          Reply

        2. 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

          Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.