July 2024 CU for SharePoint Server 2016 is available for download

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

  • KB 5002618 – July 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.
    If this is not yet installed on your Farm, you need to install it together with the language independent fix.

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

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

6 Comments


  1. Hi Stefan,

    We are facing an issue after installation of July 2024 CU in a SharePoint 2016 environment. So far we have installed CU in the Test environment. We are not proceeding with installation in the Production environment because of the issue.
    Before the installation we had June 2024 CU in place.

    Perhaps you can help with it. Maybe something is wrong with the CU package.

    Web Application “web.config” file has changed after the CU installation. Specifically, one line has changed:

    The attribute “Safe” was set to “True” before July 2024 CU. After CU installation the attribute value became “False”.
    It is the only change in the “web.config” file.

    This change appears to be affecting Site Collection creation via PowerShell / code.

    Sample script:

    $webApp = Get-SPWebApplication “{WebAppUrl}”
    $db = $webApp.ContentDatabases[[GUID]”{DB_GUID}”]

    $db.Sites.Add(“/sites/SiteCollection1”, {AccountName}, {EMail})

    Site Collection creation is failing with the following errors:

    1) In PowerShell:

    Exception calling “Add” with “3” argument(s): “This page has encountered a critical error. Contact your system administrator if this problem persists.”

    2) In SharePoint Logs:

    Error: Failure in loading assembly: Microsoft.SharePoint.ApplicationPages, Version=16.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c
    Safe mode did not start successfully. Microsoft.SharePoint.WebPartPages.WebPartPageUserException: This page has encountered a critical error. Contact your system administrator if this problem persists.
    at Microsoft.SharePoint.ApplicationRuntime.SafeControlsList.InitSafeControlsInfoFromConfig(Boolean inNonVRootAppDomain, SafeControlsContainer safeControlsContainer, SPWebApplication app, SPUrlZone zone)
    at Microsoft.SharePoint.ApplicationRuntime.SafeControlsList..ctor(SPWebApplication app, SPUrlZone zone)
    at Microsoft.SharePoint.ApplicationRuntime.SafeControls..ctor(SPWebApplication app, SPUrlZone zone)
    Error importing WebPart. Assembly Microsoft.SharePoint.Portal, Version=16.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c, TypeName. Microsoft.SharePoint.Portal.WebControls.ContactFieldControl. This page has encountered a critical error. Contact your system administrator if this problem persists.

    https://{WebAppURL}/sites/SiteCollection1/_catalogs/masterpage/TabViewPageLayout.aspx – An unexpected error has been encountered in this Web Part. Error: This page has encountered a critical error. Contact your system administrator if this problem persists.

    Note that a Site Collection can be created in the same Database via Central Admin UI. But it is failing via PowerShell / code.
    We have custom solution where Site Collections are automatically getting created via code. So, our custom solution is now failing – Site Collections cannot be created.

    We have tried to manually change the value of the attribute “Safe” to “True” in the above mentioned “web.config” line – then Site Collection creation starts to work as expected. But we do not consider it a permanent solution – we did it only for a test.

    Is the above issue something that may be CU related?

    We observed another strange behavior during the Configuration Wizard after CU installation. In all the previous CU update instances the Configuration Wizard completed without issues.
    But after July 2024 CU there were hundreds of warnings for many Databases in the Upgrade Log file (no errors, though). Perhaps it is also somehow related?

    Here is an example of the warning:

    WebPart class [9a8d6fd1-1df5-5af8-3ed4-08962d6091eb] (class [Microsoft.Office.Server.Search.WebControls.ContentBySearchWebPart] from assembly [Microsoft.Office.Server.Search, Version=16.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [12] times in the database [{DatabaseName}], but is not installed on the current farm. Please install any feature/solution which contains this web part.

    Tests in UI of our solutions haven’t revealed any issues yet – all web parts (both standard and custom) are working as expected.

    Thank you in advance!

    Regards,
    Martins Grube

    Reply

    1. Hi Martins,

      please open a support case to allow us to investigate this issue.

      Cheers,
      Stefan

      Reply

  2. I see that my attempts of formatting the above message have been removed. Also the “web.config” line is removed.

    This is the “web.config” line I was writing about – I removed few symbols – hopefully it will be kept when I add this comment:
    SafeControl Assembly=”Microsoft.SharePoint.ApplicationPages, Version=16.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” Namespace=”Microsoft.SharePoint.ApplicationPages” TypeName=”SPThemes” Safe=”False” AllowRemoteDesigner=”False” SafeAgainstScript=”False”

    If there is another way to provide you information (which would retain formatting), then I could use it as well.

    Reply

  3. When applying the patch for SharePoint 2026 on prem, the test of the content databases reports a lot of missing web parts.
    Has anyone else got this issue?

    Reply

    1. Hi Kjell,

      The same here. I have mentioned it also in my comment above from July 11 (towards the end of it).

      Regards,
      Martins Grube

      Reply

    2. Hi Kjell,

      please open a ticket with Microsoft Support on this to ensure that this gets investigated.

      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.