November 2017 CU for SharePoint Server 2016 is available for download

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

The KB articles for November 2017 CU are available at the following location:

  • KB 4011244 - November 2017 Update for SharePoint Server 2016 (language independent) - This is also a security update!
  • KB 4011243 - November 2017 Update for SharePoint Server 2016 (language dependent fixes)
  • There was no fix released for Office Online Server 2016 in November 2017

The download for November 2017 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 November 2017 CU Build Numbers:

Language Independent fix: 16.0.4615.1000
Language Dependent fix: 16.0.4615.1000

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

Cancel reply

  1. Bart Plessers says:

    Installed but error on Configuration wizard on the end. IIS has to be started manually, and then SharePoint seems to be running again on version 16.0.4615.1000. However, I do not feel comfortable with the config wizard not ending successfully. Anybody else experiencing the same problem?

    1. Hi Bart,
      which error did you get in the config wizard?
      And which step was failing?
      Usually config wizard show a pretty good explanation of the error and the necessary restart command to be used after fixing the issue.

  2. Andre says:


    quick question. Do I have to install WSS at first and then STS Update, or vice versa? Can I install both updates and then run the config wizard? Also for the this question is the order important (wss and then sts or vice versa?!?).

    1. Hi Andre,
      the sequence does not matter. You should install both fixes together and then run the config wizard only once after all fixes are installed.

      1. Andre says:

        Hi Stefan,

        thanks for the quick reply. I will proceed as you recommended. Thanks you so much!

        Best regards

  3. Erik Augustsson says:

    After I installed this I got errors on psconfig-gui “Upgraded database doesn’t match the targetSchema (eventId:an59t).
    Dismounting databases and running it again solved that problem.
    However, then get-spwebapplication returned nothing so I couldn’t mount the databases until I restarted the server.
    Singleserver-farm so might be unlucky, but we’ll see when it goes into production 🙂

  4. Dominik says:

    Hi Stefan,

    is this correct that this Update also includes the October Patches?


    1. Dominik says:

      Because I Installed the November Updates and forgot that my Colleague did not installed the October and September Patches..

      Oh and by the way: A huge Thanks for doing this blog 🙂

      1. Yes, thats correct. All previous cus are included.

  5. SJNBham says:

    Installed a brand new SharePoint 2016 Enterprise farm and applied the Nov 2017 CU packages (they show up in installed updates):

    – Security Update for Microsoft SharePoint Enterprise Server 2016 (KB4011244)
    – Update for Microsoft SharePoint Enterprise Server 2016 (KB4011243)

    When I try to run the Products Configuration Wizard, it fails on checking the server farm product and patch status. It shows both of the packages above as missing on server “” (blank).

    I ran the “get-spproduct -local” command and it didn’t resolve the issue.

    Anyone else experience this or have a workaround? I’ve seen other posts citing ways to force the upgrade using psconfig.exe. However, I’m hesitant to do this since this is a brand new farm and want everything to install clean.

    Thanks for any info you can pass along.

    1. Hi,
      this is a known issue if your config db contains information about a server which is no longer in the farm but has not been properly removed.
      Looks as if you reused an old config database rather than creating a new one with your new farm.

  6. TD says:

    I have a new small farm install and in the process of installing the November CU. No other patching has been performed. The config wizard has been running for well over 15 hours and is still at 10% complete, with no real errors within the log file. High level messages are like:
    Entering monitored scope: (Fetch object from file system: Fetching object [7b7cbc85…
    Deserializing the type named….
    refreshed SPPersistedObject with Name Upgrade-20171205-105443….
    Leaving Monitored Scope
    ULS Init completed

    The entering monitored scope fetching object is the same number throughout the log file, but there are no errors.

    Any ideas as to why this would continue to be sitting at 9 of 10 and at 10% complete? Or does it just take that long to complete all CUs?

    1. Hi Tracy,
      that is not normal execution time.
      My recommendation is to open a support case with Microsoft to get this investigated.

  7. Agasthya says:

    After the update I am getting the following errors which running my CSOM code. Any idea what the issue could be?
    1. Sending HTTP response 401 – text/plain:401 UNAUTHORIZED
    2. The remote server returned an error: (400) Bad Request.
    3. Error when processing types in server stub DLL Microsoft.FileServices.ServerStub.Beta
    4. Error in ProxyMap.Init. Exception=System.IO.FileLoadException: Could not load file or assembly.

    FYI, My updates were installed by Windows Automatic updates and later I ran the Psconfig util to complete the SP upgrade.


    1. Hi Agasthya,
      did you run the sharepoint config wizard (UI version) or the command line version?
      In case you used the command line version did you ensure to use all the parameters as outlined here:
      PSConfig.exe -cmd upgrade -inplace b2b -wait -cmd applicationcontent -install -cmd installfeatures -cmd secureresources -cmd services -install

Skip to main content