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

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

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

  • KB 3172456 - SharePoint Foundation 2013 March 2017 CU
  • KB 3172497 - SharePoint Server 2013 March 2017 CU
  • KB 3172462 - SharePoint Server 2013 with Project Server March 2017 CU
  • KB 3172457 - Office Web Apps Server 2013 March 2017 CU

The Full Server Packages for March 2017 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 this 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 (31)

  1. Johan says:

    When installing this update I get following message in the health analyzer. (In all our environments!)
    “Verify that the critical User Profile Application and User Profile Proxy Application timer jobs are available and have not been mistakenly deleted.”

    The ‘Repair automatically’ action fixed this problem.



    1. Sikander says:

      Have also got the same Error on Health Analyzer Pst March’17 CU install and “Repair Automatically” fix the error

        1. uzma says:

          This reference is for SP2016, are you stating that this issue is seen in both SP2013 and SP2016?

  2. Neville says:

    After applying this CU when I click on the EDIT link provided for a document in the document’s context menu, it doesn’t open in Office Web Apps but instead opens in the Office client. The document library is set to ‘Use the server default (Open in browser)’. Prior to applying this CU the document would open in Office Web Apps.

    1. Hi Neville,
      you might want to open a support case with Microsoft to get this analyzed.

  3. After install this CU on my DEV environment ( last installed CU is from July 2016 ) i have this problem :

    Failed to upgrade SharePoint Products.

    An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown.
    Additional exception information:
    CanUpgrade [Microsoft.SharePoint.Administration.SPIisWebSite] failed. (EventID

    Exception: The system cannot find the path specified. (EventID:ajxme)


    Cannot upgrade [Microsoft.SharePoint.Administration.SPIisWebSite]. (EventID

    CanUpgrade [Microsoft.SharePoint.Administration.SPIisWebSite] failed. (EventID

    Exception: The system cannot find the path specified. (EventID:ajxme)


    Upgrade completed with errors. Review the upgrade log file located in D:\LogFil
    es\ULS\Upgrade-20170323-101737-45.log. The number of errors and warnings is lis
    ted at the end of the upgrade log file.

    Follow this link for more information about how to troubleshoot upgrade failures

    Total number of configuration settings run: 8
    Total number of successful configuration settings: 7
    Total number of unsuccessful configuration settings: 1
    Successfully stopped the configuration of SharePoint Products.
    Configuration of SharePoint Products failed. Configuration must be performed be
    fore you use SharePoint Products. For further details, see the diagnostic log l
    ocated at D:\LogFiles\ULS\PSCDiagnostics_3_23_2017_10_17_29_185_255806164.log an
    d the application event log.

    and I do not really know what I can do now especially when now 5 of 7 sharepoint web application do not work any more

    1. OK I have manage to solve the problem however mysites web app not work any more and it looks like after this CU mysites lost permission levels. None of the users and event site admins cant open the web site of mysites.

      1. Hi Michal,
        I would recommend to open a support case with Microsoft to get this issue analyzed.

  4. Mitchell says:

    Were experiencing a number of cases in multiple farms (Dev and Test) where SCA permissions are breaking when applying the March 2017 CU – upgrading from the November 2016 CU. When the SCA tries to go to a site collections settings they are getting the “Sorry you do not have access to this page” message. Granting web Application permissions level has the same issue as well as. Also turning on anonymous does not work. Were having to run PSCONFIGUI -CK Resources to repair. Running the regular psconfigui does not correct the permissions.

  5. Sam Bañaga says:

    Hi Stefan,

    Good day,

    As per installing SharePoint Server 2013 March 2017 CU, I get the error “The installation of this package failed”, however SharePoint Foundation 2013 March 2017 CU works fine. I already have installed the prerequisites of this patch (SharePoint Server 2013 SP1 having the Microsoft Access Services English Language Pack’s version 15.0.4571.1502) and the current CU of the farm is on November 2016 CU (15.0.4875.1000). Did I miss something why I get this error? Please advise.

    Thanks and Regards,

    1. Hi Sam,

      this is not expected. Please check the installer log for details about why the installation failed. If you need assistance to resolve the issue I would recommend to open a support case with Microsoft.


  6. Brad says:

    We have noticed since applying March CU we have one particular site collection that a library will not open a document successfully in office web apps currently. Doesn’t matter if its an existing document or a new upload the same behaviour is experienced. I came across two technet articles on the topic that are similar, it sounds like your team is aware will a fix be included in next months CU? It seems we do have a space in the name of the site collection similar to what someone else was experiencing on their site.

    1. Hi Brad,
      this issue has been reported to Microsoft on March 28th. The issue is currently still being investigated.
      If you need further information about when a fix will be available you should open a support case with Microsoft.

  7. Mark Rioux says:

    Having issues with office web apps not working in Chrome on Windows 10 computers. Works fine with windows 7 and chrome. any ideas? Have Oct 2016 CU Office Web apps currently installed. Wanted to check first if anyone else experiencing this issue before going to March 2017 CU for Office web apps.

    1. Mark Rioux says:

      Correction: The new Chrome Update 57 breaks Office Web Apps for all Window OS’s. Do you know if the March 2017 CU for OWA fixes this issue?

      I remember this issue being similar back in August 2016 with Google removing the NPAPI Plug-in support from Chrome

      1. Hi Mark,
        creating a hotfix usually takes between 2 and 3 months after an issue has been reported to Microsoft through a Premier customer.
        An issue can be reported only after the problem has occurred. Based on the Google website Chrome update 57 was released on March 11th – so 3 days before March CU was released.
        That means it is impossible that March CU contains a fix for an issue created by an update of Google chrome which was released 3 days before.
        From what I see the issue has not yet been reported to Microsoft through official support channels. So if you need a fix – ensure to open a support case with Microsoft.
        I would also recommend to raise a support case to Google in parallel in case that this is not a problem in SharePoint but a problem in the Chrome fix.

  8. Elton Oliveira says:


    Is that common for the March 2017 CU for SharePoint 2013 to take about 20 hours to complete the binaries installation over just one server (main server with Central Administration and SQL Server Products)? Details:
    – Production Evironment
    – Small Size Farm
    – Two tiers (1 application Server/DB + 1 application server)
    – Small databases for Intranet and BI
    – Less than 1000 users

    1. 20 hours is long – a couple of hours is normal if you are not using the steps listed in this article:

  9. Sikander says:

    Hi Stefan,

    While opening documents with spaces sites/sub-sites in OWA are throwing error and I guess this has already reported to MS and MS has investigated this issue. Can we expect the fix in April’17 CU ?

    1. The current plan is to include this fix in April CU.

      1. Sikander says:

        Thanks Stefan. I can see the statement of fix in April’17 CU which has bee released. We’ll implement the same now.
        Thanks for the prompt response.

      2. Mohanghimire says:

        HI Stefan,
        It appears document opening through OWA and DataForm Webpart issues introduced since Dec2016 CU seems fixed with April 2017 CU (I have not applied this yet though but reading your blog and April KB Article )

        I am seening some discussion here after applying March CU , SCA permission are breaking is there any reported issue yet ?

  10. Subhash Prasad says:

    Hi Stefan,

    We have Installed Language pack SP1+ DEC 2016 CU on our SharePoint 2013 and now we want to install March 2017 CU so do we also need to install language pack once again or we can simply install March 2017 CU and run the PSCONFIG.

    1. Hi Subhash,
      no need to reinstall a language pack.
      If the language pack is installed and is at least of SP1 level for this service pack March 2017 CU will update it to the latest patch level.

  11. Neeraj says:

    Hello Stefan,

    As per this March CU , version of SharePoint should be ​15.0.4911.1001 but when we install the same it comes out to be ​15.0.4911.1000. Can you please explain the difference or we are correct?


    1. Hi Neeraj,
      what do you mean with “the same comes out”?
      Where do you see this version?

      1. Neeraj says:

        Hi Stefan,

        When we installed March CU Version shown on Central Administration ( Servers in the farm) is 15.0.4911.1000 but every wherer its written that the expected version should be15.0.4911.1001


        1. Hi Neeraj,
          the Servers in the farm page does not show the version of a CU – it shows the schema version of the configuration database.
          This schema version is not necessarily in sync with the build number of a CU.
          See here for details:


Skip to main content