For more details check this article: Trending Issue: SharePoint fixes fail to install after installation of September 2025 CU
The product group released the November 2025 Cumulative Update for SharePoint Server 2016 product family.
This CU also includes Feature Pack 1 which was released with December 2016 CU and Feature Pack 2 which was released with September 2017 CU.
The KB articles for November 2025 CU should be available at the following locations in a couple of hours:
- KB 5002805 – November 2025 Update for SharePoint Server 2016 (language independent)
This is also a security update! - There was no language dependent fix released this month.
The most recent language dependent fix is KB 5002787 from October 2025 CU.
If this is not yet installed on your Farm, you need to install it together with the language independent fix.
The downloads for November 2025 CU are available through the following links:
- Download November 2025 Update for SharePoint Server 2016 (language independent)
This is also a security update! - There was no language dependent fix released this month.
The most recent language dependent fix is KB 5002787 from October 2025 CU.
If this is not yet installed on your Farm, you need to install it together with the language independent fix.
Important: It is required to install both fixes (language dependent and independent) to fully patch a SharePoint server. This applies also to servers which do not have language packs installed. The reason is that each SharePoint installation includes a language dependent component together with a language independent component. If additional language packs are added later (only) the language dependent fix has to be applied again.
It is irrelevant which language you pick on the drop down in download center. Even the language dependent fixes are all in the same package for all languages.
After installing the fixes you need to run the SharePoint 2016 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.
SharePoint 2016 November 2025 CU Build Numbers:
Language independent fix: 16.0.5526.1001
To understand the different version numbers please have a look at my article which explains the different SharePoint build numbers.
Please ensure to have a look at the SharePoint Patching Best Practices before applying new fixes.
Related Links:
- Technet: Updated Product Servicing Policy for SharePoint Server 2016
- Blog: SharePoint Patching Best Practices
- Blog: Common Question: What is the difference between a PU, a CU and a COD?
- 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 Patch Build Numbers Powershell Module
- Blog: SharePoint Server 2016 Zero-Downtime Patching Demystified
- Blog: SharePoint does not have a build version. Full Stop.

Permalink
Regarding the note in the blue box, would it not be more accurate to say “If your current farm patch level is September 2025 then you need to…..”
My understanding was that if you’ve installed the October update (after installing September) then the issue is resolved and no accounts need to be removed from groups. Or do I have that wrong?
Permalink
Yes – absolutely!
Thanks Tom! Wording has been updated.
Permalink
Hello Stefan,
can you please confirm patching steps for 2016 farm with Classic Workflow Manager and August CU?
Add the ServerDebugFlags 53601
Ensure LOCAL SYSTEM account is removed from WSS_WPG & IIS_IUSRS groups.
Install Novermber CU & run the wizards.
And that’s all? Thank you.
Permalink
Hi Martin,
if your SharePoint farm is on August CU or older, removing local system is not required.
If your SharePoint farm is on September CU, then it is required.
The other steps look good.
Cheers,
Stefan
Permalink
Hi Stefan!
Instructions for installing KB5002805 says if im using Sharepoint Workflow Manager i have to install KB5002799 before SP-server patch. This was missed in my environment.
Do you know if i have to uninstall KB5002805 and start all over, KB5002799 first and then KB5002805?
Installing KB5002799 on top wont work?
Regards
/Micke
Permalink
H Micke,
KB5002799 is a SPWFM fix, not a SharePoint Server fix.
So you can install it on the SPWFM machine before or after installing the SharePoint Server fix.
But don’t forget to uninstall the old SPWFM client and then install the SPWFM client libraries matching the SPWFM fix from KB5002799 as well on all SPWFM and SharePoint Server machines!
Without it will not work.
Cheers,
Stefan
Permalink
Hi Stefan!
Thank you for your answer!
I found why instruction was confusing me.
Im Swedish and the instruction in swedish for KB5002805 must be wrong.
“Om du kör SharePoint Arbetsflödeshanteraren måste du installera SharePoint-Arbetsflödeshanteraren (KB5002799) i servergruppen innan du installerar den här kumulativa uppdateringen.”
Becomes in english:
“If you are running Sharepoint Workflow Manager you must install SPWF(KB5002799) before you upgrade this CU(KB5002805)
The english page has the correct instruction
“If you’re currently running SharePoint Workflow Manager, you must install the August 2025 update for SharePoint Workflow Manager to your farm before you install this cumulative update.”
Regards,
/Micke
Permalink
after install and update november CU we faced error
500 – Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed.
Permalink
Hi Abdullah,
please check if you are running into this issue:
https://blog.stefan-gossner.com/2023/10/17/trending-issue-module-sprequestfiltermodule-could-not-be-found-after-september-october-2023-cu/
Cheers,
Stefan
Permalink
HI Stefan,
We are currently using classic workflow manager with our SP 2016 farm.
During the October patch update, we already added below and completed the patching successfully :
ServerDebugFlags 53601
Now for November patch, there is no need to run the below script again, we can simply go ahead with binaries installation and PSConfig using an account which is NOT a member of WSS_WPG:
$farm = Get-SPFarm
$farm.ServerDebugFlags.Add(53601)
$farm.update()
iisreset
Permalink
Hi Aditya,
yes, there is no need to set the ServerDebugFlag again.
Cheers,
Stefan
Permalink
Stefan,
Our Last CU is July 2025, do we need to proceed following instructions as if it was September 2025 CU?
Permalink
Hi Pam,
no – there are no special steps required if you skip September 2025 CU.
Cheers,
Stefan
Permalink
I guess its no difference to go from August CU to November CU, but I better ask, can it be installed as “usual” as well ?
AMSI is not enable, how will that affect the farm when “Machine Key Rotation using the new automatic SharePoint timer job” is implemented? Should it just work out of the box, or can it be disabled if necessary?
Permalink
Hi Freddy,
you can directly go from August to November CU.
AMSI will be permanently enabled after the upgrade and cannot be disabled. So my recommendation is that you check your configuration against the following article before applying the patch to ensure that the relevant module is correctly configured to prevent a downtime:
https://blog.stefan-gossner.com/2023/10/17/trending-issue-module-sprequestfiltermodule-could-not-be-found-after-september-october-2023-cu/
The machine key rotation job will be available after the upgrade and will be configured to run once a week on Sunday.
It should work automatically but – yes, the job can be disabled if required.
Cheers,
Stefan
Permalink
Hi Stefan,
Thank you very much for taking your time and answering so quickly. Installation seems to have gone well.
Best regards
Fred