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

As I received this question a couple of times in the past here a short summary of the different update types used with SharePoint:

  

Service Pack

What is it: A service pack is a combination of previously released fixes, fixes which have only been released in context of the service pack and potentially new functionality added to the product.

What is included: new fixes, new functionality, all previously released fixes (older Service Packs, CUs, PUs)

Multilingual: No. You need separate Service Packs for each installed language

What is the prerequesit: Usually there is no prerequesit to install a service pack.

When to install: it is recommended to evaluate and install Service Packs as soon as possible.

Impact on future fixes: CUs and PUs released more than 12 months after the last service pack can only be installed if the Service Pack has been installed before

Installation Sequence: no specific sequence. You can install a service pack on top of CUs and PUs released later.

Release Cycle: no specific release cycle

 

Cumulative Update (CU)

What is it: A cumulative update includes fixes for problems with our product that have been reported by customer in context of support cases.

What is included: new and all previously released fixes (CUs and PUs) since the oldest supported service pack (within the first 12 month after a Service Pack has been released the CU includes also fixes released after the previous service pack)

Multilingual: Yes. The CU package includes fixes for all languages.

What is the prerequesit: The oldest supported service pack. Within the first 12 months after releasing a SP you can install on the latest SP and the previous one. CUs released more than 12 months after the newest SP require the newest SP to be installed.

When to install: CUs should only be installed to resolve specific issues fixed with the CUs as mentioned in each CU KB article: "Apply this hotfix only to systems that are experiencing the problems described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.". Or if adviced to install by Microsoft Support.

Impact on future fixes: In general a CU is not a prerequesit of future CUs and PUs. But in some situations a CU can be a prerequesit of a COD (see below).

Installation Sequence: no specific sequence.

Release Cycle: every second month (February, April, June, August, October, December) – since June 2014 CUs are released every month.

 

Public Update (PU)

What is it: A public update usually includes security fixes for the product or fixes for problems which affect a broad number of customers.

What is included: please review the KB article for each public update in detail to see which fixes are included.

Multilingual: Yes. The PU package includes fixes for all languages.

What is the prerequesit: Usually the oldest supported service pack. Within the first 12 months after releasing a SP you can install on the latest SP and the previous one. PUs released more than 12 months after the newest SP usually require the newest SP to be installed.

When to install: As a PU includes security fixes it is recommended to evaluate and install PUs as soon as possible.

Impact on future fixes: In some situations a PU can be a prerequesit of future CUs and PUs. E.g. the March 2013 PU for SharePoint 2013 will be a prerequesit for all future CUs (and potentially PUs) for SharePoint 2013.

Installation Sequence: A PU can only be installed on a system which does not already have the included fixes applied through another source – e.g. through an earlier released CU. As PUs are advised to be installed by all customers while CUs should only be installed by customers affected by one of the fixes incuded in the CU the test cycle for a PU is much longer than for a CU. That means a PU released in March can be superseeded by a CU released earlier (e.g. February CU or December CU). Also in some situations a CU requires an earlier released PU to be installed first – otherwise the fix will not install.

Release Cycle: once a month (if required)

 

Critical On Demand Fix (COD)

What is it: A COD is a fix which is provided only to a small number of customers affected by a critical problem directly through Microsoft Support to provide a quick relief. The code change in the COD will be included in one of the next CUs and it is advised to install that CU on top of the COD as soon as it has been released.

What is included: only the specific fix for a specific issue.

Multilingual: Usually not.

What is the prerequesit: Usually the CU that was used as the baseline to develop the COD. Microsoft Support will provide guidance which CU is required to be installed as a prerequesit for the COD.

When to install: Only if advised by Microsoft Support.

Impact on future fixes: A COD will not have an impact on future CUs or PUs. But the next CU can potentially revert the the code change introduced in the COD. See Installation Sequence.

Installation Sequence: As the COD will be released as soon as possible to a small number of affected customers. It might happen, that the next CU released shortly before or after the COD will not include the code change introduced by the COD. Customers which need the fix in the COD have to wait for the CU which will include the fix included in the COD. Microsoft Support will provided guidance on which CU can be installed on top of a COD.

Release Cycle: on demand

 

