January 2024 CU for SharePoint Server 2016 is available for download

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

  • KB 5002541 – January 2024 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 5002524 from December 2023 CU.

The downloads for January 2024 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 January 2024 CU Build Numbers:

Language independent fix: 16.0.5430.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. If the December updates haven’t been applied, can I applied the January STS update and the December WSS update. Or do I need to do both December updates first, then the January STS update?

    Reply

    1. Hi David,
      SharePoint fixes are cumulative. That means January CU includes all fixes from previous CUs.
      Installing the latest one will be sufficient.
      Cheers,
      Stefan

      Reply

  2. Hi Stefan, any reports of this patch breaking IIS on web and app servers?
    I get this after patching my environments and no idea how to troubleshoot further

    Server Error
    500 – Internal server error.
    There is a problem with the resource you are looking for, and it cannot be displayed

    if i try to launch from the server itself

    The requested page cannot be accessed because the related configuration data for the page is invalid.Detailed Error Information:
    Module IIS Web Core
    Notification Unknown
    Handler Not yet determined
    Error Code 0x80070032
    Config Error Cannot read configuration file because it exceeds the maximum file size
    Config File \?\C:\inetpub\wwwroot\wss\VirtualDirectories\45110\web.config

    i checked the reg key MaxWebConfigFileSizeInKB and it is correct

    Reply

  3. Hi Stefan,

    Is there, any know issue with January 2024 CU for SharePoint Server 2016?

    We are planning to install it in our SP 2016 environment.

    Thank you,
    Deepak Singh

    Reply

    1. Hi Deepak,
      so far we have not seen any feedback for new issues with this CU.
      Cheers,
      Stefan

      Reply

      1. Thanks, Stefan for update.

        Reply

  4. Hi Stefan,

    We have installed January 2024 CU for SharePoint Server 2016 for one of the application got effected and trowing error ‘The property or field has not been initialized. It has not been requested or the request has not been executed. It may need to be explicitly requested’ for custom master page, Can you please suggest is there any alternate solution?

    Reply

    1. Hi Prasad,
      it would be required to analyze the custom master page and the properties or fields being used here to understand what fails.
      As this is a custom masterpage you should involve the developer of this masterpage to investigate the issue.
      Cheers,
      Stefan

      Reply

    2. Thank for your response Stefan, but there are different webapplication and giving different errors with different solutions with this CU so realy stuck with the clueless.

      Reply

      1. Hi Prasad,
        if you need assistance to get this analyzed I would recommend to open a ticket with Microsoft support.
        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.