January 2022 CU for SharePoint Server 2016 is available for download

The product group released the January 2022 Cumulative Update for SharePoint Server 2016 product family.

This CU also includes Feature Pack 1 which was released with December 2016 CU and Feature Pack 2 which was released with September 2017 CU.

The KB articles for January 2022 CU should be available at the following locations in a couple of hours:

  • KB 5002113 – January 2022 Update for SharePoint Server 2016 (language independent)
    This is also a security update!
  • KB 5002118 – January 2022 Update for SharePoint Server 2016 (language dependent)
    This is also a security update!

The downloads for January 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 2016 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.

SharePoint 2016 January 2022 CU Build Numbers:

Language independent fix: 16.0.5266.1000
Language dependent fix: 16.0.5266.1000

To understand the different version numbers please have a look at my article which explains the different SharePoint build numbers.

Please ensure to have a look at the SharePoint Patching Best Practices before applying new fixes.

Related Links:


  1. Hello Stefan,

    I installed this CU to my SP2016 farm and I’m having trouble to mount/upgrade my SP2013 content database. My schema version is 15.0.5259.1001 (SP2013) and I have succesfully upgraded this database a few month agos during my last test to 16.0.5197.1000 (SP2016). Now the latest schema version on my farm is 16.0.5266.1000 and when running

    Mount-SPContentDatabase -Name dbname -WebApplication Url

    I’m getting the following error:
    An extension defined in the database is not registered with the farm

    When running
    Test-SPContentDatabase -Name dbname -WebApplication url

    I’m getting the following error:
    The number of column pool tables exceeds the database limit. The tables that exceed this limit and should be dropped are .

    This is all very odd to me and looking through the logs doesn’t bring any light.

    I could find this error message in my ULS logs
    02/01/2022 20:56:40.95 powershell (0x29A4) 0x3038 SharePoint Foundation Upgrade PDEUpgradeSequence cxxn8 ERROR Exception while checking applicability of PDEUpgradeSequence on database dbname. Error : System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.Office.Project.Server.Database.Extension.Upgrade.PDEUpgradeSequence.get_IsApplicable()

    Today was supposed to be the day, where I can finally leave that SP2013 server behind. Please help 🙂


    1. Hi Andreas,
      I would suggest to open a support case with Microsoft to get this analyzed in detail.


  2. Hi Stefan,

    Is it possible to upgrade from April 2020 CU to Jan 2022 CU for SharePoint server 2016 directly??


    1. Yes that is possible.


  3. Hello Stefan,

    I’ve installed this CU (KB 5002118) on my SP2016 farm, then after Sharepoint apps are not working and getting below errors.

    Application error when access /sites/thermalservicerecords/ThermalSAPCustomerSearch/Pages/Default.aspx, Error=This page has encountered a critical error. Contact your system administrator if this problem persists.
    at Microsoft.SharePoint.ApplicationRuntime.SafeControls.IsSafeControl(Boolean isAppWeb, String virtualPath)
    at Microsoft.SharePoint.ApplicationRuntime.SPPageParserFilter.AllowVirtualReference(String referenceVirtualPath, VirtualReferenceType referenceType)
    at System.Web.UI.BaseTemplateParser.GetReferencedType(VirtualPath virtualPath, Boolean allowNoCompile)
    at System.Web.UI.BaseTemplateParser.GetUserControlType(VirtualPath virtualPath)
    at System.Web.UI.MainTagNameToTypeMapper.ProcessUserControlRegistration(UserControlRegisterEntry ucRegisterEntry)
    at System.Web.UI.BaseTemplateParser.ProcessDirective(String directiveName, IDictionary directive)

    Thanks in advance.

    Venkata Appini


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.