January 2018 CU for SharePoint Server 2016 is available for download

The product group released the January 2018 Cumulative Update for SharePoint Server 2016 product family.
This CU also includes Feature Pack 1 which was released with December 2016 CU and Feature Pack 2 which was released with September 2017 CU.

The KB articles for January 2018 CU are available at the following location:

  • KB 4011642 - January 2018 Update for SharePoint Server 2016 (language independent) - This is also a security update!
  • KB 4011645 - January 2018 Update for SharePoint Server 2016 (language dependent fixes)
  • KB 4011021 4011022 - January 2018 Update for Office Online Server 2016 - This is also a security update!

The download for January 2018 CU is available through the following link:

Important: It is required to install both fixes to fully patch a SharePoint server as each SharePoint installation comes with a language independent component and a language dependent component. If additional language packs are added later (only) the language dependent fix has to be applied again.

It is irrelevant which language you pick on the drop down in download center. Even the language dependent fixes are all in the same package for all languages.

After installing the fixes you need to run the SharePoint 2016 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.

SharePoint 2016 January 2018 CU Build Numbers:

Language Independent fix: 16.0.4639.1002
Language Dependent fix: 16.0.4639.1001

To understand the different version numbers please have a look at my article which explains the different SharePoint build numbers.

You can use the SharePoint Server 2016 Patch Build Numbers Powershell Module to identify the patch level of all SharePoint components.

Related Links:

Comments (16)

  1. I tried installing “kb4011021” on my office online server and I received “Installation Failed.” I tried removing office online and reinstalling it fresh (on top of November 2017 build) with the same results. Is anyone else seeing this?
    I am hoping that this patch will fix the “Unhealthy” issue with ServerStatus that I have been seeing since the Nov 2017 build.

    1. @Sergei: I have the same problem.

    2. Luterin says:

      I too have experienced the same problems. Here’s the event log msg: “Product: Microsoft Office Web Apps Global Components – Update ‘Security Update for Microsoft Office Online Server (KB4011021) 64-Bit Edition’ could not be installed. Error code 1603.”

      FYI, that is what I did:
      * Uninstalling “Office Online Server language pack – French” Version 16.0.7726.1027
      * Uninstalling “Office Online Server” Version 16.0.7766.8550
      * Installing “Office Online Server” Version 16.0.8471.8525
      * Installing “Office Online Server language pack – French” Version 16.0.8431.1018
      * Installing Security Update version 16.0.8471.8538 (December 2017)
      * Failing installation on Security Update version 16.0.8471.8545 (January 2018)

      1. I would suggest to open a ticket with Microsoft support on this to get this analyzed.

    3. Just in case anyone is wondering about the office online server patch:

      basically do not install 🙂

      1. DonOfBran says:

        KB 4011021 description has been updated with Known Issues: “Microsoft is aware of an issue that may cause the installation of this update to fail. We are investigating the problem and will provide additional information as it becomes available.”

      2. Andy Dawson says:

        … And now the download is not available.
        I assume a fixed version will be available shortly?

        1. Thanks. I updated the article above.

  2. karimSP says:

    As usual very helpful…Thank you….

  3. JUANCARLOSR says:

    Question I have installed Feature Pack 2 and now I want to install the March 2018 STS and Wss ( will both March patches have the CU for oct nov dec jan and feb?)

    1. Yes, March 2018 Fixes include everything you need.

      1. JUANCARLOSR says:

        Thank you Stefan and the last question: When patching I have seen some people saying to stop gracefully Distributed cache patch and before run psconfig remove-dist…cache others just said stop gracefully and patch and run psconfig which one will be the best approach. Thank you Stefan one more time.

        1. You should follow the instructions here:
          (check the “Start and stop the Distributed Cache Service” section)

Skip to main content