February 2021 CU for SharePoint Server 2019 is available for download

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

  • KB 4493194 – February 2021 Update for SharePoint Server 2019 (language independent) – This is also a security update!
  • KB 4493193 – February 2021 Update for SharePoint Server 2019 (language dependent)

The download for February 2021 CU is available through the following link:

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 2021 CU Build Number:

Language independent fix: 16.0.10371.20043
Language dependent fix: 16.0.10371.20043

Related Links:


  1. When installing the language dependent update it says “no products affected on the system”. I don’t have any language packs installed, but above you said I need to install the language dependent update anyways.


    1. Hi Justin,
      that should not happen.
      In this case you should open a support case with Microsoft to get this investigated.


  2. Sometimes it takes a while after the binary install. A timer job updates the internal list of installed products. Sometimes a reboot can fix this. Sometimes I could solve this by resetting the SharePoint Timer cache.


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.