March 2016 CU for SharePoint 2013 product family is available for download

The product group released the March 2016 Cumulative Update for the SharePoint 2013 product family.

For March 2016 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, March 2016 CU includes all fixes from March 2016 PU.


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 March 2016 CU should be available at the following locations in a couple of hours:

  • KB 3114822 - SharePoint Foundation 2013 March 2016 CU
  • KB 3114827 - SharePoint Server 2013 March 2016 CU
  • KB 3114823 - SharePoint Server 2013 with Project Server March 2016 CU
  • KB 3114821 - Office Web Apps Server 2013 March 2016 CU - This is also a security fix!

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

Important: If your farm has been on a patch level lower than July 2015 CU: July 2015 CU and later contains a breaking change compared to earlier builds which requires running the SharePoint 2013 Products Configuration Wizard on each machine in the farm right after installing the CU.
If you don't run PSCONFIG after installing March 2016 CU (on a farm which had a lower patch level than July 2015 CU) crawl might no longer work - so ensure to schedule a maintenance window when installing this CU which includes PSCONFIG runs.
See here for detail:

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:

Comments (42)

  1. Jussi Palo says:

    Hooray! Fix for the User Profile picture issue. 🙂

  2. IT Norbert says:


    short question: Should I install the march CU, although I always patch the system through windows update?
    I know I have to run psconfig after installing a sharepoint updates, but is the march cu even necessary in my case?

    Kind regards,

    1. Hi Norbert,
      it depends. If you only need to ensure that all SharePoint security fixes are applied, the Microsoft Update is sufficient. If you also need some of the non-security fixes for SharePoint, then you have to install the CU.


      1. Hi Stefan,

        This just reminded me of something I was to ask you. We had a 2013 server farm running the build SP1 + March 2015 CU. We installed all the security fixes from the following bulletins: MS15-015, MS15-046, MS15-099, MS15-110, MS15-116 and MS16-015. Now in central admin the config db version has been bumped to Feb 16 CU (???). Is that supposed to happen? The farm is not on Feb 16 CU patch level (i.e. with all hotfixes included in CUs from March 15 to Feb 16) for sure.

        1. Hi Marco,
          that is expected. The config db schema is not bound to a CU but to the fact if a patch updates the config db schema. That can happen with a CU or with a security fix.
          In the past there were CUs which did not change the schema version as well.

          Ser here for details:


          1. Hi Stefan, I see I could have done some more search on that. Thanks for your reply.


  3. filip says:

    During our deployment we have installed sharepoint 2013 with sp1 (slipstreamed) and with cumulative update November 2014 (4 server farm).
    After installation we then created the farm and ran psconfig (a sp2013 + sp1 + cu november 2014 farm).
    Now we want to install march cu 2016 CU but we encounter installation failure cause the sp1 is unfortunately the bad sp1.

    We ran Stefan Goßner script and it confirms we have bad sp1

    DisplayName : Microsoft SharePoint Server 2013
    DisplayVersion : 15.0.4569.1506

    DisplayName : Language Pack for SharePoint and Project Server 2013 – German/Deutsch
    DisplayVersion : 15.0.4571.1502

    So bottom-line is we have bad SP1 but note we also have November 2014 CU applied, that is succesfully applied
    What would be the correct proces to install march 2016 CU?

    – install good sp1 and install German LP SP1 and install march 2016 CU and then run psconfig?
    – install good sp1 and run psconfig and then run march 2016 CU and then run psconfig again?

    1. Hi Filip,
      if you would like to get the updated SP1 installed, then just install that.
      PSCONFIG is not required afterwards if you are planning to directly install March 2016 CU.
      Just install SP1 (rereleased) and then March 2016 CU.
      PSCONFIG is only required at the very end.

      1. filip says:

        We install officeserversp2013-kb2880552-fullfile-x64-en-us successful but then we install cu march 2016 and it fails instant with ‘installation failed’ before the install process begins

        1. Hi Filip,

          this error message is not related to a missing service pack. Otherwise the installation would fail with the information that the product to be patched cannot be found.
          Here I would recommend to enable MSI logging to get more details about the issue that causes the fix installation to fail.


        2. Franck says:

          Hi Stefan,
          Got the same issue as Filip when installing a new SP2013 farm (using AutoSPInstaller).
          Although I got the ISO with SP1 from VL, it failed installing March2016 CU (ubersrv2013-kb3114827-fullfile-x64-glb.exe) with Invalid baseline error.
          I then reinstalled SP1 (kb2880552) successfully but it still fails when installing March2016 CU with the same invalid baseline error.
          After running psconfig to create the farm, it says 15.0.4571.1502 in “manage patch status”. But still it failed applying the March2016 CU with the same invalid baseline error.
          How could I enable MSI logging to get more info?

          1. Hi Franck,
            standard MSI logging is automatically enabled with SharePoint. You can find the logs in %temp%\SharePoint Server Setup … log.
            In case that %temp% end with \1 or \2 you need to check the parent directory.

          2. Hi Franck,
            I was wondering if you were successful in installing the March 2016 Uber update with AutoSPInstaller? I wonder if the March 2016 is expecting .NET Framework 4.6 and if you rolled back to 4.5 in order to run the SharePoint Install? I was thinking of attempting the install with the Uber Update myself, but thought it best to fix the hack for the .NET Framework first and apply the OS Patches manually due to the delicate nature of the .NET 4.6 / SharePoint 2013 debacle.

          3. SharePoint 2013 with latest patch levels are fully compatible with .NET 4.6. Our hotfix installers for current fixes work with .NET 4.5.x and .NET 4.6.
            I’m not sure what “debacle” you mean in regards to SharePoint 2013 and .NET 4.6 as a properly patched SP2013 fully supports .NET 4.6

  4. Ryan says:

    Hi Stefan,

    How has the uptake been with the March CU? Have there been many issues as a result of this update? My Dev testing suggests that its ok I am just double checking 🙂

    Thank you,


    1. Hi Ryan,
      we haven’t seen cases for issues introduced by March CU.

      1. Ryan says:

        Thank you very much.


  5. Andy says:

    Hello Stefan,

    Is there a problem with the download servers ?
    I’m trying to download SharePoint Foundation 2013 SP1 ( for one of my customers and I get a gateway timeout….
    Direct URL:

    Full error message:
    Gateway Timeout
    The proxy server did not receive a timely response from the upstream server.
    Reference #1.bb0a1602.1459257883.3be924b4

    Note: I’m not using a proxy….

    Could you provide an alternate download location ?


    1. Hi Andy,
      I just tested this download link and it works perfectly fine.
      Please test again.

      1. Andy says:

        Hi Stefan,

        Thanks a lot. Really appreciate your quick reply.

        Best regards,

  6. Hello!
    After this CU unable to see SSRS report options in the context menu of an SSRS report in SharePoint 2013 and Report Server Integration Feature disappeared in Site Collection Features. But content types of Reporting Services we can still use. I opened ticket in Microsoft and waiting for resolution.
    Have someone the same issue?

    1. Rosolved. Reinstall SSRS Add-In helped me.

  7. Eric says:

    Hi Stefan,
    Is server having issues? I was able to go to select packages for SharePoint Server CU but got “page not found” after that.

    1. Hi Eric,
      I just tested all 4 downloads and they work fine.
      Please test again.

  8. Brad says:

    Hi Stefan,

    After the March SP2013 updates there has been one reported issue which is not making sense to me as the issue is only affecting one of our web applications. Essentially when there is a requirement to have a column contain information when uploading a document through a web part document library view although information is entered when you hit save its as if it sees the field as blank. It also shows a message that the field cannot be blank in red. If you upload the document directly to the library versus the web part view this issue does not occur. I have turned off that requirement on the fields to allow our users to upload from the web part view in the meantime. Any thoughts on this?

    1. Hi Brad,
      I haven’t seen that. As it is only in one web application its more likely to be something related to this web application than related to a problem in the CU.
      If you need assistance in isolating the issue I would recommend to open a support ticket with Microsoft.

  9. Abhinav Ag says:

    Hi Stefan,

    I have SharePoint 2013 installed on my client environment with Service Pack 1 (Second Release Version 15.0.4571.1502).
    We need to install the patches in our SharePoint 2013 Environment.

    Can you please suggest which CU, PU or Uber package should I install in our environment and What is the correct Process for Updating SharePoint.
    We want to keep our SharePoint Up to date. As i came to know from different blogs that the latest version package may not have stability and as per the recommandation we should keep a lag of some months. so please suggest which package should be installed or updated.

    Abhinav Agarwal

    1. Hi Abhinav,

      there is no general recommendation about which CU/PU or Uber to install.
      We recommend to evaluate and install all security fixes/PUs as soon as possible to fix security holes and to install CUs only if they either fix a specific issue you need to get addressed. If a CU needs to be installed we recommend the Uber package.


      1. Abhinav Ag says:

        Thanks, Stefan for the quick response,,

        So as I understand, if I install a Uber package of January 2016 then it will install all the previous releases of CU’s and PU’s till Jan 2016 and after that we can install all the PUs that are released after January 2016 for the security updates. Is it right?

        Can you please suggest the installation process may be through some blogs.


        1. Hi Abhinavele,
          it will not install all previous CU’s – it will only install January 2016 CU. But this CU contains all previously released fixes.
          The installation process is described on technet:


          1. Abhinav Ag says:

            Okey Stefan.

            Thanks for your help.


  10. Sebastian says:

    Hi Stefan,
    we encountered a strange issue installing the march 2016 cu. On our Test system we installed a clean 2013 SP1 with April 2014 CU (as we are using MS SQL 2014). After install everything seems to work perfect. But if we install the March 2016 CU, User Profile Sync fails to start with error:

    UserProfileApplication.SynchronizeMIIS: Failed to configure MIIS post database, will attempt during next rerun. Exception: System.Configuration.ConfigurationErrorsException: ERR_START_SERVICE…

    Any ideas on this?


    1. Hi Sebastian,
      this is not a known issue.
      If you need assistance in analyzing this issue I would recommend to open a support case with Microsoft.

  11. DS Nayee says:

    Great post, very helpful. I was able to apply CU successfully. Link to run PS config helped as well.

  12. Sarfraaz says:

    Hi Stefan,
    After March CU patch on our QA and PROD , User Profile Synchronization service is falling to Start.. and logs below errors

    Windows Event Data:
    The Open Procedure for service “FIMSynchronizationService” in DLL “C:\Program Files\Microsoft Office Servers\15.0\Synchronization Service\Bin\mmsperf.dll” failed.

    ULS logs Error:
    UserProfileApplication.SynchronizeMIIS: Failed to configure MIIS post database, will attempt during next rerun. Exception: System.Runtime.InteropServices.SEHException (0x80004005): External component has thrown an exception. at Microsoft.Office.Server.UserProfiles.Synchronization.ILMPostSetupConfiguration.ConfigureMiisStage2() at Microsoft.Office.Server.Administration.UserProfileApplication.SetupSynchronizationService(ProfileSynchronizationServiceInstance profileSyncInstance).

    Any idea about this issue.

  13. Alessandra says:

    Hi Stefan,
    Thank you for the great post.
    I installed March Update KB3114817 ( by itself and when I try to run the KB3114827 I get an ‘installation failed’ message right away. My logs don’t show anything abnormal. Have you seen this before? Thx.

    1. Hi Alessanrda,

      3114817 is included in 3114827 – so no need to install it separately.
      Please check the MSI logs for 3114827 to see what went wrong.
      If you need assistance with this I would recommend to open a support ticket with Microsoft.


      1. Alessandra says:

        Thanks for your prompt reply. I figured out what the problem was, it was missing a cab file 😉
        Thanks for your help.

  14. PoWaShell says:

    Hi Stefan,

    I am trying to access link MS16-029: Description of the security update for SharePoint Server 2013: March 8, 2016 (KB3114826) – specified on March 8, 2016, cumulative update for SharePoint Server 2013 (KB3114827) – and I am getting a “This page doesn’t exist”.

    I thought I’d check Microsoft Security Bulletin MS16-029 – and there is no mention of it. Has this been removed from the March 2016 CU?

    Kind Regards


    1. Hi Paul,
      I’m not sure why the KB is not avail.
      You might want to open a support ticket to follow up on this.

Skip to main content