The product group released the September 2022 Cumulative Update for the SharePoint 2013 product family.
For September 2022 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, September 2022 CU includes all fixes from September 2022 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 September 2022 CU should be available at the following locations in a couple of hours:
- KB 5002262 – SharePoint Foundation 2013 September 2022 CU
- KB 5002264 – SharePoint Server 2013 September 2022 CU
- KB 5002263 – Project Server 2013 September 2022 CU
- There was no update released for Office Web Apps Server 2013 in September 2022
The Full Server Packages for September 2022 CU are available through the following links:
- Download SharePoint Foundation 2013 September 2022 CU
- Download SharePoint Server 2013 September 2022 CU
- Download Project Server 2013 September 2022 CU
- There was no update released for Office Web Apps Server 2013 in September 2022
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 Stefan,
after installing the september CU the web front end server do not answer any request.
I i request on a wfe https://localhost the IIS respond with this error:
Config Error
Cannot read configuration file because it exceeds the maximum file size
Config File
\?\C:\inetpub\wwwroot\wss\VirtualDirectories\Hostnamed SC Webapplication-443\web.config
I compared the web.config with the last “.bak” in the directory and it is about 100kb larger than the bak (251kb vs 148 kb)
There are many new lines in the web.config like:
and
Do you know such problems?
best regards
Jörg
Permalink
Hi Joerg,
its possible that in context of enabling built in controls for the security fixes released this month significantly increased the web.config file.
If this file already had a large size the default maximum value might have exceeded.
You can change the maximum size using a registry key:
https://docs.microsoft.com/en-ca/archive/blogs/httpcontext/cannot-read-configuration-file-because-it-exceeds-the-maximum-file-size-web-config
Cheers,
Stefan
Permalink
Just wanted to chime in saying we experienced this issue as well and increasing the size of the config like in the article your posted fixed out issue.
Permalink
Good evening,
we had the same problem. First of all I changed the web.config with the backup web.config.
Now I have tested also the possibility to change MaxWebConfigFileSizeInKB and it also worked.
Thank you!
Permalink
Hi Stefan,
Thank you for sharing CU updates for SharePoint Environment.
I have a question related to the Office Web Apps Server 2013. We couldn’t patch our SharePoint 2013 Environment with August 2022 CU updates and have decided to patch the SharePoint environment along with Office Web Apps Server 2013 with September 2022 CU this weekend. As no update was released for Office Web Apps Server 2013 in September 2022, can we patch only the SharePoint 2013 server with September 2022 CU updates? Do we have to patch Office Web Apps Server 2013 with August 2022 during this patch?
SharePoint CU: https://support.microsoft.com/en-us/topic/september-13-2022-cumulative-update-for-sharepoint-enterprise-server-2013-kb5002264-2ceb3d37-f945-4d1b-9a1a-952bab2df2d5
Office Web Apps Server 2013: https://support.microsoft.com/en-gb/topic/august-9-2022-update-for-office-web-apps-server-2013-kb5002237-462fdd77-b355-4620-a865-e1aef746b712
Your suggestion is precious to us. Thank you.
Best Regards,
Meena Makwana
Permalink
Hi Meena, it’s recommended but not required to keep Office Web Apps and SharePoint patch level in sync. So best would be to patch Office Web Apps with the August patch and SharePoint with the September CU. But it also depends on the previous patch level of your system.