January 2020 CU for SharePoint Server 2016 is available for download

The product group released the January 2020 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 2020 CU are available here:

  • KB 4484215 – January 2020 Update for SharePoint Server 2016 (language independent)
  • KB 4484220 – January 2020 Update for SharePoint Server 2016 (language dependent)

The download for January 2020 CU is available here:

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 2020 CU Build Numbers:

Language independent fix: 16.0.4954.1000
Language dependent fix: 16.0.4954.1000

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

Related Links:


  1. Before I receive the first couple of questions on this topic: this CU fixes the issue with the not working links in the Calendar overlay buttons are not working after installing the October 2019 updates.


  2. When we will be able to receive patch which fixes not working links in the calendar overlay?
    Before recommendation to open ticket I would like to inform that we have opened ticket for this problem more then month ago 🙂


    1. Please read the comment above your comment.
      The fix is included in this CU.


  3. I have installed both fixes and I receive a Buildversion of 16.0.4948.1000 instead 16.0.4954.1000, why is that?
    If I look in CA under Managed Patch Status, I can see for example “Update for Microsoft SharePoint Enterprise Server 2016 (KB4484220) 64-Bit Edition 16.0.4954.1000 Installed”. If I look in DB Server I can see Content DB have version 16.0.4954.1000 but SharePoint_Config and AdminContent have version 16.0.4948.1000. I’m confused because I have no error by installing and by Product Configuration I have error (Content DB was not in right schema). So I do Get-SPContentDatabase | Upgrade-ContentDatabase and restart Product Configuration. After that no errors, but If I call buildversion, I see 16.0.4948.1000.


  4. Hi Stefan, the patch failed during the Upgrade phase when I installed it on my Dev farm (SP 2016 Enterprise + Project Server, 16.0.4948.1000. Seems to be failing on a lack of permission in content databases.

    Basically the Upgrade wizard keeps failing due to a permissions issue (related to Project Server) on content databases. I found out that the Farm account is part of a database role (PSDataAccess) that actually has a DENY permission set for Insert and Select statements.

    The workaround is to remove the farm account from the PSDataAccess role for each database. I tested this on one database and it upgraded with success.

    I don’t know why it’s doing this NOW. I haven’t changed permissions on these databases since the initial farm setup. This is the first time a patch has complained about those permissions, let alone failing the upgrade.

    I am also unsure of whether it’s appropriate to remove the Farm account from that DB role. I don’t remember setting that permission before so it’s possible the role was automatically assigned as a farm operation; e.g. when I installed Project Server.

    Running PSConfigUI, I get this error:
    An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown. Additional exception information:
    Action 16.1.313.0 of Microsoft.Office.Project.Server.Database.Extension.Upgrade.PDEUpgradeSequence failed. (EventID:ajywk)
    Exception: The SELECT permission was denied on the object ‘MSP_PROJECTS’, database ‘My_Content_Database’, schema ‘pjpub’. (EventID:ajywk)
    Upgrade [SPContentDatabase Name=My_Content_Database] failed. (EventID:an59t)
    Inner Exception: The SELECT permission was denied on the object ‘MSP_PROJECTS’, database ‘My_Content_Database’, schema ‘pjpub’. (EventID:an59t)
    Exception: Action 16.1.313.0 of Microsoft.Office.Project.Server.Database.Extension.Upgrade.PDEUpgradeSequence failed. (EventID:an59t)
    Upgrade Timer job is exiting due to exception: Microsoft.SharePoint.Upgrade.SPUpgradeException: Action 16.1.313.0 of Microsoft.Office.Project.Server.Database.Extension.Upgrade.PDEUpgradeSequence failed. —> System.Data.SqlClient.SqlException: The SELECT permission was denied on the object ‘MSP_PROJECTS’, database ‘My_Content_Database’, schema ‘pjpub’. — End of inner exception stack trace —


    1. As I mentioned above, I found a workaround so I could upgrade a database individually (using Upgrade-SPContentDatabase). But I went back to check the permissions for that SQL login and found that the PSDataAccess role had been re-added for the Farm account for that database. Apparently there’s a timer job that manages that security and overrides your changes. That would make my workaround kind of useless, then.


      1. Hi Greg,
        it is hard to answer without deeper analysis. I would recommend to open a ticket with Microsoft support to perform this analysis.


Leave a Reply

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