Feature Pack 2 for SharePoint Server 2016 (aka September 2017 CU) is available for download


The product group released the Feature Pack 2 for the SharePoint Server 2016 product family.

Through the Feature Pack 2 which is included in September 2017 CU for SharePoint Server 2016 we’re delivering several new features based on customer feedback and developer needs, highlighting these investments, the SharePoint Framework.

The SharePoint Framework (SPFx) is a page and web part model that provides full support for client-side SharePoint development, easy integration with SharePoint data and support for open source tooling. With the SharePoint Framework, you can use modern web technologies and tools in your preferred development environment to build productive experiences and apps on SharePoint that are responsive and mobile-ready from day one!

Feature Pack 2 for SharePoint Server 2016 contains the foundation of modern web part hosting and editing experiences, including core SPFx APIs, SPFx package deployment, and property panes.

To learn more about these enhancements refer to https://go.microsoft.com/fwlink/?linkid=856819.

Feature Pack 2 also includes all the features earlier released in Feature Pack 1.

For more details about Feature Pack 2 please have a look at Bill Baers official blog post.

The KB articles for September 2017 CU with Feature Pack 2 are available at the following location:

  • KB 4011127 - September 2o17 Update for SharePoint Server 2016 with Feature Pack 2 (language independent) - this is also a security update!
  • KB 4011112 - September 2017 Update for SharePoint Server 2016 with Feature Pack 2 (language dependent fixes)
  • KB 3213658 - September 2017 Update for Office Online Server 2016 - this is also a security update!

The download for September 2017 CU is available through the following link:

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 September 2017 CU Build Numbers:

Language Independent fix: 16.0.4588.1001
Language Dependent fix: 16.0.4588.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 (12)

  1. Hans says:

    Oh, I really thought the Feature Pack 2, would contain the modern experience as seen in SharePoint online. So much for the excitement.
    With modern team sites, pages and more. Maybe I’m looking in the wrong place but I can’t find the settings for turning this on in on-premise.
    Bummer…….

    1. M.Qassas says:

      Hi Hans,

      Unfortunately, There is no Modern Team Site in SharePoint 2016 On-Prem yet! The release of ‘Feature Pack 2 for SharePoint Server 2016’ provides you to only use and build the SharePoint Framework **WEB PARTS** hosted in the classic web part pages of SharePoint Server 2016.

      Please read more at-

      https://dev.office.com/blogs/now-available-deploy-sharepoint-framework-web-parts-to-sharepoint-server-2016-with-feature-pack-2
      https://blog.devoworx.net/2017/09/16/sharepoint-framework-for-sharepoint-server-2016/
      https://dev.office.com/sharepoint/docs/spfx/sharepoint-2016-support

  2. Anon says:

    After installing Sep 2017 Independent + Dependent , the timer service stopped and didn’t start by any means

    1. M.Qassas says:

      I’ve updated my SharePoint 2016 Staging Environment with Sept 2017 that has been installed and configured successfully without any issue related to Timer Service,

      So I think you should try to check the following:

      1. If you can’t stop and start the timer service via CMD, try to open ‘Task Manager’ > In ‘Process’ Tab, check the ‘SharePoint Timer Service’ > Right click, End Process.
      2. Now, go to ‘Services’ > Right Click on ‘SharePoint Timer Service’ > Properties > at ‘Log-On’ tab, try to provide again the correct credentials of your farm account
      3. Open CMD as Administrator > Start the SP timer service again as “net start SPTimerV4”
      4. Also, Make sure that the SQL Server service is running with the correct Log-on information.
      5. Now try to start the Sharepoint Configuration wizard to reflect the installed patch on your farm.

  3. Anon says:

    By the way, I installed CU Sep 2017 on RTM

  4. M.Qassas says:

    Hi Stefan Goßner, Thank you so much for everything you share with us,

    I think there is a bit typo note at the “SharePoint 2016 November 2016 CU Build Numbers:” that should be “SharePoint 2016 September 2017 CU Build Numbers:”

    1. You are right – thanks for the hint!
      I have updated the info.

      1. M.Qassas says:

        Great, another question Please? Is ‘September 2017 update for SharePoint Server 2016’ considered a CU or PU?

        1. In this context it is a CU as it includes all previous PUs and CUs as well.
          It also includes a PU which is the language independent part as it includes new security fixes.
          Cheers,
          Stefan

          1. Mohanghimire says:

            Hi Stefan,
            we used to have CU (full server package) for 2013 and didn’t see any language independent or dependent download .However, for 2016 we see something different , I believe we just install language independent package ? when is language dependent package required and impact not installing it ?

          2. Hi Mohanghimire,
            the reason is the different packaging model. In SP2013 you would have to maintain 30+ packages for SharePoint and it would be hard to keep all up2date. So we created the full server packages.
            With SP2016 we only have two packages – so no need for a full server package as it should be simple to install two packages.
            Cheers,
            Stefan

          3. Just to add: you always need both packages.
            SharePoint comes with an language independent component and one built in language (e.g. if you install russian SharePoint you have the russian language built in) plus additional lanuguages you can install on top through language packs.

Skip to main content