November 2022 CU for SharePoint Server 2016 is available for download

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

  • KB 5002305 – November 2022 Update for SharePoint Server 2016 (language independent)
    This is also a security update!
  • KB 5002289 – November 2022 Update for SharePoint Server 2016 (language dependent)
    This is also a security update!

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

Language independent fix: 16.0.5369.1000
Language dependent fix: 16.0.5369.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:

11 Comments


  1. Any issues with SharePoint Server 2016 November CU’s identified so far.

    Reply

  2. Hi All,

    Any issues identified so for SharePoint 2016 Nov 2022 CU’s

    Thanks,
    Arshad

    Reply

    1. Hi
      not sure. We had issues in some farms after October CU security changes for the farm account. One farm failed with November CU today. Reason was that farm account did not have dbo permissions on SharePoint_Config database anymore and this made the upgrade job stuck at 10%. But the lacking dbo permissions I cound not verify on other farms. Better check before upgrading.
      Regards
      Christoph

      Reply

      1. Thanks for the update, actually we have patched our servers with AUG 2022 cu last time, and planing to patch Oct 2022 cu’s but I saw some issues with Oct 2022 cu’s.so decided to plan Nov 2022.we will test in lower environment first and see,any possibility to rollback cu’s once it is installed?

        Reply

        1. only via SQL backup and snapshots of the SharePoint servers (taken while they are down).

          Reply

        2. As outlined by Christoph – only through cold snapshots and with SQL backups.

          Reply

      2. Hi Christoph,
        I reached out to the relevant Program Manager and got the information that this behavior is not intentional.
        If you have ULS/Upgrade logs when installing October CU or if you skipped it from November CU it would be great if you could open a support case to ensure that this can be analyzed in more detail.
        Thanks,
        Stefan

        Reply

        1. Hi
          sorry. Did not see this earlier. I do not have the logs anymore, so I cannot give further information. But in the comments section to November CU there are other statements pointing into this direction.
          Regards
          Christoph

          Reply

  3. After the successful installation of the two binaries and the execution of the PSCONFIGGUI, I am getting this
    Configuration database version: 16.0.5368.1000
    Instead of 5369, it is showing up as 5368.
    Is that ok?
    My farm is running fine with no errors reported in the logs.

    Reply

  4. We have come across an issue after patching with Nov CU. 2010 workflows which were added after patching have a pause condition for 5 minutes. workflows are stuck in that state and don’t move to next step. ULS logs did not show any error related to this. I created a different wf with same condition and it works. Any insights on this?

    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.