May 2018 CU for SharePoint 2013 product family is available for download


The product group released the May 2018 Cumulative Update for the SharePoint 2013 product family.

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

  • KB 4018394 - SharePoint Foundation 2013 May 2018 CU
  • KB 4018397 - SharePoint Server 2013 May 2018 CU
  • KB 4018395 - Project Server 2013 May 2018 CU
  • KB 4018393 - Office Web Apps Server 2013 in May 2018 CU - This is also a security update!

The Full Server Packages for May 2018 CU are available through the following links:

Important: If your farm has been on a patch level lower than July 2015 CU ensure to read the following blog post:
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 2013 CU. And the Project Server 2013 CU also contains the SharePoint Server 2013 CU and SharePoint Foundation 2013 CU.

Related Info:

Comments (5)

  1. Hi Stefen,
    MAY 2018 CU has important FIX for MARCH 2018 Security update as below,
    • After you install the security update for SharePoint Foundation 2013 (KB3172540), SharePoint Server 2013 is in an inconsistent state.

    Since March 2018 updates are part of APR 2018 CU, are we still good to proceed with Apr 2018 update?
    I have a plan to deploy Apr 2018 CU update to my farm. The word “inconsistent state” is creating concern for me to proceed with.

    Please share your thoughts and clarify.

    1. Hi Chandru,
      the issue is the one I discussed here including workaround:
      https://blogs.technet.microsoft.com/stefan_gossner/2018/03/29/common-problem-with-march-2018-security-fixes-for-sharepoint-2013-accesskey-too-long-cannot-be-more-than-one-character/
      The fix in May will prevent the stale .NET cache during fix installation.
      Cheers,
      Stefan

      1. PoWaShell says:

        Hi Stefan,

        To clarify, if I patch with CU April 2018 full server package I should be ok and will not be required to perform the workaround detailed in https://blogs.technet.microsoft.com/stefan_gossner/2018/03/29/common-problem-with-march-2018-security-fixes-for-sharepoint-2013-accesskey-too-long-cannot-be-more-than-one-character/ – correct?

        Paul

        1. Hi Paul,
          no – the fix is in May PU – not in April PU. So with April you should also clear the Temporary ASP.NET Files folder on each SharePoint machine.
          Cheers,
          Stefan

          1. PoWaShell says:

            Good to know, thanks!

            Paul

Skip to main content