April 2016 CU for SharePoint 2010 product family is available for download

The product group released the April 2016 Cumulative Update for the SharePoint 2010 product family.
For April 2016 CU we have full server packages (also known as Uber packages) for SharePoint server and Project server. For SharePoint Foundation there was no CU released in April. For the latest updates for SharePoint Foundation look for the March 2016 CU.
As this is a common question: Yes, April 2016 CU includes all SharePoint security fixes released with April 2016 PU.
Be aware that CU is a Post-SP2 hotfix. It is required to have SP2 installed before installing the CU.
It is required to have SP2 installed for the base product and all installed language packs to install April 2016 CU for SharePoint 2010.

This CU includes all SharePoint 2010 fixes (including all SharePoint 2010 security fixes) released since SP2. The CU does not include SP2.
The KB articles for April 2016 CU should be available at the following locations in a couple of hours:

  • No fixes released for SharePoint Foundation 2010
  • KB 3114995 – SharePoint Server 2010
  • KB 3114992 – Project Server 2010

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

After installing the fixes you need to run the SharePoint 2010 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 2010 CU contains the SharePoint Foundation CU.
That means only one package has to be installed for the SharePoint 2010 product family.
Related Links:


  1. According to KB 3114995, April 2016 CU build is 14.0.7168.5000. However, when I installed, it shows up as 14.0.7166.5000. Which one is correct?


  2. Hi Stefan
    The people like me book marked your blogs for the upgrade planning etc . For me your blog is the first stop and reference before we plan any upgrade. I have request to you , if possible could you add a Sub heading ” Regressions & issues ” ? ..If you included this it would be a great place to see all the information related to the patch release and can decide on which CU is suitable for our environment .
    Shany A K


    1. Hi Shany,
      I’m not in the position to blog about regressions and issues. Such information has to come through official channels.
      The main reason is that most regressions and issues we see only affect a very small percentage of customers as they are for very specific customer scenarios.
      Only a very small amount of issues hit a broader amount of customers – and those issues are usually documented in KB articles or official blogs from our product groups as soon as they are confirmed.
      SharePoint is a very flexible product and it is impossible to test all functionality in combinations with all features and products that can be integrated.
      So testing a fix in YOUR specific test environment which should be as near to the production environment as possible is a very important step before applying the fix to your production environment.


      1. Thanks for your reply Stefan ! I can understand that.
        Every year we have our steering committee meeting to finalise one CU which has no or less issues reported . After that we upgrade almost 35 to 40 farms ( Test/QA/PROD) . Before finalising one CU , we used to refer all technet articles blogs to see what all issues reported from other customers . Your blog is one of the references where we can get lot of other customers feedback. Thanks for the blog and update.


      1. Hi Henning
        Yes Todd Klindt was one our reference point , Thanks for the link from Jeff Jones ..nice reference.


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.