November 2023 CU for SharePoint Server 2016 is available for download

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

  • KB 5002517 – November 2023 Update for SharePoint Server 2016 (language independent)
    This is also a security update!
  • There was no language dependent fix released this month.
    The most recent language dependent fix is KB 5002501 from September 2023 CU.

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

Language independent fix: 16.0.5422.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:

16 Comments


  1. Hi,
    Our SharePoint 2016 farm is hosted on Windows Server 2012 that is not supported anymore by Microsoft.
    We are in migration phase to decommission servers before the end of this year.
    Do you think we can apply the latest patches without any risks? Or this is not recommended.
    Thanks.
    Best regards.

    Reply

    1. Hi Loic,

      the only thing would be the AMSI integration.
      You need to ensure that the feature stays disabled since September 2023 CU.

      Cheers,
      Stefan

      Reply

      1. Hi,
        Thanks for your answer, that means we could install any new SP16 patches even if the OS is not up-to-date, right?
        Regards.
        Loïc

        Reply

          1. Thanks.


  2. Hi Stefan,
    you write the most recent language dependent fix is August 2023 CU (KB 5002398). What about the language dependent fix in September 2023 Update (KB 5002501)? Or do I overlook anything?
    Best regards.

    Reply

    1. Hi Ingo,
      yes you are right – copy&paste error. Thanks a lot for the heads-up!
      Has been fixed now.
      Cheers,
      Stefan

      Reply

  3. Hi Stefan,

    As you suggested to install the Sept 2023 CU language dependent fix but, in the improvement and fixes section there is note that “To get the improvement, you have to install KB 5002494 together with this update.[ September 2023 Update for SharePoint Server 2016 (language independent)”

    so we need to install September2023 language independent update or just November Language independent is sufficient? or both?

    Nov 2023 CU:
    There was no language dependent fix released this November 2023 month.
    The most recent language dependent fix is KB 5002501 from September 2023 CU.

    Note from KB 5002501 from September 2023 CU:
    Note: To get the improvement, you have to install KB 5002494 together with this update.[ September 2023 Update for SharePoint Server 2016 (language independent)
    This is also a security update!]

    Reply

    1. Hi Praveen,
      SharePoint fixes are cumulative. November language independent package includes all fixes from the September language independent package.
      If you are installing the November language independent package there is no need to install the September language independent package.

      If you plan to install the November language independent package you need to ensure to have the September language dependent package as well but there is no need to install futher packages.

      Cheers,
      Stefan

      Reply

  4. Hi Stefan,

    After this update on my Windows 2016 server, my MicroFeedWebPart isn’t showing any content anymore. (multiple farms)
    Additionally, the “_api/social.feed/My/TimelineFeed” and “_api/social.feed/My/News” endpoints give errors stating that “The operation failed because the server could not access the distributed cache. Internal type name: Microsoft.Office.Server.Microfeed.MicrofeedException. Internal error code: 55.” (and 56 for the TimelineFeed)

    I’ve checked the Feedcache, and all seems fine.
    Distributed Cache: Online & AppFabricCachingService: UP

    In the ULS i found the same errors preceeded by a chain of exceptions regarding the Microfeed. Example:

    Microsoft.Office.Server.Microfeed.MicrofeedException: ServerErrorFetchingCategoricalFeed : ( Unexpected exception in FeedCacheService.GetCategoricalFeed: Unable to cast object of type ‘System.Collections.Generic.List1[System.Collections.Generic.KeyValuePair2[System.String,System.Object]]’ to type ‘System.Collections.Generic.IEnumerable1[System.Collections.Generic.KeyValuePair2[System.String,System.Byte[]]]’.. )

    Does this have to do with the Trending issue of the Distributed Cache problem that was fixed in August?

    If not, have you heard of any similar issues?
    Kind regards,
    Ruben Pillen

    Reply

    1. Hi Ruben,

      the trending issue fixed in August CU was about a different issue.

      I haven’t seen the issue you mentioned above.
      If you need assistance for this I would recommend to open a support ticket with Microsoft to get this investigated.

      Cheers,
      Stefan

      Reply

      1. After patching now multiple SP2016 environments with the november (and additonal december) cumulative update this reported issue seems to consistent on all systems. Is there already some research going on or is this still an unmonitored issue on microsofts side?

        Greetings,
        Oliver

        Reply

        1. Hi Oliver,

          I haven’t seen a support ticket for this – so most likely not an issue that is being investigated.

          Cheers,
          Stefan

          Reply

  5. Hi Stefan,
    Thanks for all your knowledge in your blog! On our sp2016 ent prod and test instances, we are seeing an SPUpgradeException being thrown when running psconfig.exe -cmd upgrade on featureid 4cf046f3-38c7-495f-a7da-a1292d32e8e9 despite disabling it. Am I missing something in disabling AMSI or is there something else beyond disabling that feature I should be doing?
    Best regards,
    Garrett

    Reply

    1. Hi Garrett,
      disabling a feature does not prevent it from being upgraded to the latest version when a patch is installed.
      I would suggest to open a ticket to analyze why upgrading this feature causes an exception in your environment.
      Cheers,
      Stefan

      Reply

Leave a 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.