Fix-SeptemberCU-Permission-Problem.ps1
Alternatively you can also remove the NT Authority\system account from WSS_WPG and IIS_IUSRS local security groups of the SharePoint machines.
For more details check this article: Trending Issue: SharePoint fixes fail to install after installation of September 2025 CU
The product group released the May 2026 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 May 2026 CU will be available at the following location in a couple of hours:
- KB 5002863 – May 2026 Update for SharePoint Server Subscription Edition
This is also a security update!
The download for May 2026 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 May 2026 CU Build Number: 16.0.19725.20280
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:
- Learn: Updated Product Servicing Policy for SharePoint Server Subscription Edition
- Learn: 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
- Learn: SharePoint Updates
- 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
Still no product updates…?
Permalink
Hi John, hat Do you mean by product Update?
Permalink
He probably means “Feature Update”, like 26H1, with some new contents & features. I was also waiting for this kind of update this month.
Permalink
Talking about a Feature Update included in the CU 🙂
I think some of us understood (or misunderstood) that there will be one CU + Feature Update every 6 months and that maybe some of them are required to servers under MS support.
Permalink
Hi Nico,
yes, I understand. Historically it was always March and September.
Be aware that the expected sequence of feature updates is outlined in this article:
https://learn.microsoft.com/en-us/sharepoint/product-servicing-policy/faq/faq-subscription-edition#how-are-feature-updates-different-from-pus
“New feature experiences are bundled together in Feature Updates, which will be released twice a year (once in the spring and once in the autumn).”
A specific month was not communicated.
The current plan is to release the next feature update with June CU.
Cheers,
Stefan
Permalink
Thanks a lot Stefan ! 👍
Permalink
Do farms in SPSE July 2025 need to run the Fix-SeptemberCU-Permission-Problem.ps1? Or can we patch directly to May 2026?
Permalink
Hi Carlos, you can directly go to May 2026 CU.
Cheers,
Stefan
Permalink
Hi Stefan,
I just installed the current patch on our SPSE prod system where I had some issues which I wanted to let you know (on our test system everything went well). So I installed the binaries which was as usual and worked. Then I upgraded the content DBs which took longer than normal (especially for one DB). After this was finished I ran the psconfig wizard and I had on all server the same error: “Atempting to register null pointer at: .”
In the CA the server was register with “no action required” and everything was working as usual (I had to start the pools manuelly because the wizard did not do it). So beacause I don’t know wheater this is an error related to our farm (never had this error before) or from the current patch. To be sure I opend a case with Microsoft support to get this checked out – don’t want this on our next upgrade.
Let me know if I should send you the case number, so you can check this out too.
BR Alex
Permalink
Hi Alex,
yes, please send me your SR number using “Contact the Blog author” at the top right.
Cheers,
Stefan
Permalink
Hi Alex, I know its a little off-topic, but how did you manage to open the case with Microsoft Support? My customer has Sharepoint Standard SPSE CAL LSA OLV which includes software assurance (3 year contract), and Microsoft said through the reseller that CU related issues are “installation related” and that they need to buy a $499.00 per incident support.
Permalink
Hi Carlos,
we are a company with a four-digit number of employees and therefore we have unified enterprise support through Microsoft (not via a third party provider). We therefore have the possibility to open Microsoft cases on any issues / questions we have and Microsoft tools we are using. I hope that answers your question.
BR Alex
Permalink
Yes, It does. Thanks for the response!
Permalink
Hi Stefan!
I installed SPSE and the April update earlier this month & ran the configuration wizard for the App servers. (This is a new farm without a content DB yet). Later, the service account permissions were granted for the services. Last week, I installed the May update and got an error during Config that the April Language Pack is missing. How do I install the April Language Pack? When I tried to re-run the April uber install, it says it’s already installed. (I have a support ticket with Microsoft, but they seemed to be swamped.)
Thank you in advance!
Marlene
Permalink
I followed the article below, ran the Get-SProduct -local and that fixed it. https://www.sharepointdiary.com/2014/10/some-farm-products-and-patches-were-not-detected-on-this-or-other-servers.html
Permalink
I ran with same issue a while ago. In my case, I reinstalled the language pack and selected repair. Reboot and it worked. https://www.microsoft.com/en-us/download/details.aspx?id=103600
Permalink
Yes – that was my assumption that the info that the fix was installed did not get populated into the ServerVersionInformation table in the Config DB.
The command you listed fixes this.
Cheers,
Stefan
Permalink
I installed the May 2026 CU on 14 SharePoint farms. So far, I have experienced two issues a few times. The issues usually appeared a few days later, after the Windows Servers were restarted.
1️⃣ At least 5 farms had Search Service Application in error state. Search Administration showed “Searchable items: All Errors” and “Search Application Topology: Unable to retrieve topology component health states.”
➡️ After restarting the “SharePoint Search Host Controller” and waiting about a minute, Search worked again.
2️⃣ On at least 2 farms the SharePoint Website response time changed from 0.3 seconds to exactly 80 seconds (which resulted in some timeouts).
➡️ After running PSConfig again, the issue was resolved.
Hope this helps someone else.
Cheers from 🇨🇭,
Benjamin
Permalink
Hello Benjamin!
Thank you for this comment. We have reproduced the issue with search in our SP2019 test environment. I posted a comment about this under the article related to the SP2019 May CU. Interestingly, after a reboot and restarting the SharePoint Search Host Controller, the next reboot caused the issue to return.
Regards,
Zaneta
Permalink
Hi Benjamin,
Thanks for sharing your experience – very helpful.
Quick question: were all those 14 farms running SharePoint Server Subscription Edition (SPSE), or was it a mix of versions? I’m currently running the May 2026 CU on 4 SPSE farms, and so far I haven’t seen any issues with the Search service, even after server restarts.
Interestingly, I’ve only encountered similar problems on SharePoint Server 2019 with the May 2026 CU.
Would be great to understand if your issues were specific to SPSE or affected other versions as well.
Thanks!
Permalink
Hi Benjamin,
Never mind my previous comment – I’m joining the club 🙂 One of my farms has now broken as well, and the symptoms look very similar to what I’ve seen on SP2019 with the May 2026 CU.
Permalink
Just had a second farm get hit by this also.
Permalink
Thanks for the heads up Ben! I had this happen on one of our Windows Server 2022 farms.
Permalink
For me, I had a duplicate and broken search service proxy.
I had to re-create the search service and proxy a long time ago when it got corrupted, I must created a duplicate or the old one did not get cleaned up.
Once a duplicate search service proxy deleted and rebooted, it came back to normal.
Permalink
Hi Stefan,
I have installed May 2026 CU in SPSE farm. I am facing issue with documents. Somehow documents which are uploaded in SharePoint are in Read-only state. On the local machine, we can edit the files but on sharepoint its showing in readonly state.
Can you please help me on this.
Thanks a lot !
Ganesh P.
Permalink
Hi Ganesh,
on SharePoint? What do you mean?
In Office Online Server?
Sorry – I don’t understand where in SharePoint “read-only” would show up.
Cheers,
Stefan
Permalink
Hi Stefan, good morning !
Inside site collection, under document librarys, whatever files we are uploading all of them are showing in read only state. But whenever, that document is downloaded, opened on local machine we can edit the files. On sharepoint site, its in read only state. site is not read only but the files like excel, word, ppt are in read only state.
Thanks !
Permalink
Hi Ganesh,
I would suggest to open a ticket with Microsoft to get this analyzed.
Cheers,
Stefan