Updated Windows 10 v1607 (14393.447) install media available

[Arthur]

Updated ISOs for both Windows 10 v1607 and Windows Server 2016 are now available to download from MSDN or from VLSC on 26th January.

 

If you have been using the original v1607 (build 14393.0) ISOs to do clean installs of Windows 10 then you may have found that Windows Update cannot communicate with your WSUS server to download further updates post-install. These new ISOs include the November 2016 cumulative update (build 14393.447) which means that you won't suffer from this issue (or any of the other bugs fixed between when the Anniversary Update was released and November 2016).

 

^ This is why it's always a good idea to integrate the latest CU (and Servicing Stack if available) into your reference image either with MDT or DISM.

 

Source: Microsoft

 

On 29th November 2016, 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 26 January 2017.

 

As we mentioned in our 29th November blog post, for many organizations, no specific action is needed. If you have already installed the December cumulative update (KB 3201845), 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 26th January, the 60-day grace period for Windows 10, version 1507 will begin. That means, after 26th March 2017, Windows 10, version 1507 will no longer be serviced as only the two most Current Branch for Business (CBB) versions are actively serviced.

 

Edited January 21, 2017 by Arthur

[ITGURU]

We are running the original 1607 release anniversary edition.

Since imaging the PCs, all have checked into WSUS, downloaded updates I approve, installed on the clients, rebooted and report 100% status.

What should be happening again.......

[Arthur]

Since imaging the PCs, all have checked into WSUS, downloaded updates I approve, installed on the clients, rebooted and report 100% status.

There were definitely multiple WSUS-related issues in the initial Anniversary Update release. There's a long thread on EduGeek about them. You must be lucky.

 

http://deploymentresearch.com/Research/Post/540/Building-a-Windows-10-v1607-reference-image-using-MDT-2013-Update-2

 

 

 

https://blogs.technet.microsoft.com/windowsitpro/2017/01/19/windows-10-v1607-media-now-available

 

 

We are running the original 1607 release anniversary edition.

Are you imaging your PCs using the unmodified install.wim directly from the ISO?

Edited January 21, 2017 by Arthur

[Arthur]

VLSC now has the new ISOs too.

 

 

Edited January 26, 2017 by Arthur

[Arthur]

An updated LTSB 2016 ISO will be available on VLSC in June 2017.

[newpersn]

After i do my reimage, before i join the computer to the domain i get windows updates to run during MDT task. Will this help or am i better off recreating my base image?

[Localtechie]

Just to confirm in VLSC that updated November 2016 is today's ISO release.

 

We are having an issue with updates failing and want to double check it is the latest one and is MSDN it is saying January 2016?

 

Thanks

[Arthur]

We are having an issue with updates failing and want to double check it is the latest one and is MSDN it is saying January 2017?

The VLSC and MSDN ISOs are identical even though one says November 2016 and the other January 2017. Both include the November 2016 CU.

 

MS isn't very good at naming things!

 

Edited January 26, 2017 by Arthur
Clarification

[Arthur]

Will this help or am i better off recreating my base image?

Unless you are having issues it's probably not worth it.

[jmak]

Still feels weird that the clients that I built with Windows 8.1 in 2015 will continue to receive security updates until 2023, but the machines I built with 1511 last summer will stop receiving security updates before the end of this year.... 6 years earlier.

 

We really are going to have to learn to trust MS more - testing cycles are going to be really compressed.