October 2017 CU for SharePoint Server 2016 is available for download

The product group released the October 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 October 2017 CU are available at the following location:

  • KB 4011217 – October 2017 Update for SharePoint Server 2016 (language independent) – This is also a security update!
  • KB 4011161 – October 2017 Update for SharePoint Server 2016 (language dependent fixes)
  • KB 3213659 – October 2017 Update for Office Online Server 2016 – This is also a security update!

The download for October 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 October 2017 CU Build Numbers:
Language Independent fix: 16.0.4600.1002
Language Dependent fix: 16.0.4600.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:


  1. I think it is important to highlight the following on your blog as it is stated as mandatory before applying this update:
    Registry information
    Follow the steps in this section carefully. Serious problems might occur if you change the registry incorrectly. Before you change it, back up the registry for restoration in case problems occur.
    After you install this update, you can follow these steps to control the metafiles optimization:
    Start Registry Editor:
    In Windows Server 2012, if you’re using a mouse, move it to the upper-right corner, go to Search, and then enter regedit in the search text box.
    Select regedit.exe in the search results.
    Locate and then select the following registry subkey:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\16.0\WSS\
    On the Edit menu, point to New, and then select DWORD Value.
    Enter BypassDboDropMember, and then press the Enter key.
    In the Details pane, press and hold (or right-click) BypassDboDropMember, and then select Modify.
    In the Value data box, enter 1, and then select OK.
    Note If you don’t want to bypass the behavior, you can set the value to 0.
    Exit Registry Editor.
    Security update deployment information


    1. Hi Islam,
      from the KB article:
      As part of SharePoint database upgrade, the members of the db_owner role are deleted from the role, except for the “dbo” user and the user who is performing the upgrade. This is done for enhanced security to make sure that an errant account isn’t inadvertently left having the db_owner role privileges. However, there may be situations in which this behavior is not desirable. For example, RBS may be broken every time that an upgrade is run. In this situation, a registry key is added to bypass this behavior.
      With other words: this is not mandatory – this is optional and only applies to certain specific situations.


  2. Hi,
    do i have to set the SideBySiteToken onto 16.0.4600.1002 or 16.0.4600.1000
    i would say 16.0.4600.1002
    (our sharepoint is english with a german languagepack)
    $webapp.WebService.SideBySideToken =


    1. Hi Tobias,
      you always have to pick the highest applied build number.
      With other words: 16.0.4600.1002


  3. Hi Stefan,
    I did the October KB 4011217 Update and ran PSConfig. I could now create SPFx in SP 2016. However the configuration DB is at build 16.0.4600.1001 . The upgrade status in CA is “No Action Required” . I believe the build should have been ideally 16.0.4600.1002 , but in CA and PowerShell cmdlet “(Get-SPFarm).BuildVersion” shows “16.0.4600.1001” . Can you please shed some light on this. Is there something I am missing ?


Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.