March 2024 CU for SharePoint Server Subscription Edition is available for download

The product group released the March 2024 Cumulative Update for SharePoint Server Subscription Edition.

Monthly SharePoint Server Subscription edition updates are released as a single unified “uber” package containing both the language independent and language dependent fixes. Language independent and language dependent fixes will no longer be released separately. This is similar to the full server packages released for SharePoint 2013.

The KB article for March 2024 CU will be available at the following location in a couple of hours:

  • KB 5002564 – March 2024 Update for SharePoint Server Subscription Edition
    This is also a security update!

The download for March 2024 CU is available through the following link:

It is irrelevant which language you pick on the drop down in download center. It will always download the same package.

After installing the fix you need to run the SharePoint 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.

Please ensure to have a look at the SharePoint Patching Best Practices before applying new fixes.
SharePoint Server Subscription Edition March 2024 CU Build Number: 16.0.17328.20136

Related Links:


  1. After Updating the First FronEnd Server (via Install-SPSE_Fix.ps1 ) we get the following Error. There was only a Directory “C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Microsoft.Owin\v4.0_4.2.2.0__31bf3856ad364e35”.
    So we copied the v4.0_3.0.1.0__31bf3856ad364e35 Folder from a different Machine
    and it works fine. The Web.Conf reference the wrong dll. Mayby after SPConf everything Works? But there is no Zero Downtime patching with this Error.

    Exception information:
    Exception type: FileNotFoundException
    Exception message: Could not load file or assembly ‘Microsoft.Owin, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ or one of its dependencies. The system cannot find the file specified.
    at Microsoft.Owin.Host.SystemWeb.OwinAppContext.Initialize(Action1 startup)
    at Microsoft.Owin.Host.SystemWeb.OwinBuilder.Build(Action1 startup)
    at Microsoft.Owin.Host.SystemWeb.OwinHttpModule.InitializeBlueprint()
    at System.Threading.LazyInitializer.EnsureInitializedCore[T](T& target, Boolean& initialized, Object& syncLock, Func`1 valueFactory)
    at Microsoft.Owin.Host.SystemWeb.OwinHttpModule.Init(HttpApplication context)
    at System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers)
    at System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context)
    at System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context)
    at System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext)


    1. Hi Andreas,
      yes – this has been identified as a known issue in this update. An update for the KB article is currently in the works.
      Solution is to run the SharePoint configuration wizard – it will add the required changes to the web.config.


  2. Same issue here with CU March

    The workaround I found is to replace the version numbers in following section in the web.config:
    find section in web.config



    After doing this, the Web Application and/or Central Admin site is working again.
    And you can bring the server online again and continue with ZDP


    1. Hi Richard,
      yes, thats the workaround we proposed to the product group to support zero-downtime-patching.
      The workaround is currently being evaluated to understand if the upgrader still performs all actions when running psconfig later.
      There is a small chance that the upgrader exits early and does not perform futher required upgrades.
      For now this workaround should not be performed in a production environment till approval has been given by the product group.

      The easiest way to resolve this issue is to run the SharePoint Configuration Wizard after the installation of the fixes.
      It will perform the required changes in the web.config.



      1. Hi Stefan,

        Thanks, good to know we can still patch this CU with ZDP with this workaround.

        Best Regards,


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.