The product group released the May 2023 Cumulative Update for SharePoint Server Subscription Edition.
Starting with March 2023 CU, Microsoft releases cumulative updates for SharePoint Server Subscription edition as a unified “uber” package containing both the language independent and language dependent fixes. Language independent and language dependent fixes will no longer be released separately.
Going forward it will be sufficient to install one single package to fully patch a SharePoint Server Subscription Edition server. This is similar to the full server packages released for SharePoint 2013.
The KB article for May 2023 CU will be available at the following location in a couple of hours:
- KB 5002390 – May 2023 Update for SharePoint Server Subscription Edition
This is also a security update!
The download for May 2023 CU is available through the following link:
- Download May 2023 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 May 2023 CU Build Number: 16.0.16130.20420
- Technet: 23H1 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.
Did May Patch broke Distributed Cache? Unable to join DCS Role server to existing farm (Getting error – Cache host is null exception.) Also, will there be fix for IIS site IP/Cert binding removal when modifying web application authentication for SPSE?
so far we have not received any reports about such an issue.
Actually May CU contains fixes for Distributed Cache issues introduced in January 2023 CU.
If you need assistance to get this analyzed I would recommend to open a support case.
I’m not aware of a problem with IP/Cert binding removal in SPSE – except if you did not use the correct steps to configure them in the first place.
Unlike earlier SharePoint Versions SPSE supports configuring these settings in central admin. Manual updates to the web.config will be cleaned-up on reprovisioning of the web application.
Please verify if you followed the correct steps:
Hello, are there any knows issues with this patch? Farm solutions / wsp files need now 10 – 15 min to be deployed. We installed the CU yesterday on our development environment and before the CU everything worked normal, like 1 min to deploy a solution as it always was.
I tried the same solution in our staging farm, which still runs the April CU and there we have no issues.
this is not a known issue. I would recommend to open a ticket with Microsoft Support to get this analyzed.
thanks for the quick reply. Tried already the usual, server reboot, Timer Service restart and iisreset without success. Guess we try next our staging farm, if there we have the same issues, we open a ticket.
We installed the CU now on our staging farm and have the same problem as on the development farm. Before the CU the deployment of wsp files worked fine, now deployment takes 10 – 15 min on a 2 server farm. Application pools stop all the time and need to be started manually over this 10 – 15 min.
We will create a ticket at Microsoft support.
Please check here:
thanks, we were one of the companies which reported the issue yesterday (I think it got forwarded to you) and we got the solution today in the morning :).
We testet it already and it works, thanks.
Still unexpected because it worked for so long.
But you are doing a great job of keeping people informed, especially for On-Premise were information is kind of scarce!
indeed I was involved in your case. 🙂
Hello, this is general question. We noticed that the installation time of the update got significantly longer with Subscription Edition in comparison to 2019.
2019 with Core and Language Updates needs ~15 Minutes per Server
Subscription Edition needs ~45 Minutes per Server.
Is this just us or did anyone else notice this?
Thank you very much
yes, unfortunately I noticed that.