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 January 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 January 2026 CU will be available at the following location in a couple of hours:
- KB 5002822 – January 2026 Update for SharePoint Server Subscription Edition
This is also a security update!
The download for January 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 January 2026 CU Build Number: 16.0.19127.20442
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,
Hope you’re doing great.
I wanted to check whether the SharePoint worker process crashes with the 0xC06D007E and 0xE0434352 exceptions have been fixed in this release.
Thanks,
Chandu
Permalink
Hi Chandu,
no it has not.
If a fix for this issue would have been included, I would have posted the information in the relevant article and/or created a separate blog post for it.
The fix for the issue you are referring to is currently planned for February 2025 CU.
Cheers,
Stefan
Permalink
Thankyou Very Much !!
Permalink
Hi Stefan,
Hope you’re doing great, We currently have a subscription edition farm with 2 servers, WFE/CD and APP/search, after installing the KB the wizard is sending error because it does not recognize the installation of the KB in the WFE, suggests to run Get-SPProduct -Local, but the Powershell console sends the following error:
Get-SPProduct -Local
Get-SPProduct : Snix_PreLoginBeforeSuccessfulWrite (provider: SSL Provider, error: 0 – An existing connection was forcibly closed by the remote host.)
At line:1 char:1
Get-SPProduct -Local
~~~~~~~~~~~~~~~~~~~~
CategoryInfo : InvalidData: (Microsoft.Share…letGetSPProduct:SpCmdletGetSPProduct) [Get-SPProduct], SqlException
FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SpCmdletGetSPProduct
Have you already seen this scenario?
Any advice is welcome
Permalink
Hi Pedro,
did you run the configuration wizard on the server that shows this error message?
Cheers,
Stefan
Permalink
Hi Stefan!
Hope you are doing fantastic!
We are currently have a SE farm with 2 servers, FE/CD and APP/Search it is on September 2025 CU level.
We tried to install the new January 2026 CU, but the installer stuck at about 20%.
I see the following warnings flooding the Windows Application log with the 10010 Event ID:
Application ‘C:\Windows\System32\inetsrv\w3wp.exe’ (pid 7316) cannot be restarted – Application SID does not match Conductor SID..
Application ‘C:\Windows\System32\inetsrv\w3wp.exe’ (pid 8900) cannot be restarted – Application SID does not match Conductor SID..
Application ‘C:\Windows\System32\inetsrv\w3wp.exe’ (pid 2332) cannot be restarted – Application SID does not match Conductor SID..
The sts-x-none_MSPLOG.LOG log is flooded with the following (similar to this but with different assembly):
01/23/2026 19:33:57.719 [1932]: Assembly Install: Failing with hr=80070005 at RemoveDirectoryAndChildren, line 393
01/23/2026 19:33:57.719 [1932]: Detailed info about C:\Windows\assembly\temp\MACETNCU4P\microsoft.ceres.external.contentapi.dll
01/23/2026 19:33:57.719 [1932]: File attributes: 00000080
01/23/2026 19:33:57.782 [1932]: Restart Manager Info: 3 entries
01/23/2026 19:33:57.782 [1932]: App[0]: (7316) IIS Worker Process (), type = 5
01/23/2026 19:33:57.782 [1932]: App[1]: (8900) IIS Worker Process (), type = 5
01/23/2026 19:33:57.782 [1932]: App[2]: (2332) IIS Worker Process (), type = 5
01/23/2026 19:33:57.782 [1932]: Security info:
01/23/2026 19:33:57.782 [1932]: Owner: S-1-5-18
01/23/2026 19:33:57.782 [1932]: Group: S-1-5-18
01/23/2026 19:33:57.782 [1932]: DACL information: 5 entries:
01/23/2026 19:33:57.782 [1932]: ACE[0]: Type = 0x00, Flags = 010, Mask = 001f01ff, SID = S-1-5-18
01/23/2026 19:33:57.782 [1932]: ACE[1]: Type = 0x00, Flags = 010, Mask = 001f01ff, SID = S-1-5-32-544
01/23/2026 19:33:57.782 [1932]: ACE[2]: Type = 0x00, Flags = 010, Mask = 001200a9, SID = S-1-5-32-545
01/23/2026 19:33:57.782 [1932]: ACE[3]: Type = 0x00, Flags = 010, Mask = 001200a9, SID = S-1-15-2-1
01/23/2026 19:33:57.782 [1932]: ACE[4]: Type = 0x00, Flags = 010, Mask = 001200a9, SID = S-1-15-2-2
Could you please point me to the right directions?
Thanks in advance
Adam
Permalink
Hi Adam,
I assume you did not use my script to speed up the installation?
https://blog.stefan-gossner.com/2024/03/08/solving-the-extended-install-time-for-spse-cus/
https://github.com/stefangossner/Install-SPSE_Fix/blob/main/Install-SPSE_Fix.ps1
It seems IIS could not be stopped while installing the fix.
If it the install is still stuck, try to unblock it by manually stopping IIS using IISRESET /STOP
Cheers,
Stefan
Permalink
Hi Stefan!
Thanks for your quick reply. I used your script and will absolutely use it next time, it is a lifesaver.
Finally the CU is installed, and everythings is working.
Have a great weekend.
BRs
Adam
Permalink
Hi everyone,
we have recently done a migration of a mostly German SharePoint/Project farm to Subscription Edition, installed the latest updates and get the following issue, that had already been solved last February 2025:
Any date column in modern view (with custom or user friendly formatting) will swap day/month when the site locale is set to e.g German, but display it correctly when locale is set to e.g. English (US).
If we edit a file today Feb 4th 2026 (2026-02-04) it will state April 2ns with German and “Today” with English locale. Things edited on e.g. Jan 20th with be interpreted as 1st of the 20th month which does not exists and SP reverts to 01.01.0001 as default date. On the display is affected.
I can repro it it one farm, but seemingly not in another. Does anyone else have that behaviour?
https://support.microsoft.com/en-us/topic/description-of-the-security-update-for-sharepoint-server-subscription-edition-february-11-2025-kb5002681-df2df363-1ef0-4613-9526-778d5141b01c
Fixes an issue in which the Date column shows “30.12.1899” instead of the correct value if the list contains any column that use custom formatting.
Permalink
Update: Issue resolved
Apparently, the installed updates were not properly applied to the UI? After setting farm update ring to preview and back, SP wizard and IISResets, this (and other issues pointing to a pre-patch UI) resolved themselves.
Permalink
Hi,
I have had the same issue since November 2025 PU on DK and NO environments. Changing the feature release preferences did not help :/
Stefan – do you know anything about this issue?
Permalink
Hi KASP – sorry I’m not sure which “same issue” you are referring to as your comments is not the answer of a previous comment. Can you provide more details?
Thanks,
Stefan
Permalink
oh, sorry. I mean the problem from Adrian’s comment – with the DateTime field with friendly formatting. I have already created a ticket for MS technical support (2512050050000593)
Permalink
A combination fo the following did it for me:
– Run Wizard (PSConfigUI) directly, not command line / PowerShell. Repeat for good measure.
– Change Release Ring to Preview
– Run Wizard, IISReset, or better just Reboot the whole farm
– Change Release Ring back to Standard
– Run Wizard, IISReset, or better just Reboot the whole farm
Note: I had the issue on a fresh install with CU 2025-12. Ran the usual update process to 2026-01 to see if it does something > it did not. During the update, I did the farm update via commmand line, psconfig.exe, and in the process above I used the wizard. Note that the wizard stated for me that a config update after a language pack was pending.