The product group released the November 2020 Cumulative Update for the SharePoint 2013 product family.
For November 2020 CU we have full server packages (also known as Uber packages) for all products. No other CU is required to fully patch SharePoint.
As this is a common question: Yes, November 2020 CU includes all fixes from November 2020 PU.
ATTENTION:
Be aware that all Updates for SharePoint 2013 require SharePoint Server 2013 SP1 to be installed first.
Please also have a look at the article that discusses how to properly patch a SharePoint 2013 farm which has Search enabled (see below).
Previous releases of the SharePoint Server 2013 cumulative update included both the executable and the .CAB file in the same self-extracting executable download. Because of the file size, the SharePoint Server 2013 package has been divided into several separate downloads. One contains the executable file, while the others contain the CAB file. All are necessary and must be placed in the same folder to successfully install the update. All are available by clicking the same Hotfix Download Available link in the KB article for the release.
This CU includes all SharePoint 2013 fixes (including all SharePoint 2013 security fixes) released since SP1. The CU does not include SP1. You need to install SP1 before installing this CU.
The KB articles for November 2020 CU should be available at the following locations in a couple of hours:
- KB 4486728 – SharePoint Foundation 2013 November 2020 CU
- KB 4486731 – SharePoint Server 2013 November 2020 CU
- KB 4486729 – Project Server 2013 November 2020 CU
- KB 4486727 – Office Web Apps Server 2013 November 2020 CU
The Full Server Packages for November 2020 CU are available through the following links:
- Download SharePoint Foundation 2013 November 2020 CU
- Download SharePoint Server 2013 November 2020 CU
- Download Project Server 2013 November 2020 CU
- Download Office Web Apps Server 2013 November 2020 CU
After installing the fixes you need to run the SharePoint 2013 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.
Be aware that the SharePoint Server 2013 CU contains the SharePoint Foundation 2013 CU. And the Project Server 2013 CU also contains the SharePoint Server 2013 CU and SharePoint Foundation 2013 CU.
Please ensure to have a look at the SharePoint Patching Best Practices before applying new fixes.
Related Info:
- Technet: Updated Product Servicing Policy for SharePoint 2013
- 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
- Blog: Support for SharePoint 2013 RTM has ended
- Blog: SP1 for SharePoint 2013
- Technet: CHANGE: SharePoint 2013 Rollup Update for the December 2013 Cumulative Update Packaging
- Technet: Install a software update for SharePoint 2013
- Blog: How to: install update packages on a SharePoint 2013 farm where search component and high availability search topologies are enabled
- Technet: Update Center for Microsoft Office, Office Servers, and Related Products
- Blog: SQL Server 2014 and SharePoint Server 2013
Permalink
Hello.
Have you faced an issue with latest google chrome update and this update?in terms of FBA and claim based authentication. On IE and Firefox it is working but not on google chrome.
Thx
Permalink
It is okay.I managed to find the issue. The portal is http and chrome 80+ has some issues with same site cookies. I was able to fix it with url rewrite in case anyone faced similar issue.Thx
Permalink
Could you please share step by step instructions to fix this issue?
Permalink
Hello,
Does anybody have step by step instruction, how to install this update?
Permalink
Hi Martin,
important is to evaluate it first in a test environment as you cannot uninstall it.
Recommended steps:
1) take a farm backup
2) install the fix on all machines
3) run sharepoint config wizard on the machine hosting the central admin
4) run sharepoint config wizard on all other machines
Cheers,
Stefan
Permalink
Hi Stefan,
I having issues with the timer service after installing the patch. The cache.ini file is not appearing on the cache folder and the original GUID folder has been updated as .tmp
Could you please help if this is a known issue?
Permalink
Hi Arul,
this is not a known issue.
Cheers,
Stefan
Permalink
Hi
Is it best to install all the updates then run PSCONFIGGUI at the end- or run psconfig after each patch?
Download SharePoint Foundation 2013 November 2020 CU
Download SharePoint Server 2013 November 2020 CU
Download Project Server 2013 November 2020 CU
Download Office Web Apps Server 2013 November 2020 CU
Permalink
Also, is it still a good idea to run the patch via this script to save time? https://blog.russmax.com/why-sharepoint-2013-cumulative-update-takes-5-hours-to-install/
Permalink
Hi Trev,
for SharePoint 2013 the answer is yes.
Cheers,
Stefan
Permalink
Hi Trev,
you only have to install one of these patches – not all of them.
E.g. the SharePoint Server patch includes the SharePoint Foundation one and the Project Server patch includes the SharePoint Server and the SharePoint foundation one.
The config wizard only has to be run once after all patches you would like to applied are installed.
Cheers,
Stefan
Permalink
We are on July 2020 CU and we want to install the Nov 2020 CU, will the issue from Oct 2020 CU carried to Nov 2020 CU or this is free from Oct 2020 CU issue?
Permalink
Hi Prasad,
which issue are you talking about?
Cheers,
Stefan
Permalink
Hi Stefan,
we are unable to install kb4486731, every time we try to run, we get the following error: “The installation of this package failed” and we have also tried extracting the KB, however the extract also fails.
Patch installation log says that :” The Detection failed , this can be due to a corrupted installation database.
Permalink
Hi Nayana,
windows has an installation database where it keeps track of all installed products and updates.
If this database is corrupt this error will occur.
My recommendation is to open a support case with Microsoft to see if the issue is indeed caused by a corrupt installation database and if yes to check if the database can be repaired.
Cheers,
Stefan
Permalink
Hi Stefan,
Thank you this information .
We have tried to install the same update on 3 different farms which is connected to 3 different sql servers. On all the 3 farms we get the same error.
Permalink
Hi Alex,
either the fix got corrupted during download or there is a problem on each of these servers. Have they e.g. been created through the same template?
If you cannot resolve the issue on your own I would recommend to open a support case with Microsoft.
Cheers,
Stefan
Permalink
Hi Stefan,
Thank you for the advice . Servers were not created using same template.