The product group released the October 2021 Cumulative Update for the SharePoint 2013 product family.
For October 2021 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, October 2021 CU includes all fixes from October 2021 PU.
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 October 2021 CU should be available at the following locations in a couple of hours:
- KB 5002037 – SharePoint Foundation 2013 October 2021 CU
- KB 5002040 – SharePoint Server 2013 October 2021 CU
- KB 5002039 – Project Server 2013 October 2021 CU
- KB 5002036 – Office Web Apps Server 2013 October 2021 CU
The Full Server Packages for October 2021 CU are available through the following links:
- Download SharePoint Foundation 2013 October 2021 CU
- Download SharePoint Server 2013 October 2021 CU
- Download Project Server 2013 October 2021 CU
- Download Office Web Apps Server 2013 October 2021 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.
- 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
Every week I wait for your CU update! But this time I have a problem with the Office installation files (C: \ Windows \ Installer) – I have 1527 missing files on it.
I looked for the ‘Oputil.vbs’ file but I couldn’t find it on the internet. How can I solve this problem? Thanks!!!!
oputil can be found here:
If you need assistance to resolve this I would suggest to open a support case with Microsoft.
Thank you Stefan!!! I try with this!!
The vbs is OK, but Install-SPPatch give me an error:
Patch ubersrv2013-kb5002040-fullfile-x64-glb.exe installed with Exit Code 17302
In this case I would recommend to open a support case with Microsoft.
Alternatively you try to dig deeper yourself or rebuild the server.
I can see still after upgrade the build version not getting changed. the patch was successfully installed.
the build version is not a reliable way to determine if a fix was properly installed.
See here for details:
Thanks for the great information!
I have a issue in my Farm after October -21 SharePoint Patch updates. I am still seeing UPGRADE AVAILABLE status , Though we have ran PSCONFIG and was successful.
sounds as if there are some objects which have not been successfully upgraded.
I would suggest to run “stsadm.exe -o localupgradestatus” on the machine which shows upgrade required to see which objects require an upgrade.