July 2022 CU for SharePoint Server 2016 is available for download

The product group released the July 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 July 2022 CU should be available at the following locations in a couple of hours:

  • KB 5002231 – July 2022 Update for SharePoint Server 2016 (language independent)
  • There was no language dependent fix released this month.
    The most recent language dependent fix is KB 5002118 from January 2022 CU.

The downloads for July 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 July 2022 CU Build Numbers:

Language independent fix: 16.0.5344.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. Hi Stefan,

    Can we expect a July 2022 CU for SharePoint 2013? The latest update available for SP 2013 is June 2022 CU


    1. Hi Arul, there is no fix for SP2013 in July 2022.


  2. Hello Stefan,

    what about July 2022 CU for SharePoint Server 2013? No CU this month?

    Thanks and best regards


    1. Correct. No CU this month.


  3. Hi Stefan,

    General question for SharePoint patching, can we do the SharePoint patch installation through Microsoft SCCM push option? Right now we are following the Manually format so to automate I am asking this question.


    1. Hi Prabhu, I’m not an SCCM expert but from my experience SCCM only installs security fixes automatically. For non security fixes additional work is required to register them. I don’t have all the details but maybe someone from the community can answer the question in more detail.


  4. Hi Stefan,

    Do we have any July 2022 security updates for Office Online Server?


    1. Hi Nixon, there were no (security) fixes released for Office Online Server in July.


  5. We patched and updated our site to use https. The next day we deployed a master page update, javascript and css references were stripped on html to master conversion. Is this something that has been noticed with this months patching – or a general side effect that has been seen before?


  6. Hi Stefan,

    I am new in SharePoint patching. I have not patched our SharePoint server 2016 since January of this year 2022. Our last successful patch was October 2021. Will there be an issue if I patch our server with this latest Security update July 2022 CU?


    1. Hi Raymund, ensure to apply the language dependent fix from January 2022 (KB 5002118) and the language independent from July 2022 CU (KB 5002231)


  7. Hi Stefan,
    We do install patches every month and run the upgrade script also.
    Is it okay if we run upgrade script only once in 3 months but install patches every month?


    1. Hi Amien,

      do you mean to run the config wizard only evey 3 month?
      It is recommended to run this as soon as possible after applying the patches – otherwise fixes for the database schema will not be applied.
      Also the config wizard does a lot of operations.
      If the config wizard is delays should at least run install-spapplicationcontent cmdlet on each server to ensure that updated binaries are copied into the correct directories.
      Without this you will have a mix of binaries which is unsupported and can cause serious problems.



      1. Thank you Stefan. This is helpful.


  8. Hi Stefan ,

    We installed SP 2013 June CU update. But post that all our High Trust provider hosted apps and web services communicating with SP started giving 401 Unauthorized error ? Does anybody face similar issue ? Do we have any further SP 2013 updates that will fix this issue.

    Any information is highly appreciated.

    Thanks !


Leave a Reply to Stephen Jackshaw 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.