February 2022 CU for SharePoint Server 2019 is available for download

The product group released the February 2022 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 2022 CU will be available at the following Location in a couple of hours:

  • KB 5002135 – February 2022 Update for SharePoint Server 2019 (language independent)
    This is also a security update!
  • KB 5002134 – February 2022 Update for SharePoint Server 2019 (language dependent)

The downloads for February 2022 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 2022 CU Build Number:

Language independent fix: 16.0.10383.20001
Language dependent fix: 16.0.10383.20001

Related Links:


  1. RSS feeds are not working after deploying Feb 2022 PU on SP19. Getting “ProtocolError occurred trying to complete the request. The server returned a status code of : Forbidden and the status description is : “Forbidden”” error message. Have not opened up a ticket with Microsoft Support yet.


    1. I am having this exact issue. Did you ever figure out the problem? It was just reported to me today, I patched the environment a few weeks ago, so I have to assume it’s the patch that broke it as it used to work. Going to open a ticket in the meantime.


      1. The February 2022 SharePoint 2019 PU has changed how the disableIntranetcalls and disableIntranetcallsfromapps is handled. We set both of these properties using the SPFarmPropertyBag resource which sets the value for the key to [String]. We built out our farms in the fall of 2019 using this, and our configuration has been checking for this value successfully since then, however after the February 2022 PU, the RSS Viewer web part broke. The only option we had to resolve it is to explicitly set the property to [Boolean].


  2. are you sure SharePoint monthly update is Cumulative Update ,i didont find the key in the kb document。


    1. yes they are all cumulative.


  3. hi anyone facing the issues after patch February 2022 CU unable to call lightbox play the mp4 video ? ( repost here , after tested Mar CU have problem ,try on Feb Cu also facing same issues)

    check on the browser noticed below 404(Not found) >> GET https://xxx/_layouts/15/Lightbox.aspx?xxxxxx…mp4 404 (Not Found)


    1. Yes same problem here, embedded video not working


  4. We have SharePoint Server 2019 (on-Prem) with Project Server 2019. We applied Feb 2022 patch.

        SharePoint Server 2019 – KB 5002135
        SharePoint Server 2019 MUI/language patch – KB 5002134 16.0.10383.20001 February 2022

    When we ran SharePoint configuration wizard, we got following  error message 

    ERROR    FirstLine should start with ‘CREATE’: /**/

    ERROR Upgrade [SPContentDatabase Name=ProjectWebAppDEV] failed

    ERROR Exception: Specified argument was out of range of valid values. Parameter name: sLine

    What could have caused this error and how do we fix it?


    1. Hi Ana,
      this means that there are unsupported modifications in this database. This can happen through different things:
      – manual modification of the content database
      – 3rd party products modifying the database content

      It looks that someone/something modified stored procedures or table valued functions in your content database which is unsupported.
      These changes have to be reverted.



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.