September 2020 CU for SharePoint 2013 product family is available for download

The product group released the September 2020 Cumulative Update for the SharePoint 2013 product family.

For September 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, September 2020 CU includes all fixes from September 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 September 2020 CU should be available at the following locations in a couple of hours:

  • KB 4484519 – SharePoint Foundation 2013 September 2020 CU
  • KB 4484523 – SharePoint Server 2013 September 2020 CU
  • KB 4484521 – Project Server 2013 September 2020 CU
  • KB 4484518 – Office Web Apps Server 2013 September 2020 CU

The Full Server Packages for September 2020 CU are available through the following links:

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:

6 Comments


  1. After installing SharePoint Server 2013 September 2020 CU, we get this:
    The base type ‘AC.Web.PageLayouts.ACPageLayouts.ACHomePage’ is not allowed for this page. The type AC.Web.PageLayouts.ACPageLayouts.ACHomePage, AC.Web, Version=1.0.0.0, Culture=en, PublicKeyToken=5f3d55c70580fe7d could not be found or it is not registered as safe.

    Reply

  2. Hi Stefan, we’re seeing this happen after applying Sep 2020 CU. The unsafe control fix doesn’t resolve the problem.

    Container WebPart: The attribute ‘autoeventwireup’ is not allowed in this page.
    at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding) at System.Web.UI.TemplateParser.ParseFile(String physicalPath, VirtualPath virtualPath) at System.Web.UI.TemplateParser.ParseInternal() at System.Web.UI.TemplateParser.Parse() at System.Web.Compilation.BaseTemplateBuildProvider.get_CodeCompilerType() at System.Web.Compilation.BuildProvider.GetCompilerTypeFromBuildProvider(BuildProvider buildProvider) at System.Web.Compilation.BuildProvidersCompiler.ProcessBuildProviders() at System.Web.Compilation.BuildProvidersCompiler.PerformBuild() at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) at System.Web.Compilation.BuildManager.GetVPathBuildResult(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean ensureIsUpToDate) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at OurCustomFramework.WebParts.ContainerWebPart.CreateChildControls()

    Reply

    1. Hi Desmond,
      please open a ticket with Microsoft support to ensure that this issue is tracked and can be analyzed in more details.
      Thanks,
      Stefan

      Reply

  3. After installing September 2020 CU for SharePoint 2013 we have started seeing following errors in few of the custom web parts:

    Web Part Error: The control type ‘System.Data.DataTable’ is not allowed on this page. The type System.Data.DataTable, System.Data, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 could not be found or it is not registered as safe. Correlation ID: c206799f-10dd-7037-7d24-5086ce38d8a7.

    Reply

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.