The product group released the September 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 September 2024 CU will be available at the following location in a couple of hours:
- KB 5002640 – September 2024 Update for SharePoint Server Subscription Edition
This is also a security update!
The download for September 2024 CU is available through the following link:
- Download September 2024 Update for SharePoint Server Subscription Edition
This is also a security update!
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 September 2024 CU Build Number: 16.0.17928.20086
Important: To minimize the installation time for SharePoint Server Subscription Edition Fixes, please follow the guidance in the following article: Solving the extended install time for SPSE CUs
Related Links:
- Technet: 24H1 Feature Update for SharePoint Server Subscription Edition
- Technet: Updated Product Servicing Policy for SharePoint Server Subscription Edition
- Technet: FAQs for SharePoint Server Subscription Edition product servicing policy
- Blog: SharePoint Patching Best Practices
- Blog: SharePoint Patching demystified
- Blog: Why I prefer PSCONFIGUI.EXE over PSCONFIG.EXE
- Technet: Update Center for Microsoft Office, Office Servers, and Related Products
- Blog: SharePoint Server 2016 Zero-Downtime Patching Demystified (applies also to SharePoint Server 2019)
- Blog: SharePoint does not have a build version. Full Stop.
- Blog: Solving the extended install time for SPSE CUs
Permalink
On the June 2024 CU there was a “High CPU consumption” issue fixed, and that fix was caused by the September 2023 CU. Now in September 2024 CU there is another high CPU usage fix.
What is this one about? Does it mean the Sept2023 issue was not completely fix by the Jun2024? Or is this a distinct issue?
Permalink
Hi Andre,
this is a different issue.
Cheers,
Stefan
Permalink
I don’t see a fix for the upload from Office client JavaScript issue. Does anyone know if this has been fixed as well?
Permalink
Hi Martijn,
the issue has NOT been fixed in September CU.
The fix for the Javascript issue is planned to be included in October 2024 CU.
Cheers,
Stefan
Permalink
Hi Stefan,
After installing Sept 2024 CU, 2010 workflows stopped on our systems. On our test and PROD system as well.
Republish not working, “Unexpected error on server associating the workflow” Error were found when compiling the workflow.
Run fails with “Failed on Start”
2013 workflows running properly.
Permalink
Hi Zoltán,
please check the known issues section of September CU – it lists that issue including a workaround.
Cheers,
Stefan
Permalink
Hi Stefan,
I missed that information in the known issues section.
Thank you very much. It fixed our issue.
Permalink
Great! Thanks for the confirmation! 🙂
Permalink
Hi Stefan,
After installing September 2024 CU on different SharePoint versions (SE, 2019, 2016), we found issue with serialization of List of SafeControls on Classic WebPart.
In CU release notes, there is known issue for IDictionary types serialization, but is there a workaround for generic Lists?
Following error message can be found in ULS after navigating to page with classic webpart, which is not rendered.
‘Getting Error Message for Exception System.ArgumentException: The serialized data is invalid. —> Microsoft.SharePoint.ApplicationRuntime.SafeControls+UnsafeControlException: The control type ‘System.Collections.Generic.List
1[[Our.Custom.DLL.Formatting.ViewFieldData, Our.Custom.DLL, Version=1.0.0.0, Culture=neutral, PublicKeyToken=XXX]]' is not allowed on this page.at Microsoft.SharePoint.WebPartPages.SPSerializationBinder.IsAllowedType(Type type) .....
I’ve ensured that given type is registered as safe in SafeControls in web.config, and it worked on previous SP CU. Installation of latest Language pack patch did also not change anything.
I’ve found a workaround for rendering unsafe controls (changing ControlCompactMode to true in SafeMode in web config), but it’s a little not secure.
Best Regards,
Marcin
Permalink
Hi Marcin,
it might be that you are running into a side effect of one of the security fixes we released with August CU.
It prevents the usage of the SafeControls list in certain situations.
Please open a support case with Microsoft to ensure that we can investigate the issue and if required get guidance from the product group.
Cheers,
Stefan
Permalink
I’m running into the dreaded:
Error encountered when creating uri from baseUrl /_layouts/15/next/odspnext/
After applying the latest patch in my DEV environment, the Contents is blank. Oddly enough, for only one (the main) web application. It works fine in the others.
Just to be sure, since it is easy enough, I removed SharePoint from the front-ends and re-installed everything from scratch (SharePoint + Latest CU). But this did not fix the problem.
Normally, it is an incomplete patch (missing Language pack) but now we have a combined one. Anyone else running into this issue?
Permalink
Just a follow-up with solution (in case anyone else runs into this)
Since it was only affecting ONE web application, went down that path. Possible corrupt Web Application?
Created a new Web Application and added my root site (dismount / mount).
That worked!
Once I dismounted the rest of the databases and added them to the new Web Application, everything seems to be working on all site collections in the Web Application.