November 2016 CU for SharePoint 2013 product family is available for download


The product group released the November 2016 Cumulative Update for the SharePoint 2013 product family.

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

  • KB 3127930 – SharePoint Foundation 2013 November 2016 CU
  • KB 3127933 – SharePoint Server 2013 November 2016 CU
  • KB 3127931 – SharePoint Server 2013 with Project Server November 2016 CU
  • KB 3127929 – Office Web Apps Server 2013 November 2016 CU – this is also a security fix!

The Full Server Packages for November 2016 CU are available through the following links:

Important: If your farm has been on a patch level lower than July 2015 CU: July 2015 CU and later contains a breaking change compared to earlier builds which requires running the SharePoint 2013 Products Configuration Wizard on each machine in the farm right after installing the CU.
If you don’t run PSCONFIG after installing this 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 (20)

  1. Neeraj Joshi says:

    Hello ,

    Does it contains all Language packs??

    Thanks

    Neeraj

    1. Hi Neeraj,
      SharePoint 2013 CUs include fixes for all language packs.
      Cheers,
      Stefan

  2. Thanks again for this great Support to keep us up to date.

    1. SPAdmin says:

      Agreed! Goßner in 2020!

  3. Piotr Siódmak says:

    Hi,
    KB3115176 does not list any improvements and fixes. Was that intentional?

    1. Hi Piotr,
      sorry – don’t know. I’m not involved in the KB creation.
      Cheers,
      Stefan

  4. Brad says:

    Hi Stefan,

    Can you clarify something for me, when a security update is included in the SharePoint Server instance if I have our Server Admins release this update through their WSUS updates does that cover the security of the SharePoint exploit for Word Automation Services? The reason I ask is lately there has been several of these security fixes and I am applying the updates monthly although I am starting to wonder is there an easier way to address these particular security fixes and then I can simply apply the Office web apps ones. I am going through applying the update packages and running the PSConfig wizard.

    Thanks as always!

    1. Hi Brad,
      not sure if I correctly understood the question but yes, security fixes for Word Automation Services can be deployed through WSUS. But be Aware that you still have to run PSCONFIG after installing the fixes.
      Cheers,
      Stefan

      1. Brad says:

        Hi Stefan,

        Got it! That’s what I was trying to ask, I’m glad you understood! 🙂 Was hoping that if the update was pushed through WSUS we could avoid the additional work of running PSCONFIG afterwards. This clarifies things, thanks again.

  5. Aria says:

    Hi Stefan , Many thanks for your support and update. We have not applied any cumulative updates since the installtion of SP1. Does this Cumulative update require any privious Cumulative updates ? When I try to install this cu , i get the following error : “The expected product version was not detected on the system” . Vi have a 2 server farm with the following information : The version of the our SharePoint server 2013 is 15.0.4571.1502 and the version of the language pack for Sharepoint and Project Server 2013 is “15.0.4420.101” Many thanks in advance for your support Stefan !

    1. Hi Aria,
      the Problem in your sitatuation is not the SharePoint Version. It is the language pack. The base SharePoint Installation is on SP1 while your language pack is on RTM Level.
      That is unsupported for two different reasons:
      1) the resource files for your Server for the additional language do not match the binaries installed on the System (These come with the base Installation)
      2) The only supported Service pack Level now is SP1 – and your language pack is on RTM leve.

      To fix this you have to install SP1 for all language packs where this has not yet been installed.
      You Can find the Service pack for the language packs at the following link:
      https://www.microsoft.com/en-us/download/details.aspx?id=42543

      After updating all language packs with SP1 you should be able to install the CU.

      Cheers,
      Stefan

      1. Aria says:

        Hi Stefan, Many thanks !
        in order to read the display version info for installed SharePoint product and language packs (which I had provided in my privous post/Comment) I had used the powershell script that you have provided in the following link:
        https://blogs.technet.microsoft.com/stefan_gossner/2015/04/20/powershell-script-to-display-version-info-for-installed-sharepoint-product-and-language-packs/

        But when I checked the already installed language pack vessions (from SharePoint Central Admin -> Manage Patch Status) I can view different versions and I can not find the version which is displayed when I run your powershell script i.e I can not find the version “15.0.4420.101”

        from “Manage Patch Status” page in SharePoint Central Administration I can se the following versions for the different languages :

        Product Version Install Status
        ——————————————————————————————————————————————

        Language Pack for SharePoint and Project Server 2013 – Danish/dansk Installed

        Microsoft Access Services Danish Language Pack 15.0.4433.1507 Installed
        Microsoft Document Lifecycle Components Danish Language Pack 15.0.4433.1507 Installed
        Microsoft Education Danish Language Pack 15.0.4433.1507 Installed
        Microsoft Excel Services Danish Language Pack 15.0.4433.1507 Installed
        Microsoft InfoPath Form Services Danish Language Pack 15.0.4433.1507 Installed
        Microsoft Office PowerPoint Services Danish Language Pack 15.0.4433.1507 Installed
        Microsoft OMUI Danish Language Pack 15.0.4433.1507 Installed
        Microsoft Project Server Danish Language Pack 15.0.4433.1507 Installed
        Microsoft Search Server 2013 Danish Language Pack 15.0.4433.1507 Installed
        Microsoft Server Proof (Arabic) 2013 15.0.4571.1502 Installed
        Service Pack 1 for Microsoft SharePoint Server 2013 (KB2880552) 64-Bit 15.0.4571.1502 Installed
        Microsoft Server Proof (Danish) 2013 15.0.4571.1502 Installed
        Service Pack 1 for Microsoft SharePoint Server 2013 (KB2880552) 64-Bit 15.0.4571.1502 Installed
        Microsoft Server Proof (English) 2013 15.0.4571.1502 Installed
        Service Pack 1 for Microsoft SharePoint Server 2013 (KB2880552) 64-Bit 15.0.4571.1502 Installed
        Microsoft Server Proof (French) 2013 15.0.4571.1502 Installed
        Service Pack 1 for Microsoft SharePoint Server 2013 (KB2880552) 64-Bit 15.0.4571.1502 Installed
        Microsoft Server Proof (German) 2013 15.0.4571.1502 Installed
        Service Pack 1 for Microsoft SharePoint Server 2013 (KB2880552) 64-Bit 15.0.4571.1502 Installed
        Microsoft Server Proof (Russian) 2013 15.0.4571.1502 Installed
        Service Pack 1 for Microsoft SharePoint Server 2013 (KB2880552) 64-Bit 15.0.4571.1502 Installed
        Microsoft Server Proof (Spanish) 2013 15.0.4571.1502 Installed
        Service Pack 1 for Microsoft SharePoint Server 2013 (KB2880552) 64-Bit 15.0.4571.1502 Installed
        Microsoft Server Proof (Swedish) 2013 15.0.4571.1502 Installed
        Service Pack 1 for Microsoft SharePoint Server 2013 (KB2880552) 64-Bit 15.0.4571.1502 Installed
        Microsoft Shared Coms Danish Language Pack 15.0.4433.1507 Installed
        Microsoft SharePoint Foundation 2013 1030 Lang Pack 15.0.4433.1507 Installed
        Microsoft SharePoint Multilingual Solutions Danish Language Pack 15.0.4433.1507 Installed
        Microsoft SharePoint Portal Danish Language Pack 15.0.4433.1507 Installed
        Microsoft Slide Library Danish Language Pack 15.0.4433.1507 Installed
        Microsoft Visio Services Danish Language Pack 15.0.4433.1507 Installed
        Microsoft Web Analytics Danish Language Pack 15.0.4433.1507 Installed
        Microsoft Word Server Danish Language Pack 15.0.4433.1507 Installed
        Microsoft Workflow Solutions Framework Danish Language Pack 15.0.4433.1507 Installed
        Microsoft XMUI Danish Language Pack 15.0.4433.1507 Installed
        PerformancePoint Services in SharePoint 1030 Language Pack 15.0.4433.1507 Installed

        ———————————————————————————————————————————-
        Should we update only the language packs with SP1 which have a version different from “15.0.4571.1502” or should we update all of them ?

        Many thanks in advance Stefan we appriciate your support very much !

        1. The numbers here are the patch Levels. Relevant is the patch baseline – so only the previous info counts.
          You have to apply SP1 for those language packs where the patch baseline is below the SP1 baseline.
          Cheers,
          Stefan

          1. Aria says:

            Many thanks Stefan ! After applying SP1 for the language pack as you suggested , it was posssible to install the CU successfully .

            Best regards !

  6. alex-kren says:

    Hi,

    there is a new feature introduced with this CU.
    •Introduces a new drop-down menu with options Edit (in native client), Edit in browser and Download that works across all major browsers in search result page of SharePoint 2013.

    We do have the issue that the drop down menu displays “Edit, undefined, undefined”. The options are working but the displayed name is wrong.
    Does someone else have this issue too?

    Regards,
    alex

    1. Hi Alex,
      if you need assistance I would recommend to open a support case with Microsoft to get this analyzed.
      Cheers,
      Stefan

    2. BlueSky2010 says:

      Hi Alex – any update on your issue? Have you opened a ticket with Microsoft support? I’m potentially looking to go to Nov CU and trying to track any issues.
      Appreciate any feedback.
      https://social.technet.microsoft.com/Forums/office/en-US/39f24813-1a8c-440e-87af-9ded825dbfaf/sharepoint-2013-on-premise-known-issues-with-any-recent-cu?forum=sharepointadmin

  7. Ninja says:

    Hi Stefan,
    Is there any known issue reported in November 2016 CU for SharePoint 2013 ?

    1. Ninja says:

      Hi Stefan,

      Please confirm if anyone has noticed any known issue reported by MS or Users ? we need to propose this CU upgrade to our customer , therefore we need confirmation if its safe to go with the Nov CU ?

      1. Hi Ninja,
        sorry but that will not work as we usually have several issue reported for each CU but each of them only affects a small amount of customers.
        You need to evaluate the CU in your test environment and verify if your specific application behaves correct.
        Cheers,
        Stefan

Skip to main content