Windows 10 1607 is now a Current Branch for Business (CBB) release


Today I am pleased to announce that Windows 10 1607, also known as the Windows 10 Anniversary Update, has been declared as Current Branch for Business (CBB) and is ready for deployment. This is an important milestone and signifies that this version has been validated by customers, OEMs and partners giving organizations the confidence to further accelerate deployments at scale.

To reach this milestone, we have addressed nearly a thousand items of feedback from all types of customers, including enterprises performing pilot deployments. With hundreds of millions of devices already running the CBB version 14393.447 installed by KB 3200970 or any later update, as indicated in the Windows 10 Release Info page, organizations can be assured Windows 10 1607 is fully ready for them.

The market reaction to Windows 10 has been unprecedented with a 3X increase in Windows 10 enterprise deployments over the last six months. It has been incredible to see customers from around the world embrace Windows 10, including Australian Department of Human Services, Hendrick Motorsports and Crystal Group of Companies. We have also seen strong engagement from our partner ecosystem with over 900 of our largest partners trained this year alone on Windows 10 deployment.

With Windows 10 we set out to provide both advanced security and the best platform for reducing the complexities of modern IT. By implementing Windows 10, customers are 58% less likely to encounter ransomware than when running Windows 7. Enhanced cloud infrastructure allows our antimalware researchers to utilize machine learning models to identify and block malware more quickly, improving response time from hours to just minutes.

Windows 10 is also simplifying IT and significantly reducing deployment times. For example, with Windows Upgrade Analytics, customers can better assess their readiness for Windows 10 deployment and reduce an upgrade process that used to take years to just months or weeks. Windows 10 is also our most compatible release ever and with 99% of the top 3,000 apps shown to be compatible, customers are deploying at scale with confidence.

For most organizations, no specific action is needed to take advantage of this CBB declaration. If you have the latest cumulative update installed, you are all set. We do expect to publish updated media to the Volume Licensing Service Center and to Windows Server Update Services (WSUS) in January for those customers that need it, but this is primarily just for convenience.

Businesses are seeing significant value, enhanced security and improved productivity with Windows 10 today. With the Windows 10 1607 Current Branch for Business declaration, now is the time to accelerate your Windows 10 deployment.

 

Comments (18)

  1. Matt Wilkinson says:

    Can you clarify how long 1507 and 1511 will receive updates?
    I haven’t found a clear technet article outlining this.

    1. As we described in the Windows as a service docs at http://aka.ms/waas, we service and support two CBB releases at all times, so the end of servicing for a particular release is dependent on the timing of the N+2 release. It will be at least 18 months, but can be longer when releases are more than six months apart.

      Because there are two newer CBB releases, Windows 10 1507 will not be serviced much longer – as I mentioned in a previous reply, the 60-day countdown (the grace period described in the Windows as a service docs) will start in January, meaning the last updates for Windows 10 1507 will be in March.

      For Windows 10 1511, the end of servicing will be about six months after the CBB declaration for the next Windows 10 feature update (the Creators Update, due out early next year). So Windows 10 1511 will be serviced at least through the middle of 2017, possibly longer depending on the actual release date of the next feature update.

      1. TMorgan says:

        If each Feature Update is going to be supported for a minimum of 18 months, does this mean you will no longer aim to release 3 Feature updates per year (originally forecasted as 3-4, but revised to 2-3)?
        As over time the relationship between the number of releases, support time frame and support of two versions will no longer work.

        1. We have documented at http://aka.ms/waas that our target is 2-3 times per year. That has been our stated target since the Windows 10 launch.

          1. TMorgan says:

            How can you have three updates in a year and still have at least 18 months support, plus maintain only the latest 2 versions? Even releasing a Feature Update in January, there is not enough time in a year to meet this equation.

  2. remco8264 says:

    When will it start rolling out to users who have ‘Defer upgrades’ enabled?

    1. In January, with the availability of the updated bits on Windows Update. (For PCs managed by WSUS or ConfigMgr, the updated bits still need to be deployed; the IT admin can choose when.)

  3. EA says:

    Does this mean Windows 10 1511 is going to be officially discontinued (since LTSB: 1507 and CB / CBB: 1607)? If not, in a few years there will be a lot of versions for both Microsoft and developers to maintain…

    1. We always service and support the latest two CBB releases.  That means that Windows 10 1507 is nearing the end of its servicing.  The 60-day grace period for Windows 10 1507 will start in January (coinciding with the availability of the updated Windows 10 1607 bits), so the last updates for Windows 10 1507 will be in March. 

      1. Each LTSB release (Windows 10 Enterprise LTSB 2015 and Windows 10 Enterprise LTSB 2016) is serviced and supported for 10 years (five years standard, five years extended with security-only fixes).

  4. TMorgan says:

    With a view to planning for future updates, will there be any advance notification/warning for the CBB releases? And how is this going to be communicated going forward, for those needing to plan this in for the business with testing and deployment?

    1. Our target is to declare a release as CBB (and therefore ready for broad deployment) about four months after the CB release. Generally we announce CBB as soon as that signoff has occurred, and added a 60-day grace period on the N-2 version to make sure it doesn’t catch organizations by surprise for the version that won’t be serviced any more.

  5. Mark Taylor says:

    I’m not seeing it in my CBB ring in SCCM 1607 yet. Not set for any delay offset.
    I’ve downloaded W10E 1607, injected the most recent updates, with SCCM, into the upgrade package. that has worked well, but I was expecting my CBB ring to burst into life today. does this mean it won’t be in WSUS until Jan?

    1. As indicated in the blog, updated media will be published in January (to Windows Update and WSUS; ConfigMgr gets it from WSUS). At that point, ConfigMgr should indicate that Windows 10 1607 is CBB.

  6. Michael Calabrese says:

    Michael – We are using the 1607 bits that we downloaded from the MVLS site several months ago. In our testing we are seeing some patches coming down from Microsoft Windows Update even though we have a WSUS policy in place pointing at a local WSUS server. Is this because we don’t have the refreshed bits that you mentioned that are coming in January?

    1. No, this is not related to the refreshed bits. I would suggest contacting Microsoft Support on that issue, as it is likely tied to the Windows Update for Business settings applied to the computer (e.g. specifying to “Defer upgrades”).

  7. ChanakaC says:

    You mentioned that the media will be published in January, So far we are not able to see it in the Volume Licensing Service Centre. Is there any date which you can specify ?

Skip to main content