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

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

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

  • KB 3141479 - SharePoint Foundation 2013 January 2017 CU
  • KB 3141481 - SharePoint Server 2013 January 2017 CU
  • KB 3141480 - SharePoint Server 2013 with Project Server January 2017 CU
  • No fixes released for Office Web Apps Server 2013

The Full Server Packages for January 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: https://blogs.technet.microsoft.com/stefan_gossner/2015/07/15/important-psconfig-is-mandatory-for-july-2015-cu-for-sharepoint-2013/

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 (50)

  1. Sibylla_B says:

    Hi Stefan,
    thanks a lot for sharing all these helpful posts!

    One question – you write in this article that the July 2015 CU requires running the SharePoint 2013 Products Configuration Wizard. As I understand from your further articles the Products Configuration Wizard is always required to run, so why is this specially highlighted in this case? Or is it not always necessary to run PSCONFIG / PSCONFIGUI after updating?
    Thanks for some clarification!

    1. Hi Sibylla,
      to ensure that the whole fix is applied including changes in the database and copying all the files into the right directories PSConfig is required after installing the fix. But usually you can do this in a second maintenance window (e.g.) a couple of Weeks later.
      In July was a breaking Change. SharePoint would not work correct if running PSConfig would have been delayed.
      This breaking change affects all CU installations which install a CU from July 2015 CU and later on a System with an older CU than July 2015 CU.

      1. Sibylla_B says:

        Thanks a lot for the explanation Stefan!
        Best regards

  2. Tim B says:

    I noticed in the 2013 and 2016 update notes for SharePoint server there was a fix for “SharePoint Server 2013 becomes unresponsive and a high CPU symptom requires restarting the server. Meanwhile, you can’t access sites or get extremely slow page load times.” Is there any information about what causes the sustained CPU usage? If there are user actions that can cause the issue, it would be nice to know in order to prevent the issue from occurring until we can get the CU package applied and tested out.


    1. Hi Tim,
      the issue was related to an problem with managed metadata Navigation.
      Termset retrieval and sorting of items was which could lead to high CPU if multiple threads were accessing the same datastructures due to missing synchronization.

      1. Tim B says:

        Thanks Stefan! I always look forward to these posts every month!

  3. Chandan says:

    Are there any known issues or problems with January CU we need to be aware of ? are there any general issues reported by any customers so far ?

  4. Peter M says:

    I have a SharePoint UAT/Prod farms that were left behind on installing CU, I need to know which CU should I install, shall I proceed with Jan 2017 CU, or it is better to take the previous version Dec 2016 CU to make sure I don’t have any issues. Testing will be done first on UAT.


    1. Mohanghimire says:

      Most recent CU Applied in our SharePoint Farm is (2016 January CU ) , we didn’t see any issues. We are planning to Rollout January 2017 CU that seem to have performance Fix, if anyone already applied/any known issues yet ?

  5. Frank Rüppel says:

    Hi Stefan,
    after installing january 2017 CU (Project Server 2013) search function inside task-lists is not working anymore. We didn’t change anything, crawl is fine. Every other list-type search is working fine. Anyone with a similar issue after installing january 2017 CU ??? thanks for feedback

    1. Frank Rüppel says:

      I found another user with SharePoint Server 2013, installing January CU …. no search in task-list – only in task-list!
      Is it a Microsoft bug?

      1. Hi Frank,
        if it is a problem in the CU then it is one that has not yet been reported to Microsoft.
        We can only investigate if customers open a support ticket to get the issue analyzed.

        1. Thomas says:

          Hi Stefan,

          I confirm that we can’t search within Task lists since the last CU.

          Thanks a lot for your posts.

          1. Hi Thomas,
            please ensure to open a support case with Microsoft to ensure that this issue can be analyzed.

        2. Thomas says:


          Just got off the phone with MS Support, that confirmed that this issue with the tasks list is already known to Microsoft since a very few days.
          The issue got introduced since source-code changes starting with the December 2016 CU.
          The next earliest release date for hotfix would be within the April 2017 CU.


          1. Jari Kirvesoja says:

            Hi all,

            thanks Thomas for the info! We have this issue also after I updated the December 2016 CU. What a pity that it wasn’t found before, since I deliberately waited for the January CU coming out before installing the December one, to avoid regressions…


  6. Dawn F. says:

    Dear Stefan, Thank you for your blog. Always so helpful! We just installed Jan 17 CU into our SP13 environment which had SP1 already. We are seeing weird spacing issues with term store columns during Form editing across our whole environment. I understand they were adjusting some issues for managed metadata columns but I didn’t think any were cosmetic. Have you heard about any layout changes?

    1. Hi Dawn,
      the description does not sound familiar.
      If this is an issue for you I would recommend to open a support case with Microsoft to get this analyzed.

      1. Dawn F. says:

        OK. Many Thanks!

    2. Anthony says:

      I can also confirm we are experiencing the exact same thing. Any column of data type MMS has the two little tags not aligned with the textbox row. This looks like a CSS issue here. I’m pretty shocked this would even get through Microsofts testing. We have raised a ticket with MS support.

  7. Cristian Bianchi says:

    Hello Stefan,
    Are you aware of any known issue/ Bug related to January 2017 CU for SharePoint 2013?
    I heard that it is recomended to wait to March CU, and not install January due to known issues.

    Thanks in advance!

    1. Mohanghimire says:

      Just making everyone aware we applied SharePoint 2013 January 2017 CU and Pages that have been Customized using DVWP gets broken with correlation ID.issue seem to be carried over from Dec CU and never corrected on Jan CU. We experience Enterprise-Wide big issue
      finally found this workaround working ;

      1. Hi Moghanghimire,
        did you open a support case with Microsoft to get this analyzed?

        1. Mohanghimire says:

          Hi Stefan,
          We have already opened a support case with Microsoft , they confirmed it is a bug in Dec CU and workaround is legit .”A fix has been requested from the PG and at this time still being triaged”
          (However we wanted to have a permanent fix , with thousands of Site collections Enterprise wide going through each page /site and modifying them is not Viable solution )
          The tags may or may not all appear based on the web part, but you should manually edit the page, look for the following tags, remove them and save the page:

  8. Henderson says:

    Hi Stefan,
    Thanks and Congrats for the best blog about SharePoint Products.
    I applied this Cumulative Update in my environment this weekend but i have two errors running the SharePoint Products Configuration Wizard. Looking to logs i see the errors below:

    Error 1:
    An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown. Additional exception information:
    Feature upgrade action ‘AddContentTypeField’ threw an exception upgrading Feature ‘CTypes’ (Id: 15/’695b6570-a48b-4a8e-8ea5-26ea7fc1d162′) in Site ‘URL of My Collaboration Site’: The object has been updated by another user since it was last fetched.
    The object has been updated by another user since it was last fetched.

    Error 2:
    Feature upgrade action ‘CustomUpgradeAction.FixWebFor15’ threw an exception upgrading Feature ‘PWS’ (Id: 15/’90014905-433f-4a06-8a61-fd153a27a2b5′) in Web ”: Another user checked-out the file and blocked for edit (EventID:aj2bj)

    Any help about these errors?


    1. Did you run PSConfig in parallel on more than one machine?

      1. Henderson says:

        Hi Stefan,

        No, I ran on one server at a time through the wizard



        1. Hi Henderson,
          looks as if some threads in OWSTIMER were running in parallel.
          What if you run PSCONFIG from the command line again?

          1. Mohanghimire says:

            Also, another try could be reboot server first and run PSconfig from command line (Sometime this may help to release lock on resources), do you agree Stefan ?

  9. Tina_L says:

    Hello – Thank you for providing this blog there is alot of good info here —
    I’ve recently taken over the company sharepoint environment and have two questions.
    1 – the last Cumulative Update that was completed was August, 2015 what would be the best approach to get to the more current version? Can I update using January, 2017 and this will provide all the missing updates from after August, 2015, is there a Cumulative Update I should start with, or do I need to update one, by one? Any insite would be very helpful.
    2 – the .net framework version that I’m currently running from is 4.5.1 which is no longer supported, when updating using the Cumulative Updates, do any of these updates have the .net framework 4.5.2 included? or do I need to update the framework separately?

    1. Hi Tina,
      1) Our updates are named cumulative updates because the include all previous fixes. So installing January 2017 CU will be sufficient in your scenarios.
      2) Sorry – no. SharePoint and .NET framework are separate independent products. You have to upgrade .NET framework separatly.

  10. Akash Arora says:

    Hi Stefan,

    Any idea what’s the status of the issue regarding search not working in task list after installation of this CU in SP Server2013? Has it got fixed in March2017’s SP Server 2013 CU?


    1. Hi Akash,
      this issue is currently planned to be fixed in May 2017 CU.

      1. Anthony says:

        Hi Stefan,

        Is the Task List search fix definitely going to be in the May CU?
        What is the estimated release date for this CU?


        1. Hi Anthony,
          the current plan is to fix this in May.
          It will be confirmed as soon as the CU is shipped as there is always a chance that an issue is identified short before the CU will be released which requires to remove a specific fix from a CU.

  11. mahindra says:

    HI Stefan,

    I have installed SharePoint January 2017 CU in my Development environment, Post completion of installation i have run the configuration wizard with out failed, but i have an issue in the build version number is not update to current version

    currently build version is showing 15.0.4893.1000 instead of 15.0.4839.1001

    Any help… Thanks in advance


    1. Seems you installed some fixes from Januar 2017 CU.

      1. Oliver Dörr says:

        Hi Stefan,
        I´m experiencing the same issues like mahindra describes. In addition, it is not possible to execute the Jan-17-CU.exe again. It fails and tells that the expected product version could not be found. Any ideas to correct this behaviour?

        1. Hi Oliver,
          it is expected that you cannot install the same CU twice.
          I’m not sure where you see a problem. Can you elaborate?

          1. Oliver Dörr says:

            Hi Stefan, thx for your response. I thought if I try to install it a second time it would prompt with the status “Package already installed”. Because at the moment it is not possible to install any CU higher than Jan´17. All others fail to install and state “The expected version of the product was not found on the system”. There are GER Language Packs installed as well, but properly patched with SP1 package.

          2. Oliver Dörr says:

            I could fix this issue. After calling the setup exe within a CMD and the parameter PACKAGE.BYPASS.DETECTION.CHECK=1, it works.

          3. Hi Oliver,
            you should never do this on a production system as it can lead to an unsupported installation.
            Using this parameter without asked to do so by Microsoft support is not recommended.
            The fact that the installation failed with a missing prerequisit needs to be investigated to understand which requirement is missing.
            just pushing the bits onto the system will not fix the underlying issue.
            My recommendation is to rollback this change and open a ticket with Microsoft to analyze the issue.

          4. Oliver Dörr says:

            Hi Stefan, of course you are right. Should have mentioned that in my post before that it occured on a Dev environment. There is a reason why the baseline check is implemented and of course you have to pay attention for it, especially on Prod.

  12. Ricky says:

    Hi Stefan,

    I’m a Sharepoint novice and barely know anything about it. Apparently, the CU will update the database on the SQL server in the farm as well, could you please confirm if this is the true? We have 2 nodes (1x App and 1x FE) in the farm that are in a different datacentre and setup for passive failover. I was thinking of running the CU on those 2 nodes first, since there won’t be any downtime required as they are not serving any connections. However, there’s only one SQL server in our Sharepoint farm and just wondering if the CU will update the DB on it, which may cause issues if we do not immediately update the rest of the nodes in the farm.

    1. Ricky says:

      Forgot to mention, we’re on the 2016 CU for Sharepoint 2013 foundation.

    2. Hi Ricky,
      yes. Running PSConfig after installing the CU will update the database with all changes since December 2016 CU.
      SharePoint servers cannot work with a higher database schema. So I would recommend to patch all servers first and then run PSConfig after all servers connected to the database are updated.
      Be aware that the first run of PSConfig will update the database schema but you still have to run PSConfig on all other SharePoint servers as well to apply other changes.

  13. Suhail says:

    Hi Stefan,
    I have applied the January 2017 CU in our Dev server, the CU is successfully installed also completed PSconfig command successfully without any error.
    However Under Manage server in this farm the Configuration DB version is showing as 15.0.4893.1000 instead of 15.0.4893.1001 the last number is not updated.
    In “Check product and patch installation status” it’s showing 15.0.4893.1001 Installed.
    Wanted to know any idea why the Config DB version is not showing 15.0.4893.1001 last digit not updated.
    Is this normal, can i go ahead with the same in Prod.
    Also FYI before installation of CU our SharePoint 2013 is on version 15.0.4569.1000,
    Microsoft SharePoint Server 2013 15.0.4569.1506 Installed.

    Thanks & Regards,

  14. andrew bell says:

    I have a problem after updating the office package I have share-point doesn’t exist it failed to register and seems to be missing

    1. Hi Andrew,
      if you need assistance with this issue I would recommend to open a support case with Microsoft.

Skip to main content