Windows 10 v1607 media now available


UPDATE: 2/3/2017: End of servicing for Windows 10, version 1507 will now occur in May.

On November 29th, Windows 10, version 1607 was declared the Current Branch for Business (CBB), indicating that Microsoft, independent software vendors (ISVs), partners, and customers believe that the release is ready for broad deployment.  Today we are releasing updated media for Windows 10 v1607 (also known as the Windows 10 Anniversary Update) on Windows Update for Business, Windows Server Update Services (WSUS), and MSDN Subscriptions. We will also be releasing updated refreshed media for Windows 10, version 1607 to the Volume Licensing Service Center (VLSC) on January 26, 2017.

As we mentioned in our November 29th blog post, for many organizations, no specific action is needed. If you have already installed the November cumulative update (KB 3200970), or any later cumulative update, that device is already running the equivalent of what was declared to be CBB.

End of servicing for Windows 10, version 1507

With the availability of Windows 10, version 1607 to the VLSC on January 26th, the grace period for Windows 10, version 1507 will begin. That means, after May 2017, Windows 10, version 1507 will no longer be serviced as only the two most Current Branch for Business (CBB) versions are actively serviced.

Additional information

For the latest list of Windows 10 feature updates, and current versions by servicing option, see our Windows 10 release information page.

If you haven’t yet finalized your servicing strategy for Windows 10, watch our quick 5-minute video overview of Windows as a service or read this quick guide.

Comments (31)

  1. Ryan Goff says:

    Will you be releasing an updated version of the 1607 WSUS update including the latest fixes?

    1. this updated CBB media include fixes for the WSUS issues that were in the initial release. These were released via a cumulative update, which is included in the CBB release.

      1. tim ponder says:

        Can you refer a link regarding the WSUS issues? I’m trying to make a reference 1607 image using MDT 8443 with ADK1607. I injected CU KB3213986 (Jan) but ZTIWindowsupdate.wsf continues to fail. cmtrace error lookup (8024401c) states server timeout but I don’t have issues with Win7 and Win8.1 imaging. Any advice is appreciated.

        1. that is not a symptom the WSUS issue that was in v1607 CB

          I’m guessing that error is a configuration issue, maybe specifying the wrong port for MDT to use. You may have specified:

          WSUSServer=http://server

          Instead of:

          WSUSServer=http://server:8530

          Or

          WSUSServer=https://server:8531

  2. MELERIX says:

    imho updated media ISO images for Windows 10 v1607, should be available for any user and not only for MSDN.

    1. you can easily make your own media.

      download and install Windows ADK

      Run Deployment and Imaging Tools Environment and then select Run as administrator.

      Create a mount directory for your Windows image (install.wim), and then mount the image.

      md C:\mount\Windows
      Dism /Mount-Image /ImageFile:”C:\Images\install.wim” /Index:1 /MountDir:C:\mount\Windows
      Copy

      Update your Windows images with the latest Cumulatative UpdateExample:
      Dism /Add-Package /Image:C:\mount\Windows /PackagePath:C:\MSU\Windows10-KBxxxxxxx-x64.msu /LogPath:AddPackage.log
      Copy

      Where C:\MSU\Windows10-KBxxxxxxx-x64.msu is the Cumulatative Update you want to install.

      Unmount the Windows image.
      Dism /Unmount-Image /MountDir:C:\mount\Windows /Commit

      1. MELERIX says:

        yes, I know, but I mean the official and clean ISO images made by Microsoft, should be available for any user, for clean installations purposes or even for offline upgrades, and not only for MSDN.

        1. Media Creation Tool will create ISOs and will shortly download an updated v1607

      2. Enrico says:

        I support MELERIX view: we would need clean ISO also for non MDSN users; for offline installations you could not always create your own media on the fly.

        1. Media Creation Tool will shortly download an updated v1607 ISO

      3. Glenn Turner says:

        Can you please confirm that if we dism the relevant Cumulative Update + Servicing Update + Flash into the WIM, we will end up with the same content that is available on the VLSC? No other updates or changes in the ISO?

        In other words, is there any point us downloading it if we already DISM CUs into the WIM for deployment?

        1. as per https://technet.microsoft.com/en-us/windows/release-info.aspx v1607 CBB = build 14393.447 which is v1607 + KB3200970

  3. John Doe says:

    When will CB end?

    1. End of servicing for Windows 10, version 1507 will now occur in May 2017.

  4. Brian Hoyt says:

    Everyone is reporting that support is ending for 1507 CB. Above you only mention 1507 CBB. Is all 1507 support ending in March or only for CBB? If it is only CBB then someone needs to clearly and loudly state that since it is being widely reported incorrectly. Thanks.

    1. End of servicing for Windows 10, version 1507 will now occur in May 2017.

  5. Mike Firth says:

    Thanks for the info Nathan.

    May I ask you to clarify something regarding the end of 1507 support; we currently have 1507 deployed at scale under Enterprise LTSB, so of March 26th, do we need to do something manually to upgrade those machines, or will 1507 be updated via the WU service to the next LTSB version automatically?

    Thanks!

    1. Enterprise LTSB 2015 is supported for 10 years and is not affected by the end of servicing of v1507. By design, Enterprise LTSB versions never update via WU, you will need to upgrade using media/ISO etc.

  6. Hussain Lakhani says:

    So that means no Critical Security Update will be applied to v1507 after March 2017?

  7. Frank Bevers says:

    it is my understanding that a 60 days grace period applies from the day CBB media are made available in the vlsc. For 1607 that was on january 26th 2017 so I’d expect that march 26th 2017 support would end for 1507 or is this 60 days period to be somewhat loosely interpreted ? What will happen with 1507 installations that are on CBB ? Will they simply get no more (quality) updates without being forced / nagged to upgrade to a more recent version ?

    1. after May 2017 CB/CBB v1507 will receive no more updates. Think of the grace period as “at least” 60 days.

      1. Glenn Turner says:

        Will Cumulative updates for LTSB2015 released after May be installable on 1507, or will Microsoft build logic into the LTSB2015 CU installers to ensure that people can’t use that loophole to stay on the unsupported 1507.

        1. Windows 10 Enterprise LTSB 2015 is different to v1507. LTSB is supported for 10 years. v1507 will no longer be serviced after May 2017.

      2. Frank Bevers says:

        Thinking some more on this whole upgrade mechanism; is it actually possible for someone who had 1507 to still be on 1507 in a non managed environment (no wsus, sccm etc) In other words isn’t upgrading enforced in those circumstances?

  8. Andy says:

    Will this also apply to Windows 10 Education that is still on 1507?

    1. yes this applies to all editions of Windows 10 v1507 incl Education

  9. Dazed and confused says:

    Once a version of Windows 10 is no longer supported and the ‘grace’ window has expired, how can one get a supported version of Windows 10 installed to replace the unsupported version? Do you have to purchase another license? Do you have to burn a disk? Will you get offers to update at not cost? Why is this not explained clearly somewhere?

    1. You will always be able to install a later feature update from Windows Update, WSUS, or even manually using media. (You would need to still have a valid subscription if you are upgrading Windows 10 Enterprise or Windows 10 Education.)

  10. John Morgan says:

    Almost following MS original posts relating to timing on WIn10 support…
    There is a 4 month grace period instead of 2 (Jan-May)…
    VSLB was not previously mentioned and is the new trigger for that grace period start instead of CBB release (VSLB came in Jan 2017 for 1607 & CBB was Nov 2016 for 1607).

    Are these criteria an anomaly or the norm now?

    1. John Morgan says:

      VLSC not VSLB…sorry for the error

Skip to main content