April 2014 CU for SharePoint 2013 has finally been released

- - 78 Comments

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

ATTENTION:

Be aware that all Update for SharePoint 2013 require SharePoint Server 2013 SP1 OR March 2013 PU for SharePoint 2013 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.

The KB articles for April CU will be available at the following locations in a couple of days:

  • KB 2863892 – SharePoint Foundation 2013 April 2014 CU
  • KB 2878240 – SharePoint Server 2013 April 2014 CU
  • KB 2880484 – SharePoint Server 2013 with Project Server April 2014 CU
  • KB 2863899 – Office Web Apps Server 2013 – be aware that Office Web Apps Server 2013 fixes will be released with a different cadence to SharePoint in the future.

The Full Server Packages for April 2014 CU are available through the following links:

After installing the fixes you need to run the SharePoint 2013 Products Configuration Wizard on each machine in the farm.

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:

78 Comments


  1. The product group released the April 2014 Cumulative Update for the SharePoint 2013 product family. ATTENTION

    Reply

  2. Hi Stefan,

    Do you have any more info about the support of SQL Server 2012 AlwaysOn Availability Groups Readable secondary with April 2014 CU. Its written to this article at tech-net http://technet.microsoft.com/en-us/library/jj715261.aspx

    "Readable secondary replicas are supported for runtime usage if you install the SharePoint 2013 April 2014 cumulative update (CU) package or better."

    Regards,
    Mahmoud Hamed

    Reply

  3. Hi Mahmoud,

    sorry – I don’t have more info as written in this article.

    Cheers,
    Stefan

    Reply

  4. Thanks Stefan! Though I believe you have the download URLs for Server and Project reversed 🙂

    Cheers
    Brian

    Reply

  5. Thanks Brian, its fixed now.

    Reply

  6. I was just say the same thing, Brian. Stefan, are the KBs not out yet?

    Reply

  7. Hi Todd,
    the KBs are not yet published. Should be avail in a couple of days as usual.

    Cheers,
    Stefan

    Reply

  8. Pingback from April 2014 CU for SharePoint 2013 has finally been released | MS Tech BLOG

    Reply

  9. Thanks Stefan. Wow those are three big files to download 😉 Cheers

    Reply

  11. It got published. I noticed it's called "May CU", not April CU or May PU. Is it a mistake or did the release schedule change?
    Also the prerequisites section does not mention SP1, only March PU. Does that mean I can install it right on top of March PU without bothering with SP1? Does that mean that SP1 is not the baseline version?

    Reply

  12. Hi Piotr,
    its not named May CU. It is a CU released on May 7th but it is the delayed April CU. It was delayed due to the re-release of SP1 and that caused it to slip into May.
    May CU is expected to release next week but only for Office client and WAC as these products have a different release cadence than SharePoint.
    Cheers,
    Stefan

    Reply

  13. Hi Piotr,
    regarding the baseline: our CUs always support the previous Service Pack (or RTM in this case) for 12 months after release of a service pack.
    So the baseline of this CU is March 2013 PU and SP1.
    Cheers,
    Stefan

    Reply

  14. > its not name May CU. It is a CU released on May 7th.

    In that case MS should spend some serious time thinking about its naming standards. Having a Title "Cumulative update package for SharePoint Foundation 2013 (SharePoint Foundation server-package): May 7, 2014" and a release date of the 9th of May 2014 for ver 1.0 doesn't by any stretch of the imagination indicate that this is an April CU.

    Reply

  15. Hi Mike,
    just read my blog and you are up to date. 😉
    Cheers,
    Stefan

    Reply

  16. Thanks Stefan! Does the April CU include SP1? If not I'm assuming once you install the April CU you can go back and install SP1 afterwards?

    Reply

  17. Pingback from April 2014 CU for SharePoint 2013 has been released | DeepInSharePoint

    Reply

  18. Pingback from Fix Custom Access Denied Page in SharePoint 2013 | DeepInSharePoint

    Reply

  19. Hi Ben,
    CUs never include Service Packs.
    Yes, you can install SP1 on top of April CU.
    Cheers,
    Stefan

    Reply

  20. Stefan,
    Thanks! That's what I thought, just wanted to make sure.

    Ben

    Reply

  21. Does the April CU support SQL Server 2014?
    If yes, Can we then just install the Full server package for April 2014 CU and connect to an SQL Server 2014 then install SP1? or install SP1 before creating the database?

    Reply

  22. Can Sharepoint 2013 be installed on a single Server with sql 2014 for production use for a small site where most data is accessed via a wan environment? Memory and cpu resources are not a problem.

    Reply

  23. Pingback from April CU 2014 for SharePoint 2013 has been released. | Bugra Postaci's Blog

    Reply

  24. Are those full server packages listed in the Article, i tried to download them and when installing it said it couldn't find any product?

    Reply

  25. Hi Tom,

    yes these are the full server packages.
    Which one did you try?
    Btw: the behavior you got is the one you would get when instatling the original SP1 which was pulled.
    Did you install this? Then you have to install the re-released SP1 on top to fix this issue.

    Cheers,
    Stefan

    Reply

  26. I have been most of the week on vacation, spent 3 days a t re:publica #rp14 Conference in Berlin. So

    Reply

  27. Hi Stefan,

    No tried the full server packages linked in your article but they are only hotfixes

    Reply

  28. Do language packs have cumulative updates as well?

    Reply

  29. No mention of SQL 2014 in the KB article. Is is supported?!

    Reply

  30. Hi Tom,
    seems we have a different understanding of “full server package”.
    A full server package is a hotfix. I guess you mean installation bits or a “slipstream” install,
    Slipstream installs are available for SP1 – not for April CU.
    But you can create them yourself using the slipstream version by copying the April CU bits into the update folders.

    Cheers,
    Stefan

    Reply

  31. Hi David,
    the above listed CUs include also fixes for all language packs.
    Cheers,
    Stefan

    Reply

  32. Hi Fred,
    we are currently waiting for an official statement on this from our product group.
    Cheers,
    Stefan

    Reply

  33. After apply this CU is it necesary running Configuration Wizzard ? Because I get an error after running it. When the CU finnished it required a reboot.

    Reply

  34. Hi Sorin,
    all SharePoint fixes always require the config wizzard. If you get an error you need to analyze why and fix the issue.
    The CU should not require a reboot as during the installation all SharePoint processes get stopped. Do you have custom tools running on the server which could lock SharePoint dlls? That might cause locks on the dlls which might cause a requirement for a reboot.
    Cheers,
    Stefan

    Reply

  35. Hi Stefan
    No I don't have any custom tools. It just required a reboot.
    Should I use psconfig.exe -cmd upgrade -inplace b2b -wait ?
    How can I verify if the update process was complete ?
    Thank you

    Reply

  36. Hi Sorin,
    yes that command looks good.
    It will tell you if it was successful. In doubt check the logfile.
    Cheers,
    Stefan

    Reply

  37. Hi Stefan
    I've run with success psconfig.
    Now when I look in Control Panel I see this version of my SP 15.0.4481.1005. I didn't reapply SP1 because my Romanian version isn't available (if I select Romanian language I get the Greek version). So what should I do to have the latest version (BTW which is after the April CU)

    Reply

  39. Thank you
    What about my SP version ?
    Should I reapply SP1 and then again April CU ?
    15.0.4481.1005 seems to me an older version. Is it another method for checking my SharePoint version ? Because on PSConfig it's showing other version (closer to SP1 but not SP1)
    Thank you again

    Reply

  40. Hi Sorin,
    you should try to apply April CU again after installing Romanian SP1 as April CU includes fixes for the language packs.
    If there are no updates in April CU for the LP, then the CU will tell you.
    Cheers,
    Stefan

    Reply

  41. Pingback from SQL Resource Governor-SharePoint 2013-Limit CPU, Memory and IOPS with SQL Server 2014 | Serge Luca's Blog (SharePoint MVP)

    Reply

  42. Pingback from SQL Resource Governor-SharePoint 2013-Limit CPU, Memory and IOPS with SQL Server 2014 | Serge Luca’s Blog (SharePoint MVP)

    Reply

  43. Hi Stefan,
    does SharePoint Server 2013 SP1 support Windows Server 2012 R2?
    Which CU will I need for that.

    Many Greetings

    Eva

    Reply

  44. Hi Eva,
    SP1 supports W2K12R2 but to install on this OS you need to use the slipstream installs avail on VLSC, MSDN or MPN.
    Cheers,
    Stefan

    Reply

  45. Hi Stefan,
    This SharePoint Security Patch MS14-022 is recommended to apply on SP Environments ?
    Do we need to run PSConfig post patching ?

    Regards,
    Sikander

    Reply

  46. Hi Sikander,
    it is always recommended to evaluate and install security fixes as soon as possible.
    You have to run PSCONFIG for all SharePoint patches.
    Cheers,
    Stefan

    Reply

  47. Following my tradition in presenting a summarized "Build Numbers Cube Sheet" as I did so before

    Reply

  48. Hello Stefan,

    I ran into a disturbing bug on two different SharePoint 2013 Server installations, which both run SP1 and April 2014 CU.
    In the Search Center, when you Trigger a People search for a Person, on the result page you get an error when klicking on the user´s Name.
    The underlying link is broken on both Servers.
    So People Search is not functioning with April 2014 CU for SP 2013 Server!

    Greetings!

    Reply

  50. As always: if you have a problem with a fix: please open a support case to allow us to investigate the issue. Just mentioning an issue in a blog comment will not result in a fix for the issue.

    Cheers,
    Stefan

    Reply

  51. Hi all

    We have problems with anonymous sites… they are'nt anonymous after installation of cu 04/2014 in the custom auth provider (1 of 4 zones, where 2 zones are anonymous, 1 of the works, other one not).

    we have also problems with the orphaned items checker and cleaner which is not working any more, at all.

    cheers

    Reply

  53. Hi Feytens, the workaround is to migrate to claims in SP2010 before attaching the DB to SP2013.

    Reply

  54. Hi,

    I forgot to unpacked the cab files. but I already installed the executable and run the configuration wizard. I got this version upon check the farm 15.0.4605.1002. is there a way to correct my installation of CU?

    Thanks!
    John

    Reply

  55. Hi John,
    The cab files are not intended to be manually unpacked. You need to place them in the same directory as the exe and the exe will take care of the rest.
    Cheers,
    Stefan

    Reply

  56. I wrote a blog post back in last January on the model how you can create site collections remotely using

    Reply

  57. HI Stefan,
    Does the April CU contain all the post SP2 cu?

    Reply

  58. Hi Allesandro,
    CU means cumulative update. Cumulative means it contains all previous.
    Cheers,
    Stefan

    Reply

  59. Finalmente siamo tornati online e lo facciamo pubblicando la tabella degli aggiornamenti di SharePoint

    Reply

  60. Hi Stefan,

    We are having Sharepoint 2013 Standard server but we are unable to install the hotfix "KB 2878240 – SharePoint Server 2013 April 2014 CU", its giving error "The installation of package failed". We also checked that we are having SP1 installed. Can you please
    suggest the correct hotifx.

    Thanks

    Reply

  61. Hi Gaurav,
    this is a common issue if the "old" SP1 version was used, not the rereleased one.
    The issue is fixed in May CU.
    Alternatively you need to install the rereleased SP1 version before installing April CU.
    Cheers,
    Stefan

    Reply

  62. I’m presenting a summarized "Build Numbers Cube Sheet" as I did so before, so please find

    Reply

  63. I’m presenting a summarized "Build Numbers Cube Sheet" as I did so before, so please find

    Reply

  64. I’m presenting a summarized "Build Numbers Cube Sheet" as I did so before, so please find

    Reply

  65. I’m presenting a summarized "Build Numbers Cube Sheet" as I did so before, so please find

    Reply

    1. Hi Sin,
      this is a very old hotfix (more than 2 years old) and I have currently no information about why it has been pulled.
      Might be that it introduced a critical regression or something similar.
      My suggestion would be to use a more current CU instead.
      Alternatively you can open a support ticket with Microsoft to see if the fix can be provided to you through other channels.
      Best Regards,
      Stefan

      Reply

  67. Hi Stefan,
    For SQL upgrade from SQL Server 2008 R2 to SQL Server 2014 for SharePoint 2013 Server, which latest Cumulative update should I install and how should I install it? Is it April CU 2014? The SP Server do not have Office 2013 installed. Please advise.
    Thank you in advance.

    Reply

    1. Hi,
      SharePoint 2013 SP1 plus April 2014 CU.
      Is your system on such an old patch level?
      Cheers,
      Stefan

      Reply

      1. Hi Stefan,
        I’m glad to read your immediate feedback. Noted, I am reviewing CU April 2014 SharePoint Server 2013 (KB 2880552 (SP1)) and will install on the DEV and UAT Servers first for review.
        Here are the patch level installed.
        For the Dev server Configuration database version: 15.0.4569.1000
        For the UAT server Configuration database version: 15.0.4667.1000
        For PROD Configuration database version is 15.0.4701.1000 (Superseded by 15.0.4753.1000)
        Thank you.

        Reply

        1. Ok, on Dev you are on SP1 level and you have to apply April 2014 CU.
          On UAT you seem to have already November 2014 CU installed – so no need to install April 2014 CU.
          On Prod you are even higher.
          Cheers,
          Stefan

          Reply

          1. Hi Stefan,
            Please confirm, per my understanding, UAT and PROD CU version may now support SQL Server 2014 when upgraded SQL version, right? There’s no need for us to install any CU, right?
            Please advise.
            Thank you.


  68. Hi Stefan,
    Additional clarification, you might have an idea how to resolve the red alert that says “Upgrade Required” in “Managed Servers in Farm” from Central Admin.
    Running stsadm.exe -o localupgradestatus
    I get the following output:
    SharePoint_Config
    Microsoft.SharePoint.Administration.SPConfigurationDatabase
    0
    Needs Upgrade
    I can’t get much information in StackExchange.
    Thank you in advance.

    Reply

  69. Hi Stefan,
    For the Dev server Configuration database version: 15.0.4569.1000
    For the UAT server Configuration database version: 15.0.4667.1000
    For PROD Configuration database version is 15.0.4701.1000 (Superseded by 15.0.4753.1000)
    Please confirm, per my understanding, UAT and PROD CU version may now support SQL Server 2014, right? This is in relation to my clarification above about SQL Server upgrade from 2008 R2 to 2014.
    This is because at the minimum, APRIL 2014 CU is needed. In our case the servers exceeded the minimum version of patches required to support SQL Server 2014.
    Please advise.
    Thank you in advance.

    Reply

    1. Most likely – not guaranteed. The config database version can also be updated through security fixes.
      Security fixes are usually only a small part of a CU.
      If you always installed the full CU and not the security fixes, then you are correct.
      Cheers,
      Stefan

      Reply

  70. Hi Stefan,
    I searched everywhere for the link to download “April 2014 CU for SharePoint 2013” to support SQL Server 2014, but the link tells “Sorry the page you have requested is not available.”
    Please advise and you might have an idea which link to use to download April 2014 Cumulative Update.
    Thank you in advance.
    Regards,
    Rsheyemsky

    Reply

    1. Hi Rsheyemsky,
      April 2014 CU is a very old and meanwhile unsupported fix as it was released before SP1.
      Patch levels older than SP1 are no longer supported.
      All Pre-SP1 fixes were integrated into SP1.
      If you install SP1 you automatically get all fixes from April 2014 CU as well.
      Cheers,
      Stefan

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

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