Important: A problem with this CU has been identied: Upgrading databases from January 2026 CU to March 2026 CU will fail!
It is important to install February 2026 CU and upgrade the content databases using the Configuration Wizard before installing March CU.
See here for more details:
Important: If your current farm patch level is September 2025 CU, remove the NT Authority\system account from WSS_WPG and IIS_IUSRS local security groups of the SharePoint machines – otherwise installing the SharePoint fixes will fail.
For more details check this article: Trending Issue: SharePoint fixes fail to install after installation of September 2025 CU
The product group released the March 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 March 2026 CU will be available at the following location in a couple of hours:
- KB 5002843 – March 2026 Update for SharePoint Server Subscription Edition
This is also a security update!
The download for March 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 March 2026 CU Build Number: 16.0.19725.20076
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: 25H1 Feature Update for SharePoint Server Subscription Edition
- 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
- 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
Hi Stefan! So this time March release is not a feature update…correct?
Permalink
Hi Frederik,
this is correct. March CU is not a feature update.
Cheers,
Stefan
Permalink
Is there any information why this CU does not include a 26H1 feature update?
Permalink
Hi Christian,
there is no fixed month for a feature update.
It is in most cases March or September but can be any other month as well.
For more details:
https://learn.microsoft.com/en-us/sharepoint/product-servicing-policy/faq/faq-subscription-edition
“…Feature Updates, which will be released twice a year (once in the spring and once in the autumn)”
Cheers,
Stefan
Permalink
Stefan, I’m upgrading from the January 2026 patch and psconfig is throwing a SQL exception during the upgrade sequence: An exception of type Microsoft.Data.SqlClient.SqlException was thrown. Additional exception information: Invalid column name ‘SAFE_NOTIFICATION_DATA’. Has this issue come across your radar? I can reproduce it by running Upgrade-SPContentDatabase on any content database in my farm.
Permalink
Hi Christian,
this seems to be a project server related column. I have not heard or seen this issue – but Project Server is supported by a different team than SharePoint.
My suggestion would be to open a support case with Microsoft to ensure this is investigated.
Cheers,
Stefan
Permalink
Hi Stefan,
We’re also seeing the SAFE_NOTIFICATION_DATA SQL exception during psconfig/Upgrade‑SPContentDatabase on SharePoint Server Subscription Edition after updating to the March 2026 CU (farm previously on January 2026 CU). We don’t use Project Server and have:
No Project Server Service Applications, Proxies, or WSP solutions in the farm.
All content DBs report HasExternalProjectData = False.
Test‑SPContentDatabase shows no MissingFeature or Project‑related issues.
However, in the config database the following Project Server farm services are still registered:
Microsoft Project Server Diagnostics Service
Project Server Application Service
Microsoft Project Server Events Service (ProjectEventService16)
Microsoft Project Server Calculation Service (ProjectCalcService16)
Microsoft Project Server Queuing Service (ProjectQueueService16)
This appears to force the Project Server post‑upgrade path even in a farm without PWA, which then fails on the missing column SAFE_NOTIFICATION_DATA.
Posting here to help correlate reports;
Cheers,
Permalink
I can reproduce this problem too. March has problem and we need to fix it.
Permalink
We also have this exact error message in one of our customer’s farms. There is no Project Server installed as far as I know. The customer does not have a Project Server license either.
We have an english SPSE installation with the german languge pack. We are also coming from the January 2026 patch.
Permalink
for the issue mentioned by users for march do we need to skip it until fixed
Permalink
Hi Vikram,
in case you mean the SAFE_NOTIFICATION_DATA error – no.
The issue only affects database schema upgrades from January 2026 CU to March 2026 CU.
Older or new database schemas can be upgraded without a problem.
If your servers are currently on January 2026 CU ensure to first install February 2026 CU and run the config wizard to upgrade the database schemas to February 2026 CU level. A
Afterwards you can install March 2026 CU without any problems.
If your servers are on an older CU oder your servers already have February 2026 CU installed and the config wizard has upgraded the databases you can also install March 2026 CU without any problems.
Cheers,
Stefan
Permalink
Dear Stefan, I really appreciate your blog. If you regularly install SharePoint CU, you really have to know your blog! Even after extensive research, I haven’t found a solution to the following problem. I hope you can help me… We install SharePoint CU in our SharePoint Subscription Edition farms 3-4 times a year (depending on the criticality of the security fixes). Everything’s working perfectly so far. Immediately after installing the CU (incl. running the Config Wizard :-)), the upgrade sessions for the individual farm servers are visible in Central Administration under “Check upgrade status” (with the status “Success”). When I access the “Upgrade Status” Page again a few weeks later, before the next update, the records from the last update have disappeared (“There are no items to show in this view.”). Can this be changed (e.g. retention time for these records can be configured or deletion of these records can be switched off)?
Permalink
Hi Reto,
this question has not come up before and I never looked into this – so I cannot answer this from the back of my head.
My farms are all patched on a monthly cadence.
My suggestion would be to open a support case with Microsoft to get this investigated.
Feel free to send me the SR number via “contact the blog author” at the top right of this page.
If I have bandwidth I can take ownership of the ticket.
Cheers,
Stefan
Permalink
Getting the following exception in Config Wizard after applying March 2026 CU over October 2026 CU on a SharePoint SE Single Server Farm.
Anyone seen this?
Regs
Martin
An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown. Additional exception information:
Action 18.0.15.0 of Microsoft.Office.Project.Server.Database.Extension.Upgrade.PDEUpgradeSequence failed. (EventID:ajywk)
Exception: Cannot find the object “MSP_REMINDER_TEMP_STORAGE” because it does not exist or you do not have permissions. (EventID:ajywk)
Upgrade [SPContentDatabase Name=SPContent_Root] failed. (EventID:an59t)
Inner Exception: Cannot find the object “MSP_REMINDER_TEMP_STORAGE” because it does not exist or you do not have permissions. (EventID:an59t)
Exception: Action 18.0.15.0 of Microsoft.Office.Project.Server.Database.Extension.Upgrade.PDEUpgradeSequence failed. (EventID:an59t)
Upgrade Timer job is exiting due to exception: Microsoft.SharePoint.Upgrade.SPUpgradeException: Action 18.0.15.0 of Microsoft.Office.Project.Server.Database.Extension.Upgrade.PDEUpgradeSequence failed. —> Microsoft.Data.SqlClient.SqlException: Cannot find the object “MSP_REMINDER_TEMP_STORAGE” because it does not exist or you do not have permissions. — End of inner exception stack trace —
Permalink
… over October 2025 CU – sorry.