January 2020 CU for SharePoint 2013 product family is available for download

The product group released the January 2020 Cumulative Update for the SharePoint 2013 product family.

For January 2020 CU we have full server packages (also known as Uber packages). No other CU is required to fully patch SharePoint.

As this is a common question: Yes, January 2020 CU includes all fixes from January 2020 PU.

ATTENTION:

Be aware that all Updates for SharePoint 2013 require SharePoint Server 2013 SP1 to be installed first.

Please also have a look at the article that discusses how to properly patch a SharePoint 2013 farm which has Search enabled (see below).

Previous releases of the SharePoint Server 2013 cumulative update included both the executable and the .CAB file in the same self-extracting executable download. Because of the file size, the SharePoint Server 2013 package has been divided into several separate downloads. One contains the executable file, while the others contain the CAB file. All are necessary and must be placed in the same folder to successfully install the update. All are available by clicking the same Hotfix Download Available link in the KB article for the release.

This CU includes all SharePoint 2013 fixes (including all SharePoint 2013 security fixes) released since SP1. The CU does not include SP1. You need to install SP1 before installing this CU.

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

  • KB 4484228 – SharePoint Foundation 2013 January 2020 CU
  • KB 4484232 – SharePoint Server 2013 January 2020 CU
  • KB 4484230 – Project Server 2013 January 2020 CU
  • There was no fix released for Office Web Apps Server 2013 this month

The Full Server Packages for January 2020 CU are available through the following links:

After installing the fixes you need to run the SharePoint 2013 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.

Be aware that the SharePoint Server 2013 CU contains the SharePoint Foundation 2013 CU. And the Project Server 2013 CU also contains the SharePoint Server 2013 CU and SharePoint Foundation 2013 CU.

Related Info:

11 Comments


  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.

    Reply

  2. Hi Stefan, this update did not fix the issue on SP2013 where this error comes up when previewing a master page:

    System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.SharePoint.WebPartPages.WebPartPage.get_ShouldStampRequestDigest() at Microsoft.SharePoint.WebPartPages.WebPartPage.FormOnLoad(Object sender, EventArgs e) at System.Web.UI.Control.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

    This error started after applying the October 2019 CU, and others still have the same issue. Any advice?

    Reply

    1. Hi Marius,
      I’m not aware of such a problem in SharePoint Server 2013, only in SharePoint Server 2016 (here it was fixed in December 2019 CU).
      If this exists in SharePoint server 2013 then chances are low that a fix is created.
      The reason is that SharePoint Server 2013 is in extended support where usually only security fixes released.
      If you need non security fixes for your SharePoint environment you should upgrade to a fully supported version of SharePoint, e.g. SharePoint Server 2016 or 2019.
      Cheers,
      Stefan

      Reply

      1. Hi Stefan,

        Unfortunately after installing KB4484232 on our SharePoint Server 2013 we are getting the same previewing master page error above.

        We still having the Backups of the servers since they were patched last weekend.

        Moving to SP2016 or SP2019 would take a long journey at this point.

        Would you advise restoring the backups since there a low chance that a fix will be created.

        Cheers,
        Marcos

        Reply

        1. Hi Marcos,
          the fix here will be carried forward in future security fixes.
          Rolling back would mean you will not be able to install future security fixes which is discouraged.
          I would recommend to open a ticket with Microsoft support to get this investigated.
          Cheers,
          Stefan

          Reply

        2. Hi Marcos and Stefan,
          May I know what Previewing Master Page error it is, thanks.

          Reply

          1. In SharePoint Server 2016 you would see this error in the ULS log:

            09/01/2019 10:50:32.14 w3wp.exe (WFE:0x0001) 0x24C4 SharePoint Foundation General 8nca Medium Application error when access /_layouts/15/preview.aspx, Error=Object reference not set to an instance of an object. at Microsoft.SharePoint.WebPartPages.WebPartPage.get_ShouldStampRequestDigest() at Microsoft.SharePoint.WebPartPages.WebPartPage.FormOnLoad(Object sender, EventArgs e)……..
            09/01/2019 10:50:32.14 w3wp.exe (WFE:0x0001) 0x24C4 SharePoint Foundation Runtime tkau Unexpected System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.SharePoint.WebPartPages.WebPartPage.get_ShouldStampRequestDigest() at Microsoft.SharePoint.WebPartPages.WebPartPage.FormOnLoad(Object sender, EventArgs e)………
            09/01/2019 10:50:32.14 w3wp.exe (WFE:0x0001) 0x24C4 SharePoint Foundation General ajlz0 High Getting Error Message for Exception System.Web.HttpUnhandledException (0x80004005): Exception of type ‘System.Web.HttpUnhandledException’ was thrown. —> System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.SharePoint.WebPartPages.WebPartPage.get_ShouldStampRequestDigest() at Microsoft.SharePoint.WebPartPages.WebPartPage.FormOnLoad(Object sender, EventArgs e).


          2. Stefan, Thank you for your advice early on. I appreciate that.

            Michael, If you go to Site Setting > Design Manager > Edit Master Pages > [Click on the master page name] then you will get the error. When checking the logs you get the same logs Marius posted on a comment above. (SharePoint Server 2013)

            If you click on “Go back to site” the error will disappear and the preview will work. Also if you go to the top left page and click “Change Preview Page” then “Select Existing” you can add the URL of your site and it will also work.


  3. Stefan, is there any reason why KB4484232 shows up 41 times in the “Uninstall an update” from the Programs and Features? I can confirm this in both production and development environments.

    Reply

    1. Hi John,
      4484232 is an Uber package for SharePoint Server which includes fixes (msp files) for all patchable components of SharePoint. In your case 41 of these included packages applied to your system.
      Rather than installing the Uber package you could have installed all these packages separately but that is very inconvenients. For that reason Microsoft provides these Uber packages to simplify your patching process.
      Cheers,
      Stefan

      Reply

      1. Thank you Stefan for the info.

        Reply

Leave a Reply to Stefan Goßner Cancel 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.