July 2021 CU for SharePoint Server 2016 is available for download

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

  • KB 5001976 – July 2021 Update for SharePoint Server 2016 (language independent) – This is also a security update!
  • KB 5001981 – July 2021 Update for SharePoint Server 2016 (language dependent) – This is also a security update!

The download for July 2021 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 July 2021 CU Build Numbers:

Language independent fix: 16.0.5188.1000
Language dependent fix: 16.0.5188.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:

9 Comments


  1. Hi Stefan,

    Any open issues there in July CU 2021?

    Reply

    1. Hi TK,
      this is not something that will be “fixed”. This is the new behavior introduced by a security fix.
      Please follow the guidance in the article you quoted on how to resolve issues that occur after applying the fix.
      Cheers,
      Stefan

      Reply

      1. Seriously? It broke workflows and it won’t be fixed? What are we left to do?

        Reply

        1. Hi Janet,
          it will not break SharePoint 2010 out of the box workflows.
          But for each custom action created and included through custom assemblies which uses additional data types you need to explicitly enable them following the KB article.
          Cheers,
          Stefan

          Reply

  2. For Test everything went fine but for prod I have the same issue like described in comment below this article, any ideas for solution ?

    https://blog.stefan-gossner.com/2017/11/14/november-2017-cu-for-sharepoint-server-2016-is-available-for-download/

    “(…)
    The config wizard has been running for well over 15 hours and is still at 10% complete, with no real errors within the log file. High level messages are like:
    Entering monitored scope: (Fetch object from file system: Fetching object [7b7cbc85…
    Deserializing the type named….
    refreshed SPPersistedObject with Name Upgrade-20171205-105443….
    Leaving Monitored Scope
    ….
    ULS Init completed

    The entering monitored scope fetching object is the same number throughout the log file, but there are no errors.
    Any ideas as to why this would continue to be sitting at 9 of 10 and at 10% complete?
    (…)”

    Reply

  3. Hi Stefan, Have you receive any information about this patch that may cause Search failure. After applying this patch, our Search failed with a correlation id. The query process would go into suspend mode when looking at the task manager. The failures occur about every 8-10hrs and restart of the Search controller service would bring Search back online.

    -Thanks.

    Reply

  4. Hi Stefan,
    we have the problem after the CU update that some SharePoint servers get the status Upgrade Required again and again. We have already run the PSConfig via Powershell. Is there a known bug or what else could be tried?

    Reply

    1. Hi Nikolaus,
      this is not a known symptom for this CU.
      If you cannot resolve the issue yourself I would recommend to open a support ticket with Microsoft to get this analyzed.
      Cheers,
      Stefan

      Reply

Leave a Reply to Janet Cancel reply

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