October 2015 CU for SharePoint 2013 is available for download


The product group released the October 2015 Cumulative Update for the SharePoint 2013 product family.

For October 2015 CU we have full server packages (also known as Uber packages). No other CU is required to fully patch SharePoint.

As this is a common question: Yes, October 2015 CU includes all fixes from October 2015 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 October CU should be available at the following locations in a couple of hours:

  • KB 3085488 - SharePoint Foundation 2013 October 2015 CU
  • KB 3085492 - SharePoint Server 2013 October 2015 CU
  • KB 3085489 - SharePoint Server 2013 with Project Server October 2015 CU
  • KB 3085571 - Office Web Apps Server 2013 October 2015 CU - This is also a security fix!

The Full Server Packages for October 2015 CU are available through the following links:

Important: If your farm has been on a patch level lower than July 2015 CU: Unlike other CUs - after installing the October 2015 CU you need to run the SharePoint 2013 Products Configuration Wizard on each machine in the farm.
If you don't run PSCONFIG after installing October 2015 CU (on a farm which had a lower patch level than July 2015 CU) crawl might no longer work - so ensure to schedule a maintenance window when installing this CU which includes PSCONFIG runs.

See here for detail: https://blogs.technet.microsoft.com/stefan_gossner/2015/07/15/important-psconfig-is-mandatory-for-july-2015-cu-for-sharepoint-2013/

Be aware that the SharePoint Server 2013 CU contains the SharePoint Foundation CU. And the SharePoint Server 2013 with Project Server CU contains Project Server CU, SharePoint Server CU and SharePoint Foundation CU.
Related Info:

Comments (19)

  1. Prashant says:

    Hi,

    Do we have any update on SharePoint 2013 PU for Oct 2015?

    1. Just released! Had to wait for the official security bulletin to be published.

  2. Rob says:

    Just as a point of confirmation…. if I have a vanilla build of SP2013, with SP1 rolled up into it, I assume I can instantly apply the Oct 2015 CU without any more setup.

    So, base install, patch, restart, then start spinning up services, web apps. etc.

  3. Florian says:

    Hello Stephan

    is the Issue “August 2015 CU Error – “File names can’t contain the following characters” fixed with CU Aug2015 resolved. I haven´t seen that on release notes.

    1. You mean when attaching files to list items?
      Yes the fix for this issue should be included in this CU.

      1. Florian says:

        Correct i mean this, thanks.

  4. Kyle Daley says:

    Hey Stefan,

    I’m still getting Sys.InvalidOperationException: ‘timeZoneId’ is not a property or an existing field. when trying to run a search. It’s been broken for many CU’s now.

    I ran PSCONFIG and did an Index Reset/Full Crawl. The Microsoft.Office.Server.Search.ServerProxy.dll in my _app_bins are dated 9/15 and are version 15.0.4745.1000.

    1. Hi Kyle,
      I would recommend to open a support case with Microsoft to get this issue analyzed in more detail.
      Cheers,
      Stefan

    2. Oleg Starshinov says:

      Hi Kyle,
      Were you able to figure it out? I have the same issue..
      Thanks!
      Oleg

    3. Ben Stegink says:

      I’m also getting this error in a couple different environments. Anyone have any updates/fixes?

    4. Oleg Starshinov says:

      Ok.. I figured out why I was getting this error. I hope it helps someone.
      This was on our dev environment. I hit F5 in VS2013 to debug a web part and it prompted me to enable debugging. I said “Yes”.
      Doing this, modified the web.config file for the Web Application and changed this line:

      to

      Setting the debug switch back to “false” fixed the issue for me.
      Thanks!
      Oleg

      1. Oleg Starshinov says:

        The page hid my xml lines..
        VS2013 changed
        compilation batch=”false” debug=”false”
        to
        compilation batch=”false” debug=”true” optimizeCompilations=”true”

        Just do a search in your web.config..

  5. Stephan Bren says:

    Stefan – I’m seeing this error whenever I click on Crawl Latency in Search Service: Crawl Reports. This did not occur before installing the October 2015 CU. Others have also reported this but with respect to the August 2015 CU, which I skipped (along with the September updates). Do you if this issue is a bug?

    1. Hi Stephan,
      this issue has recently been reported to us and is currently being investigated.
      Cheers,
      Stefan

      1. Kaine says:

        Hi just wondering what CU fixes Column with name ‘HybridParserTimeAvg’ was not found. ? I have checked and my farm with October 2016 still has this issue.

      2. AG says:

        Hello Stefan,

        Has this issue “Column with name ‘HybridParserTimeAvg’ was not found” been fixed yet? We are currently on March’17 CU and are still seeing this error when clicking “Crawl Altency” reports. If not fixed, is there a timeline for a fix?

        thanks,
        AG

        1. Hi AG,

          there is no plan to fix the issue you described through a hotfix as this is not an issue which can be addressed through a hotfix.
          Whenever a customer calls Microsoft support the issue will be fixed individually for the requesting customer through manual patches in the affected databases.

          Cheers,
          Stefan

          1. AG says:

            Thanks Stefan! Appreciate your reponse.

            –AG

Skip to main content