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

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

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

  • KB 4464560 – SharePoint Foundation 2013 May 2019 CU
  • KB 4464563 – SharePoint Server 2013 May 2019 CU
  • KB 4464562 – Project Server 2013 May 2019 CU
  • There was no fix released for Office Web Apps Server 2013 this month

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

After installing the fixes you need to run the SharePoint 2019 Products Configuration Wizard on each machine in the farm. If you prefer to run the command line version psconfig.exe ensure to have a look here for the correct Options.

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:

17 Comments


  1. Hi Stefan,

    Will it cover the patches for recent security vulnerablility ?

    Reply

  2. Hi Stefan, I installed May 2019 CU but, on the Central Admin, I see the build number 15.0.5131.100 instead of ​15.0.5137.1000.
    Is it correct?
    thank you

    Reply

    1. Hi Christian,
      where in the central admin do you see this?
      Thanks,
      Stefan

      Reply

      1. Hi Stefan,
        in the central Admin – Manage server in this farm page, and also running this powershell command
        $farm = Get-SPFarm
        $farm.BuildVersion

        thank you

        Reply

  3. While Installation the CU we’re getting the Error “Windows Installer installed an update. Product Name: Microsoft SharePoint Portal. Product Version: 15.0.4571.1502. Product Language: 0. Manufacturer: Microsoft Corporation. Update Name: Update for Microsoft SharePoint Enterprise Server 2013 (KB4464563) 64-Bit Edition. Installation success or error status: 1603.” for some components. The bad part is that this issue happens on some servers but not all of the farm. And it only appeared after we reached production – Test and QS/Staging went fine 🙁

    Reply

      1. Hi, thanks for the lightning fast reply. I’ve checked all listet issues and everything is fine. The update is on a fixed local drive, no encryption and the system account has full control. And since this is an CU i think i can skip “•Windows Installer is attempting to install an app that is already installed on your PC.” or did i miss something there?

        Reply

        1. I assume not. As this is a Windows Installer issue and not a SharePoint issue I would recommend to open a support ticket with Microsoft to get this analyzed.

          Reply

          1. I think i found the issue. We used to stop all Sharepoint related services which includes the W3SVC service and set the starttype to disabled, since that speeds up the CU Installation a lot – the updater fails because it wants to start the W3SVC and since its set to disabled it can not do that. After switching the starttype of the W3SVC and IISADMIN Service to Automatic the Update Installation worked.


  4. Hello Stefan,
    Several years ago, you wrote an article which I found very helpful https://blog.stefan-gossner.com/2013/03/21/common-question-what-is-the-difference-between-a-pu-a-cu-and-a-cod/

    This article does not mention uber packages. Does Microsoft have any official position in regards to “when to install” uber package? aka do you recommend to install uber-packages as they are released or only if you affected by specific issue fixed by uber? One other related question, do you need to maintain certain patch level in order to have a ‘supported configuration’ e.g you need to open a case with MS?

    Thank you, for the great blog posts!

    Cheers,
    Fedor

    Reply

    1. Hi Fedor,
      the links in this article point to the Uber packages of the CU.
      I do not link to individual fixes as it is far to complex to maintain those fixes.
      The only exception are security fixes which I highlight in a separate blog post each month.
      Cheers,
      Stefan

      Reply

      1. My company is currently updating Sharepoint patch strategy. We are installing PU (security fixes as soon as they are released via WSUS, however we would like to have more control over CU and uber packages)

        My questions are:
        – does Microsoft have any official position in regards to “when to install” uber package? aka do you recommend to install uber-packages as they are released or only if you affected by specific issue fixed by uber?

        Do you need to maintain certain patch level in order to have a ‘supported configuration’ e.g you need to open a case with MS

        Thank you,
        Fedor

        Reply

        1. Hi Fedor,
          we recommend to evaluate and install Uber packages every couple of months as we no longer release service packs.
          The minimum supported patch level to open support tickets for SharePoint 2013 with Microsoft is April 2018 CU.
          Cheers,
          Stefan

          Reply

  5. After I install May CU updates on SP2013. I am getting an issue with InfoPath Forms. Forms are not opening. It always showing “Loading” message. And I found some error on ULS logs. Please help me


    06/13/2019 20:10:37.27 w3wp.exe (0x3A4C) 0x3B0C SharePoint Foundation Upgrade ajyw6 High 06/13/2019 20:10:37.27 w3wp (0x3A4C) 0x3B0C SharePoint Foundation Upgrade SPHierarchyManager ajyw6 DEBUG [SPTree Value=SPConfigurationDatabase] added to dependency cache by lookup 00000000-0000-0000-0000-000000000000
    06/13/2019 20:10:37.27 w3wp.exe (0x3A4C) 0x3B0C SharePoint Foundation Upgrade ajyx0 High 06/13/2019 20:10:37.27 w3wp (0x3A4C) 0x3B0C SharePoint Foundation Upgrade SPDelegateManager ajyx0 DEBUG Waiting for mutex to initialize type dictionary 00000000-0000-0000-0000-000000000000
    06/13/2019 20:10:37.27 w3wp.exe (0x3A4C) 0x3B0C SharePoint Foundation Upgrade ajyx1 High 06/13/2019 20:10:37.27 w3wp (0x3A4C) 0x3B0C SharePoint Foundation Upgrade SPDelegateManager ajyx1 DEBUG Obtained mutex 00000000-0000-0000-0000-000000000000
    06/13/2019 20:10:37.27 w3wp.exe (0x3A4C) 0x3B0C SharePoint Foundation Upgrade ajyx2 High 06/13/2019 20:10:37.27 w3wp (0x3A4C) 0x3B0C SharePoint Foundation Upgrade SPDelegateManager ajyx2 DEBUG Registering assemblies and sequences 00000000-0000-0000-0000-000000000000
    06/13/2019 20:10:37.27 w3wp.exe (0x3A4C) 0x3B0C SharePoint Foundation Upgrade ajyx8 High 06/13/2019 20:10:37.27 w3wp (0x3A4C) 0x3B0C SharePoint Foundation Upgrade SPDelegateManager ajyx8 DEBUG Begin registering Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c. 00000000-0000-0000-0000-000000000000
    06/13/2019 20:10:37.27 w3wp.exe (0x3A4C) 0x3B0C SharePoint Foundation Upgrade ajyx9 High 06/13/2019 20:10:37.27 w3wp (0x3A4C) 0x3B0C SharePoint Foundation Upgrade SPDelegateManager ajyx9 DEBUG Using assembly manifest Microsoft.SharePoint.UpgradeAssemblyManifest. 00000000-0000-0000-0000-000000000000
    06/13/2019 20:10:37.27 w3wp.exe (0x3A4C) 0x3B0C SharePoint Foundation Upgrade ajyyp High 06/13/2019 20:10:37.27 w3wp (0x3A4C) 0x3B0C SharePoint Foundation Upgrade SPDelegateManager ajyyp DEBUG Registering [Microsoft.SharePoint.Upgrade.AppManagementServiceApplicationSequence] for [Microsoft.SharePoint.AppManagement.AppManagementServiceApplication], Phase: 2147483647, Order: 0. 00000000-0000-0000-0000-000000000000
    06/13/2019 20:10:37.28 w3wp.exe (0x3A4C) 0x3B0C SharePoint Foundation Upgrade ajyyp High 06/13/2019 20:10:37.28 w3wp (0x3A4C) 0x3B0C SharePoint Foundation Upgrade SPDelegateManager ajyyp DEBUG Registering [Microsoft.SharePoint.Upgrade.AppManagementServiceDatabaseSequence] for [Microsoft.SharePoint.AppManagement.AppManagementServiceDatabase], Phase: 2147483647, Order: 0. 00000000-0000-0000-0000-000000000000
    06/13/2019 20:10:37.28 w3wp.exe (0x3A4C) 0x3B0C SharePoint Foundation Upgrade ajyyp High 06/13/2019 20:10:37.28 w3wp (0x3A4C) 0x3B0C SharePoint Foundation Upgrade SPDelegateManager ajyyp DEBUG Registering [Microsoft.SharePoint.BusinessData.Upgrade.BdcServiceApplicationSequence] for [Microsoft.SharePoint.BusinessData.SharedService.BdcServiceApplication], Phase: 2147483647, Order: 0. 00000000-0000-0000-0000-000000000000
    06/13/2019 20:10:37.28 w3wp.exe (0x3A4C) 0x3B0C SharePoint Foundation Upgrade ajyyp High 06/13/2019 20:10:37.28 w3wp (0x3A4C) 0x3B0C SharePoint Foundation Upgrade SPDelegateManager ajyyp DEBUG Registering [Microsoft.SharePoint.BusinessData.Upgrade.BusinessDataCatalogDatabaseSequence] for [Microsoft.SharePoint.BusinessData.SharedService.BdcServiceDatabase], Phase: 2147483647, Order: 0. 00000000-0000-0000-0000-000000000000
    06/13/2019 20:10:37.28 w3wp.exe (0x3A4C) 0x3B0C SharePoint Foundation Upgrade ajyyp High 06/13/2019 20:10:37.28 w3wp (0x3A4C) 0x3B0C SharePoint Foundation Upgrade SPDelegateManager ajyyp DEBUG Registering [Microsoft.SharePoint.Upgrade.SPConfigurationDatabaseSequence] for [Microsoft.SharePoint.Administration.SPConfigurationDatabase], Phase: 0, Order: 0. 00000000-0000-0000-0000-000000000000
    06/13/2019 20:10:37.28 w3wp.exe (0x3A4C) 0x3B0C SharePoint Foundation Upgrade ajyyp High 06/13/2019 20:10:37.28 w3wp (0x3A4C) 0x3B0C SharePoint Foundation Upgrade SPDelegateManager ajyyp DEBUG Registering [Microsoft.SharePoint.Upgrade.SPConfigurationDatabaseSequence2] for [Microsoft.SharePoint.Administration.SPConfigurationDatabase], Phase: 1, Order: 0. 00000000-0000-0000-0000-000000000000
    06/13/2019 20:10:37.28 w3wp.exe (0x3A4C) 0x3B0C SharePoint Foundation Upgrade ajyyp High 06/13/2019 20:10:37.28 w3wp (0x3A4C) 0x3B0C SharePoint Foundation Upgrade SPDelegateManager ajyyp DEBUG Registering [Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence] for [Microsoft.SharePoint.Administration.SPContentDatabase], Phase: 0, Order: 0. 00000000-0000-0000-0000-000000000000
    06/13/2019 20:10:37.28 w3wp.exe (0x3A4C) 0x3B0C SharePoint Foundation Upgrade ajyyp High 06/13/2019 20:10:37.28 w3wp (0x3A4C) 0x3B0C SharePoint Foundation Upgrade SPDelegateManager ajyyp DEBUG Registering [Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence2] for [Microsoft.SharePoint.Administration.SPContentDatabase], Phase: 1, Order: 0. 00000000-0000-0000-0000-000000000000
    06/13/2019 20:10:37.28 w3wp.exe (0x3A4C) 0x3B0C SharePoint Foundation Upgrade ajyyp High 06/13/2019 20:10:37.28 w3wp (0x3A4C) 0x3B0C SharePoint Foundation Upgrade SPDelegateManager ajyyp DEBUG Registering [Microsoft.SharePoint.Upgrade.SPPrejoinedFarmSequence] for [Microsoft.SharePoint.Administration.SPPrejoinedFarm], Phase: 2147483647, Order: 0. 00000000-0000-0000-0000-000000000000
    06/13/2019 20:10:37.28 w3wp.exe (0x3A4C) 0x3B0C SharePoint Foundation Upgrade ajyyp High 06/13/2019 20:10:37.28 w3wp (0x3A4C) 0x3B0C SharePoint Foundation Upgrade SPDelegateManager ajyyp DEBUG Registering [Microsoft.SharePoint.Upgrade.SPFarmSequence] for [Microsoft.SharePoint.Administration.SPFarm], Phase: 2147483647, Order: 0. 00000000-0000-0000-0000-000000000000
    06/13/2019 20:10:37.28 w3wp.exe (0x3A4C) 0x3B0C SharePoint Foundation Upgrade ajyyp High 06/13/2019 20:10:37.28 w3wp (0x3A4C) 0x3B0C SharePoint Foundation Upgrade SPDelegateManager ajyyp DEBUG Registering [Microsoft.SharePoint.Upgrade.SPFarmSequence2] for [Microsoft.SharePoint.Administration.SPFarm], Phase: 1, Order: 0. 00000000-0000-0000-0000-000000000000
    06/13/2019 20:10:37.28 w3wp.exe (0x3A4C) 0x3B0C SharePoint Foundation Upgrade ajyyp High 06/13/2019 20:10:37.28 w3wp (0x3A4C) 0x3B0C SharePoint Foundation Upgrade SPDelegateManager ajyyp DEBUG Registering [Microsoft.SharePoint.Upgrade.SPIisWebSiteWssSequence] for [Microsoft.SharePoint.Administration.SPIisWebSite], Phase: 2147483647, Order: 0. 00000000-0000-0000-0000-000000000000
    06/13/2019 20:10:37.28 w3wp.exe (0x3A4C) 0x3B0C SharePoint Foundation Upgrade ajyyp High 06/13/2019 20:10:37.28 w3wp (0x3A4C) 0x3B0C SharePoint Foundation Upgrade SPDelegateManager ajyyp DEBUG Registering [Microsoft.SharePoint.Upgrade.SPServerSequence] for [Microsoft.SharePoint.Administration.SPServer], Phase: 2147483647, Order: 0. 00000000-0000-0000-0000-000000000000
    06/13/2019 20:10:37.28 w3wp.exe (0x3A4C) 0x3B0C SharePoint Foundation Upgrade ajyyp High 06/13/2019 20:10:37.28 w3wp (0x3A4C) 0x3B0C SharePoint Foundation Upgrade SPDelegateManager ajyyp DEBUG Registering [Microsoft.SharePoint.Upgrade.SPServiceSequence] for [Microsoft.SharePoint.Administration.SPService], Phase: 2147483647, Order: 0. 00000000-0000-0000-0000-000000000000
    06/13/2019 20:10:37.28 w3wp.exe (0x3A4C) 0x3B0C SharePoint Foundation Upgrade ajyyp High 06/13/2019 20:10:37.28 w3wp (0x3A4C) 0x3B0C SharePoint Foundation Upgrade SPDelegateManager ajyyp DEBUG Registering [Microsoft.SharePoint.Upgrade.SPServiceInstanceSequence] for [Microsoft.SharePoint.Administration.SPServiceInstance], Phase: 2147483647, Order: 0. 00000000-0000-0000-0000-000000000000
    06/13/2019 20:10:37.28 w3wp.exe (0x3A4C) 0x3B0C SharePoint Foundation Upgrade ajyyp High 06/13/2019 20:10:37.28 w3wp (0x3A4C) 0x3B0C SharePoint Foundation Upgrade SPDelegateManager ajyyp DEBUG Registering [Microsoft.SharePoint.Upgrade.SPWebTemplateSequenceForSite] for [Microsoft.SharePoint.SPSite], Phase: -1, Order: 0. 00000000-0000-0000-0000-000000000000
    06/13/2019 20:10:37.28 w3wp.exe (0x3A4C) 0x3B0C SharePoint Foundation Upgrade ajyyp High 06/13/2019 20:10:37.28 w3wp (0x3A4C) 0x3B0C SharePoint Foundation Upgrade SPDelegateManager ajyyp DEBUG Registering [Microsoft.SharePoint.Upgrade.SPSiteWssSequence] for [Microsoft.SharePoint.SPSite], Phase: 0, Order: 0. 00000000-0000-0000-0000-000000000000
    06/13/2019 20:10:37.28 w3wp.exe (0x3A4C) 0x3B0C SharePoint Foundation Upgrade ajyyp High 06/13/2019 20:10:37.28 w3wp (0x3A4C) 0x3B0C SharePoint Foundation Upgrade SPDelegateManager ajyyp DEBUG Registering [Microsoft.SharePoint.Upgrade.SPSiteWssSequence2] for [Microsoft.SharePoint.SPSite], Phase: 1, Order: 0. 00000000-0000-0000-0000-000000000000
    06/13/2019 20:10:37.28 w3wp.exe (0x3A4C) 0x3B0C SharePoint Foundation Upgrade ajyyp High 06/13/2019 20:10:37.28 w3wp (0x3A4C) 0x3B0C SharePoint Foundation Upgrade SPDelegateManager ajyyp DEBUG Registering [Microsoft.SharePoint.Upgrade.SPWebTemplateSequenceForWeb] for [Microsoft.SharePoint.SPWeb], Phase: -1, Order: 0. 00000000-0000-0000-0000-000000000000
    06/13/2019 20:10:37.28 w3wp.exe (0x3A4C) 0x3B0C SharePoint Foundation Upgrade ajyyp High 06/13/2019 20:10:37.28 w3wp (0x3A4C) 0x3B0C SharePoint Foundation Upgrade SPDelegateManager ajyyp DEBUG Registering [Microsoft.SharePoint.Upgrade.SPWebWssSequence] for [Microsoft.SharePoint.SPWeb], Phase: 0, Order: 0. 00000000-0000-0000-0000-000000000000
    06/13/2019 20:10:37.28 w3wp.exe (0x3A4C) 0x3B0C SharePoint Foundation Upgrade ajyyp High 06/13/2019 20:10:37.28 w3wp (0x3A4C) 0x3B0C SharePoint Foundation Upgrade SPDelegateManager ajyyp DEBUG Registering [Microsoft.SharePoint.Upgrade.SPWebWssSequence2] for [Microsoft.SharePoint.SPWeb], Phase: 1, Order: 0. 00000000-0000-0000-0000-000000000000
    06/13/2019 20:10:37.28 w3wp.exe (0x3A4C) 0x3B0C SharePoint Foundation Upgrade ajyyp High 06/13/2019 20:10:37.28 w3wp (0x3A4C) 0x3B0C SharePoint Foundation Upgrade SPDelegateManager ajyyp DEBUG Registering [Microsoft.SharePoint.Upgrade.SPSubscriptionSettingsServiceApplicationSequence] for [Microsoft.SharePoint.SPSubscriptionSettingsServiceApplication], Phase: 2147483647, Order: 0. 00000000-0000-0000-0000-000000000000
    06/13/2019 20:10:37.28 w3wp.exe (0x3A4C) 0x3B0C SharePoint Foundation Upgrade ajyyp High 06/13/2019 20:10:37.28 w3wp (0x3A4C) 0x3B0C SharePoint Foundation Upgrade SPDelegateManager ajyyp DEBUG Registering [Microsoft.SharePoint.Upgrade.SPSubscriptionSettingsDatabaseSequence] for [Microsoft.SharePoint.SPSubscriptionSettingsDatabase], Phase: 2147483647, Order: 0. 00000000-0000-0000-0000-000000000000
    06/13/2019 20:10:37.28 w3wp.exe (0x3A4C) 0x3B0C SharePoint Foundation Upgrade ajyyp High 06/13/2019 20:10:37.28 w3wp (0x3A4C) 0x3B0C SharePoint Foundation Upgrade SPDelegateManager ajyyp DEBUG Registering [Microsoft.SharePoint.Upgrade.SPUsageApplicationSequence] for [Microsoft.SharePoint.Administration.SPUsageApplication], Phase: 2147483647, Order: 0. 00000000-0000-0000-0000-000000000000
    06/13/2019 20:10:37.28 w3wp.exe (0x3A4C) 0x3B0C SharePoint Foundation Upgrade ajyyp High 06/13/2019 20:10:37.28 w3wp (0x3A4C) 0x3B0C SharePoint Foundation Upgrade SPDelegateManager ajyyp DEBUG Registering [Microsoft.SharePoint.Upgrade.SPUsageDatabaseSequence] for [Microsoft.SharePoint.Administration.SPUsageDatabase], Phase: 2147483647, Order: 0. 00000000-0000-0000-0000-000000000000
    06/13/2019 20:10:37.28 w3wp.exe (0x3A4C) 0x3B0C SharePoint Foundation Upgrade ajyyp High 06/13/2019 20:10:37.28 w3wp (0x3A4C) 0x3B0C SharePoint Foundation Upgrade SPDelegateManager ajyyp DEBUG Registering [Microsoft.SharePoint.Upgrade.SPWebApplicationSequence] for [Microsoft.SharePoint.Administration.SPWebApplication], Phase: 2147483647, Order: 0. 00000000-0000-0000-0000-000000000000

    Reply

    1. Hi Prasad,
      if you need assistance please open a ticket with Microsoft Support.
      Thanks,
      Stefan

      Reply

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.