81 Comments


  1. Excellent article, Very well writtenb and highly commendable.

    Reply

  2. it's very helpful! Thank you!

    Reply

  3. Thanks Stefan!  Plan to pass on to User Groups, ISV's and customers.  

    Reply

  4. Hi Stefan – Just to be clear, this applies to SP 2013 and 2010, correct?

    Also, are MS monthly security notifications considered a PU, things like the SP 2010 bulletin that just came out (MS13-024)?

    Reply

  5. Great Stuff!  Thanks

    Reply

  6. Perfect and Nice Explanation !! Thanks a lot !!

    Reply

  7. As many times used in our daily business, we’re used to ask for “Build number” rather

    Reply

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

    Reply

  9. Good reference material – thanks Stefan!

    Reply

  10. Updated 20/Dec/2013 Be aware that all Updates for SharePoint 2013 require March 2013 PU for SharePoint

    Reply

  11. As usual, here is the Bi-monthly CU Release. please find all info below. Some links or updates may not

    Reply

  12. Well, we were familiar from SharePoint 2010 and MOSS 2007 the bi-monthly "cumulative updates"

    Reply

  13. As usual, here is the Bi-monthly CU Release. please find all info below. Some links or updates may not

    Reply

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

    Reply

  15. When Microsoft performs an Exchange Risk Assessment Program ( ExRAP ) with a customer there are several

    Reply

  16. Be aware that all Updates for SharePoint 2013 require March 2013 PU for SharePoint 2013 to be installed

    Reply

  17. Be aware that all Updates for SharePoint 2013 require March 2013 PU for SharePoint 2013 to be installed

    Reply

  18. With some delay, here is the June 2014 CU Release for SharePoint 2013 Server, please find all info below

    Reply

  19. You are reading right, we have the first monthly cumulative update package for SharePoint Server 2013

    Reply

  20. NOTE! All Updates for SharePoint 2013 requires either the March 2013 PU or SharePoint Server 2013 SP1

    Reply

  21. Starting with the July 2014 CU, the release cycle is now every month rather than the Bi-monthly cycle

    Reply

  22. thanks for sharing.

    Reply

  23. Our SharePoint product group released the next monthly cumulative updates. This month we will have the

    Reply

  24. SharePoint 2010 Build Numbers Cube Sheet
    As many times used in our daily business, we’re used

    Reply

  25. SharePoint 2010 Build Numbers Cube Sheet
    As many times used in our daily business, we’re used

    Reply

  26. Well, we were familiar from SharePoint 2010 and MOSS 2007 the bi-monthly "cumulative updates"

    Reply

  27. Our SharePoint product group released the next monthly cumulative updates. This month we will have the

    Reply

  28. There is one thing i want to ask…could we apply the service pack or cu on SharePoint 2007 which is already expired?

    Reply

  29. Hi Akash,

    sorry I don’t understand the question.
    What do you mean by an expired SharePoint 2007?

    Cheers,
    Stefan

    Reply

  30. Our SharePoint product group released the next monthly cumulative updates. How patching works for SharePoint

    Reply

  31. Note! Since July 2014, the release cycle is now every month! Any CU’s published later than June 2013

    Reply

  32. Since July 2014 CU, the release cycle is now every month rather than the Bi-monthly cycle. NOTE! All

    Reply

  33. A equipa de desenvolvimento de SharePoint lançou o Pacote Cumulativo de Julho de 2014 para o SharePoint

    Reply

  34. A equipa de desenvolvimento de SharePoint lançou o Pacote Cumulativo de Agosto de 2014 para o

    Reply

  35. A equipa de desenvolvimento de SharePoint lançou o Pacote Cumulativo de Setembro de 2014 para

    Reply

  36. A equipa de desenvolvimento de SharePoint lançou o Pacote Cumulativo de Outubro de 2014 para o

    Reply

  37. Tank you for this information !

    Reply

  38. Our SharePoint product group released the next monthly cumulative updates. How patching works for SharePoint

    Reply

  39. The Feb 15 CU being pushed out via WSUS brought me here. Great info, BUT this statement regarding CUs is one of the reasons new SP admins have so much trouble wrapping their heads around this patching paradigm; "What is included: new and all previously
    released fixes (CUs and PUs) since the oldest supported service pack (within the first 12 month after a Service Pack has been released the CU includes also fixes released after the previous service pack)"
    This is NOT entirely true, and in fact is completely misleading based on your explanation in your Aug 2014 Blog "SharePoint patching demystified" where you explain that a CU only contains the previous released fixes FOR THOSE COMPONENTS that have a fix in this
    current CU. For instance the Feb 14 CU includes a fix for Word Automation Services so it includes all previous CU fixes for WAS but if a previous CU also included a fix for other SharePoint services those are not included in the Feb 15 CU.

    Personally I think MS is doing us a disservice labeling these as SharePoint CUs when it would be much clearer to receive a patch for SharePoint Word Automation Services. Just my $.02 worth.

    Reply

  40. Hi Tom,
    the article was referring to the Uber package which I document in each CU and which we release with each CU (with two exceptions so far).
    Cheers,
    Stefan

    Reply

  41. A equipa de desenvolvimento de SharePoint lançou o Pacote Cumulativo de Novembro de 2014 para

    Reply

  42. A equipa de desenvolvimento de SharePoint lançou o Pacote Cumulativo de Dezembro de 2014 para

    Reply

  43. Our SharePoint product group released the next monthly cumulative updates. How patching works for SharePoint

    Reply

  44. A equipa de desenvolvimento de SharePoint lançou o Pacote Cumulativo de Fevereiro de 2015 para

    Reply

  45. Nice article. Thank you so much 🙂

    Reply

  46. Hi Sid,
    September 2014 CU includes all the SharePoint related security bulletins up to September 2014.
    Cheers,
    Stefan

    Reply

  47. Our SharePoint product group released the next monthly cumulative updates. How patching works for SharePoint

    Reply

  48. Note! Since July 2014, the release cycle is now every month! Any CU’s published later than June 2013

    Reply

  49. This Month CU has been released with a full server packages, a.k.a. "Uber Packages" – so this

    Reply

  50. Hi Stefan,

    thanks for detailing the different kinds of updates and giving some guidance on how and when to apply updates.

    As the original article is dated 2013, I'm wondering of the guidance in respect to installing CUs only when you're affected by certain issues is still up-to-date or if one should always install CUs when they are released?

    What if I'm affected by an issue, but I haven't really nailed my problems with SharePoint? If I don't know what's causing some behavior, how should I know if I should install a certain CU?

    Reply

  51. Hi Henning,
    the guidance still applies.
    We recommend a test environment to verify all fixes before applying to production. Here you can verify if an issue has been addressed by the latest CU or not and you can also verify if any new issues are introduced with the CU which affect your specific configuration.
    Cheers,
    Stefan

    Reply

    1. Hi Stefan,
      I have a doubt regarding CU installation in Farm. Please clear it.
      suppose we have 4 servers in Farm. All four servers are patched till CU Feb 2016. Now we are planning to install CU Dec 2016.
      Now CU are getting released every month.
      So I have to install all CU from Mar 2016, Apr 2016, May 2016 so on till CU Dec 2016 OR just install CU Dec 2016 after CU Feb 2016 and it will cover all release issues/bugs which were released between Feb CU 2016 and Dec CU 2016.
      Regards,
      Manoj Kumar

      Reply

      1. Hi Manoj,
        it is a cumulative update. So it includes all previous updates.
        Cheers,
        Stefan

        Reply

        1. Hi Stefan,
          As manoj asked about the CU. Example – Jan CU 2017 is installed in the farm. Now we have FEB, MAR and APRL CU. We can go direct for APRIL CU, ONLY IF we have UBER file (uber Package in downloaded CU), because UBER file contain fix for all the SharePoint Components. Yes these day Microsoft releasing CU with Uber file then we can go direct/jump to any coming month CU for installation . As you also explain in https://blogs.technet.microsoft.com/stefan_gossner/2014/08/13/august-2014-cu-for-sharepoint-2013-has-been-released/

          Reply

          1. Nothing to add!
            🙂


        2. Hi Stephen, the updates/fixes that are included in the package are always Cumulative (meaning, it includes all the new and all previously released fixes (CUs and PUs) or not. Please clarify.

          Reply

  52. Our SharePoint product group released the next monthly cumulative updates. How patching works for SharePoint

    Reply

  53. helpful stuff !!!

    Reply

  54. Our SharePoint product group released the next monthly cumulative updates. How patching works for SharePoint

    Reply

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

    Reply

  56. The product group released the July 2015 Cumulative Update for the SharePoint 2013 product family.

    Reply

  57. Our SharePoint product group released the next monthly cumulative updates. How patching works for SharePoint

    Reply

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

    Reply

  59. good job laying this out Stefan, thanks for your time.

    Reply

  60. Our SharePoint product group released the next monthly cumulative updates. How patching works for SharePoint

    Reply

  61. The product group released the August 2015 Cumulative Update for the SharePoint 2013 product family.

    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. Nice information..! Thanks..!!

    Reply

  65. Hi Stefan,
    until now we have installed only SharePoint CUs in our Farms. (Latest install Jan 2017 CU)
    Is it possible to Change to PU installation over WSUS?
    Or there any Problems?
    Best regards
    Joerg

    Reply

    1. Hi Joerg,
      from what I have seen (I’m not a WSUS expert) WSUS will only install fixes on Standalone SharePoint installations. Not on Farm configuration.
      Cheers,
      Stefan

      Reply

  66. HI Stefan. If there is a Missing Dependency on the farm (in our case related to SSRS integrate) will this prevent a SharePoint farm from successfully installing and applying a Cumulative Update?

    Reply

    1. Hi Rich,
      PSConfig can fail if dependencies are not fulfilled.
      Cannot say if the dependency to SSRS would cause this, sorry.
      Cheers,
      Stefan

      Reply

  67. Hi Stefan,
    January 2020 CU for SharePoint 2016 includes all older CU 12 months back?
    Are there any requirements for SharePoint 2016 to install a January CU?

    Br Michael

    Reply

    1. Hi Michael,
      Yes, because SharePoint fixes are cumulative.
      No, there are not other requirements.
      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.