SharePoint 2013 May 2018 CU


Our SharePoint product group released the next monthly cumulative updates. How patching works for SharePoint 2013? Read more in the post from my colleague Stefan.

Since April 2015:

  • You need to have SP1 installed!

  • In case you have installed a SP1 slipstream version, please read the article from my colleague Stefan!!!
  • Search enabled Farm, please check as well this article.

The format how we are providing the Cumulative Update packages has changed in 2015, means you can find all packages on our Download Center.

When you reached the download website, it is independent which language you chose, the packages are the same.

Plan to upgrade carefully, you may need more time in case the current patch level for your Farm is June 2015 or earlier! Reason is in regards to Search and psconfig. Please check the post from my colleague Stefan!

SharePoint Foundation 2013
4018394 The full server package for SharePoint Foundation 2013
https://support.microsoft.com/en-us/help/4018394

Download link: https://www.microsoft.com/en-us/download/details.aspx?id=56921

SharePoint Server 2013
4018397 The full server package for SharePoint Server 2013 and contains also the SharePoint Foundation 2013 fixes so you need only this package.
https://support.microsoft.com/en-us/help/4018397

Download link: https://www.microsoft.com/en-us/download/details.aspx?id=56886

Office Web Apps Server 2013
4018393 The full server package for OWAS 2013
https://support.microsoft.com/en-us/help/4018393

Download link: https://www.microsoft.com/en-us/download/details.aspx?id=56930

Project Server 2013
4018395 The full server package for Project Server 2013 and contains also the SharePoint Server and Foundation 2013 fixes so you need only this package.
https://support.microsoft.com/en-us/help/4018395

Download link: https://www.microsoft.com/en-us/download/details.aspx?id=56943

Important for all Server Applications listed above:
After any binary update you need to run psconfig or psconfigui. Please refer to the following article to find out what is the best for you: why-i-prefer-psconfigui-exe-over-psconfig-exe.aspx

You might have you own strategy to run psconfig, because it depends on the farm structure and what makes sense to reduce the downtime.

Regarding PSConfig: With August 2016 CU for SharePoint Server 2016 we updated psconfig with a couple of improvements, discussed in my colleagues blog post:

The news are that these improvements are now available with this December update also for SharePoint Server 2013.

As soon as possible (in case patch level of your Farm is June 2015 or earlier) after you installed the binaries, run the psconfig! Reasons are here.

Related Info:

Update Center for Microsoft Office, Office Servers, and Related Products

Common Question: What is the difference between a PU, a CU and a COD?

How to: install update packages on a SharePoint 2013 farm where search component and high availability search topologies are enabled

CHANGE: SharePoint 2013 Rollup Update for the December 2013 Cumulative Update Packaging

SQL Server 2014 and SharePoint Server 2013

Comments (4)

  1. billy says:

    Hi Joerg,

    I came across a very weird issue related to this May CU. After installing this CU on my Dev Box, the build number is changed to 15.0.5023.1000. As you see, the build number is April CU, 2018.

    In UAT, I haven’t installed this CU yet. However in this box the latest security patches (KB4018390, KB4018398) have been applied. After running PSConfig, the build number is upgraded to 15.0.5023.1000 too.

    I checked the dll (Microsoft.SharePoint.dll). The modified date is 4/11/2018. The product version on this dll is 15.0.5023.1000.

    I just wonder if this CU is stable and how can I get clear answer from Microsoft?

    Thanks a lot for your help in advance,

    Billy

    1. Regarding build numbers: Please check: https://thesharepointfarm.com/2016/04/sharepoint-server-2016-patch-build-numbers-module/

      Regarding Security Update or Full-Server packages?
      https://blogs.msdn.microsoft.com/joerg_sinemus/2015/03/12/sharepoint-2013-and-march-2015-experience-regarding-windows-update/
      Also a security update might update the database schema, but we always suggest to install full-server packages, makes less head-age when troubleshooting farms not fully updated.

      1. billy says:

        Hi Joerg,

        Thanks for your reply.

        Let me explain a little more. Thanks for your patience.

        Actually I had successfully installed May CU 2018 of SharePoint 2013 on my Dev Box. The build number is supposed to be 15.0.5031.1000. But I got 15.0.5023.1000.

        I suspect there is a bug with this May CU 2018. The Microsoft.SharePoint.dll’s version may be incorrect.

        Thanks,
        Billy

        Get-SPProductInformation Results:

        Microsoft SharePoint Foundation 2013 Core Yes Update for Microsoft SharePoint Enterprise Server 2013 (KB4018397) 64-Bit Edition 15.0.5031.1000 https://support.microsoft.com/kb/4018397
        Microsoft SharePoint Foundation 2013 1033 Lang Pack Yes Update for Microsoft SharePoint Enterprise Server 2013 (KB4018397) 64-Bit Edition 15.0.5031.1000 https://support.microsoft.com/kb/4018397

        1. billy says:

          Hi Joerg,

          Today I happened to read Stefan’s two articles (see below) again. This time I have clear understanding about the difference between farm builder version and CU patch version. So I am confident to move forward with May CU 2018 of SharePoint 2013 and install them into UAT and Prod.

          Many thanks for your help and any more comments.
          Billy

          https://blogs.technet.microsoft.com/stefan_gossner/2016/08/23/sharepoint-does-not-have-a-build-version-full-stop/
          https://blogs.technet.microsoft.com/stefan_gossner/2014/08/18/sharepoint-patching-demystified/

Skip to main content