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

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

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

  • KB 4011649 - SharePoint Foundation 2013 January 2018 CU
  • KB 4011652 - SharePoint Server 2013 January 2018 CU
  • KB 4011650 - Project Server 2013 January 2018 CU
  • KB 4011648 - Office Web Apps Server 2013 January 2018 CU - This is also a security update!

The Full Server Packages for January 2018 CU are available through the following links:

Important: If your farm has been on a patch level lower than July 2015 CU ensure to read the following blog post:

Be aware that the SharePoint Server 2013 CU contains the SharePoint Foundation 2013 CU. And the Project Server 2013 CU also contains the SharePoint Server 2013 CU and SharePoint Foundation 2013 CU.

Related Info:

Comments (10)

  1. Tariq13 says:

    Hi Stefan,
    I have upgraded my SharePoint from Dec 2017 CU (build number 15.0.4989.1001) to January 2018 CU level. It seems like everything went well. Both binary installation PS config ran successfully. This also upgraded build number to (15.0.4995.1000). Below article shows build number should be 15.0.4997.1000. Why is this different. Here is the article show which shows new build number

      1. Tariq13 says:

        This is the first time happened to me. Thanks for the article

  2. Blue Shield says:

    Hi Stefan!

    On one SP2013 farm, we’ve had some issues starting the User Profile Synchronization service after applying the Jan 2018 CU. We’ve also heard some similar unsubstantiated stories from other sources as well, but I have not yet been able to confirm them and I have found nothing on the internet so far.

    I suppose that installing an older CU on top would not be supported and it would only mess things up, right? (As an older CU would most likely contain _less_ stuff than the current?)

    Thanks for any ideas!

    1. Hi,
      it is technically impossible to install an older CU onto a newer one.
      I would recommend to open a ticket with Microsoft support to get this issue analyzed.

      1. Blue Shield says:

        Thanks a lot for your quick input, Stefan!

        Really appreciate your blog. 🙂

  3. Chris says:

    Hi Stefan,
    I have updated my farm to the Jan 2018 CU however all my servers still show KB3213569 (Jun 2017) needing to be installed. How should I go about installing it?

    1. Hi Chris,
      first please check that the fix is really installed on all machines which are listed in this message.
      If that is the case you should run “Get-SPProduct -local” on each machine which is incorrectly listed as requiring this update.
      That will update the information about the installed fixes in the SharePoint configuration database using the data from the MSI database on your local machine.
      If the fix is still listed as missing after this step I would recommend to open a ticket with Microsoft.

  4. Dean Gross says:

    I installed the Jan 2018 CU for 2013, the Config wizard showed that it completed successfully, but in Central Admin on the Check Upgrade Status page, this update is not shown. In the logs folder, there is not any file. Many of the services are showing that they have 15.0.4997.1000 which is the correct version for that patch. However, in Control Panel, SP 2013 is shown as 15.0.4471.1502.

    My customer has had a lot of problems with this server and getting it patched yesterday was very challenging with a wide variety of issues that I’m still working through.

    Do you have any idea how this could happen, or how to troubleshoot?

    1. Hi Dean,
      as there seem to be various issue I would recommend to open a ticket with Microsoft support to get this installation analyzed in more details.

Skip to main content