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


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

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

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

  • KB 3178727 – SharePoint Foundation 2013 April 2017 CU
  • KB 3178730 – SharePoint Server 2013 April 2017 CU
  • KB 3178728 – SharePoint Server 2013 with Project Server April 2017 CU
  • KB 3178725 – Office Web Apps Server 2013 April 2017 CU – this is also a security update!

The Full Server Packages for April 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 (13)

  1. It is a good news, a lot of thanks

  2. Brad says:

    Hi Stefan,

    We applied the April CU updates to our dev environment this AM and it looks like it doesn’t resolve the issue with documents being opened in Office web apps within sites with spaces. It also now presents this issue to sites without spaces.

    1. Hi Brad,
      sounds like a different issue. You might want to open a support case with Microsoft to check what is wrong in your environment.
      Cheers,
      Stefan

  3. Mitchell says:

    If we are experiencing the OWA issue “sites with spaces in their names” can we patch just the OWA server with the CU until we can patch the rest of the servers in the farm or does this require patching the entire farm and OWA to resolve? We have a lengthy procedure for getting patches approved and if we can get away with patching OWA that would be our quickest route to resolution until we can patch the entire farm.

    1. Hi Mitchell, the main fix is in Sharepoint. So fixing owa alone will not help.

      1. Mitchell says:

        Thanks for confirming. Much appreciated.

        1. Sikander says:

          I’ve applied the April’17 CU patch on SharePoint it seems documents are now working fine with spaces urls

          Thanks

  4. MahmudDev says:

    Hi Stefan,
    Today we did CU update ( Security Update for Microsoft SharePoint Enterprise Server 2013 (KB3178724) 64-Bit Edition) in Dev and Production.

    Here is couple of confusion we have:
    -In patch status page, we find the patch is installed and the version is 15.0.4919.1000 for both Dev and production.
    -After running ps config, the production Configuration database version: 15.0.4919.1000. But the dev still have old version 15.0.4841.1000.
    I run PS configure couple of time but didn’t change in dev .

    Note : After installing CU updates in production, It said “Update Required” but In development server , it said “No action required”. I am really confused what went wrong at this point.

    Any suggestion from you would be highly appreciated!

    Thank you!

    1. Hi Mahmud,
      did you install the identical fixes in both farms?
      Please try to apply the Uber package from the following link:
      http://www.microsoft.com/en-us/download/details.aspx?id=55086
      If this does not help I would recommend to open a support case with Microsoft.
      Cheers,
      Stefan

  5. ScottSwann says:

    After Upgrading to the April 2017 CU for SharePoint 2013 we had two issues come up. On both IE 11 and Chrome on the main landing site after the upgrade we are receiving two different javascript errors that did not appear before(Feb 2016 CU). The errors are “Uncaught SyntaxError: Invalid or unexpected token in strings.js” and “Uncaught TypeError: Cannot read property ‘toString’ of undefined” in init.js. We also are using the peoplepicker in 3rd party application that we have been using for over 1 year and after the upgrade when we start typing one letter in the peoplepicker we receive the avascript error “Uncaught TypeError: Cannot read property ‘replace’ of undefined” and the peoplepicker no longer searches and finds a user because of the error. Not sure what to do now.

    Scott

    1. Hi Scott,
      if you need assistance on this I would suggest to open a support ticket with Microsoft to get this analyzed.
      Cheers,
      Stefan

  6. joerg says:

    Hi Stefan,

    do you know if the task list search bug (see January CU for SharePoint 2013 Discussion in this blog) is fixed in the April CU? It was mentioned that the April CU was the earliest to include the fix.

    1. Hi Joerg,
      the fix for this issue is currently planned for May CU.
      Cheers,
      Stefan

Skip to main content