June 2017 CU for SharePoint 2013 product family is available for download

The product group released the June 2017 Cumulative Update for the SharePoint 2013 product family.

For June 2017 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, June 2017 CU includes all fixes from June 2017 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).

This CU fixes the regression introduced in March 2017 CU and March 2017 PU (MS17-14) which prevents opening Word documents via Office Web Application Server if they are contained in sites with spaces in their names

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 June 2017 CU should be available at the following locations in a couple of hours:

  • KB 3203428 – SharePoint Foundation 2013 June 2017 CU
  • KB 3203430 – SharePoint Server 2013 June 2017 CU
  • KB 3203429 – SharePoint Server 2013 with Project Server June 2017 CU
  • KB 3203391 – Office Web Apps Server 2013 June 2017 CU – this is also a security update!

The Full Server Packages for June 2017 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 (15)

  1. FeytensJ says:

    Hi Stefan,

    Is the documentation complete?
    Can it be that there is only one server fix in this CU for SP2013?
    And I cannot find the description of the bug which prevents opening Word documents via Office Web Application Server if they are contained in sites with spaces in their names.



    1. Hi Feytens,
      the issue you are talking about was already fixed with April CU so it is not listed in the fixes in June CU.
      The following KB contains the documentation of the issue:

  2. themush1326 says:

    Any comments on 3203387? Seems like a very large security update.

    Is the June 2017 CU considered a critical update or just a normal CU?

    1. 3203387 is a security fix which is included in the CU.
      Each month we release security fixes and a CU. Customers can decide whether they would like to install the complete CU or only the security fixes.

      1. themush1326 says:

        Is there anything critical or different about this CU then any other one?
        If 3203387 is installed then are there are any other security patches for SharePoint needed?

          1. themush1326 says:

            thanks, I am aware of those, 3203387 plus the ones in the update guide
            My confusion was if I need June 2017 for security vulnerabilities in addition to the security patches released this month

          2. The security fixes are always sufficient to fix security vulnerabilities. The CU potentially contains additional non-security fixes not included in the security fixes.

  3. Hi Stefan – Regarding Office Web Apps 2013 PUs and CUs : Is there a requirement or recommendation to have the PU/CU versions of SharePoint 2013 and Office Web Apps 2013 be in sync ? For example, is it OK to run Office Web Apps Server 2013 with June 2017 CU installed, and run SharePoint 2013 with a CU older than June 2017 CU (say the Jan 2017 CU) installed ? Appreciate your feedback !

    1. Hi Mario,
      in general these are two differnet products and patching does not have to be completely in sync from a support perspective.
      On the other hand some fixes have to be implemented as well on the Office Web Apps side and on the SharePoint side and they will not work correctly if the patch level is different.
      So the recommendation would be to keep them in sync.

  4. Shane O says:

    Still having an issue that i believe started with the Nov 2016 CU.
    Iframe embeds do not preview/render (e.g. youtube video share)

    Could this be related to the Chrome rich text editor fixes that Nov CU introduced?

  5. Charls says:

    Hi Stefan,

    Installed this CU but database version is showing 15.0.4935.1000 opposed to 15.0.4937.100. Also I can see that with 15.0.4935.1000, one security vulnerability isn’t fixed.

    P.S: Upgrade status shows ‘Upgrade available’


    1. Charls says:

      I was able to run PSConfig to change status to ‘No Action Required’, still build number is 15.0.4935.1000

      1. Hi Charls,
        as SharePoint does not have a single build number I need to have more information. Where do you see this number?

    2. Hi Charls,
      the database schema version is not a build number. And the database schema is not changed with every CU or every build.
      You cannot expect that the database schema version is identical to the highest build number of SharePoint.
      See here for details:

Skip to main content