December 2021 CU for SharePoint 2013 product family is available for download

The product group released the December 2021 Cumulative Update for the SharePoint 2013 product family.

For December 2021 CU we have full server packages (also known as Uber packages) for all products. No other CU is required to fully patch SharePoint.

As this is a common question: Yes, December 2021 CU includes all fixes from December 2021 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 December 2021 CU should be available at the following locations in a couple of hours:

  • KB 5002066 – SharePoint Foundation 2013 December 2021 CU
  • KB 5002070 – SharePoint Server 2013 December 2021 CU
  • KB 5002067 – Project Server 2013 December 2021 CU
  • KB 5002103 – Office Web Apps Server 2013 December 2021 CU

The Full Server Packages for December 2021 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.

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

Related Info:

8 Comments


  1. content deployment job fails if content deployment configuration has temporary folder store in non-system drives.
    $farm=Get-SPFarm
    $farm.AllowedContentDeploymentTempFolderDirectories=”E:\” # specify driver label which store the tempory folder
    $farm.update()

    Reply

    1. Thanks! This solved my issue 🙂

      Reply

  2. HI Stefan,

    After applying the Dec 2021 CU for SPS2013, the version number in Central admin is 15.0.5399.1000, not the number 15.0.5407.1000 mentioned in KB, it is reproduced in multiple farms.

    Reply

  3. I know Microsoft will sunset SharePoint 2013 on 4/11/2023. We are in the process of moving our sites from SharePoint 2013 to SharePoint online but there are couple sites that may still be on SharePoint 2013 until early May of 2023. Will Microsoft release one more CU for Sharepoint on 4/11/2023?

    Reply

    1. Hi Nathaniel,
      sorry – I don’t have this information at this moment.
      Cheers,
      Stefan

      Reply

  4. Dear Stefan,

    Do you if someone has detected this error with the content deployments after the installation of this CU? Just after installing it, they have started failing with this error:

    Content deployment job ‘JobName’ failed.The exception thrown was ‘Microsoft.SharePoint.Publishing.Administration.ContentDeploymentException’ : ‘The content deployment temporary folder ‘[non default location]’ is not in allowed directory list or is in virtual directory of a web application.’

    Maybe some of the security improvements of this patch may have this side effect?

    Thanks!

    Reply

  5. Is anyone noticing this behaviour?
    We use Sharepoint 2013 with a document library with versioning enabled, and files are edited in this library (e.g by Word). Ever since this update we notice that files that open “Read Only” in Word are getting a new version, although we don’t hit the “Edit this document” button. Looks like the new version is created once the document information panel has loaded.
    We are using this solution for many years now, but behaviour has changed since last CU december 2021 update.

    Reply

Leave a Reply to Stefan Goßner Cancel reply

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