The product group released the February 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 February 2024 CU will be available at the following location in a couple of hours:
- KB 5002560 – February 2024 Update for SharePoint Server Subscription Edition
The download for February 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 February 2024 CU Build Number: 16.0.16731.20526
Related Links:
- Technet: 23H2 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.
Permalink
Hi Stefan,
We updated our SharePoint Farm to February 2024 CU and we noticed to major problems for us:
1. For some reason, Display templates won’t load custom css files for anonymous users (even though its published correctly)
2. Pages load extremely slow on updated servers. It seems like the page waits for all items to load and then shows up (Anonymous and authenticated)
We’re opening a ticket for those with hope we’ll find a solution as we found about it in production.
Permalink
We’ve opened a ticket and after some investigation we found that it’s a bug in this (or older) version of some OOB JS files (specifically init.js) which has and issue while loading in anonymous context.
It’s currently being investigated by the product group.
I’ll let you know once we have an update about this
Permalink
Any update on this issue? Are you able to work with Microsoft to resolve this issue? We are planning to update our SP SE servers with Feb 2024 CU. Thanks.
Permalink
Hi,
We’ve got an update that this issue was probably fixed by March 2024 CU.
We still haven’t tested it yet.
We’ll test it soon on lower environments and post an update.
Permalink
Tnx for it!
Permalink
Hello Stefan,
we installed cu February 2024 sharepoint SE. We have many users who are no longer able to access the sites they are tracking. /_layouts/15/sharepoint.aspx
An authentication pop-up constantly appears which prevents access to tracked sites. This page remains empty: https://partage-fichiers.inrae.fr/_layouts/15/sharepoint.aspx?v=following with the authentication pop.
Thank you in advance
Permalink
Hi Lavergne,
I would recommend to open a support case to ensure that this can be analyzed in more detail.
Cheers,
Stefan
Permalink
Hi Stefan ,
We just rolled out Feb 2024 CU for SharePoint subscription Edition, we have multiple Environments (Dev, Test & Prod), we noticed multiple issues
First: while installing patch for some servers it showed one KB’s only and had to re-run the. Exe to get bot KB’s applied
Second: Even patch installed Successfully and Verified through installed updates still you see “Missing/Required “and had to run Get-SPProduct –local
Third (Major issue): we run command for Psconfig
PSConfig.exe -cmd upgrade -inplace b2b -wait -cmd applicationcontent -install -cmd installfeatures -cmd secureresources -cmd services -install
We noticed SPSE not respecting the “Wait ” switch, not locking or releasing lock on time and multiple servers it seems just Hanging for hours, we had to Kill the process and re-run without “Wait ” Switch. Not consistent though we didn’t notice this in Dev Environment but caught in Test Environment, so we ran Without Wait Switch one server at a time in Prod (if we Kill the process and run second time first process might be doing Rollback and second process doing commit might put databases in bad State)
is this Reported issue already or there is more investigation going on ?
Permalink
Hi Mohan,
from what I know this has not been reported before and I have not seen this behavior in any of my environments.
Cheers,
Stefan
Permalink
Hi Stefan,
We have a dev environment at the February 2024 CU level with a “16.0.16731.20518” config database version. We set up a new environment and applied the same patch, but the version is “16.0.16731.20452”. What causes that minor difference? We can’t move the site backup from dev to the new environment because of the difference. We got the error below.
Restore-SPSite : Version string portion was too short or too long.
Do you have a suggestion to bring the farms to the same version level?
Permalink
Hi Murat,
16.0.16731.20452 is from Jan CU. 16.0.16731.20518 is from Feb CU.
It looks as if the database schema was upgraded.
Cheers,
Stefan