Updated – This post is changed with CU KB3176495
When Windows 10 1607 was released the version number is 14393.0 but within the first 24 hours the first Windows 10 1607 Cumulative Update https://support.microsoft.com/en-us/help/12387/windows-10-update-history.
To get the Windows 10 1607 up to date and to generating the users as little as possible – the solution is to use a Inplace Task Sequence.
Windows 10 1607 is only supported on SCCM 1606 so it is requirement.
- Import Windows 10 1607 OS into SCCM
- Create a package with KB3176495
- Create Task Sequence
- Modify Task Sequence
- Run the Task Sequence on a device
Import Windows 10 1607 OS into SCCM
Add Operating System Upgrade Package
- Browse to the packages source with the content of the Windows 10 1607 ISO
- Click Next
Click Next
Click Next
Click Close
Now distribute the content to the SCCM DP
Create a package with KB3176495
Download the KB3176495 and place it in your packages share
Create Package
- Enter the name of the package
- Enter manufacturer
- Browse for the KB3176495 on the package share
- Click Next
Click Next
- Enter a program name
- Enter Commandline “wusa.exe AMD64-all-windows10.0-kb3176495-x64_a344b21f039bfc4c4c145af471da86005fa4288f.msu /quiet /norestart”
- Select “Whether or not a user is logged on”
- click Next
Click Next
Click Next
Click Close
Now distribute the content to the SCCM DP
Create Task Sequence
Create Task Sequence
Select “Upgrade an operating system from an upgrade package”
Click Next
Enter Task Sequence Name
Click Next
Browse for the OS upgrade package
Click Next
Click Next
Click Next
Click Next
Click Close
Modify Task Sequence
Add Install Package under “Post-Processing”
Browse for the patch package
Create a Restart Computer Action after the install package
Change the setting to “The currently installed default operating system”
Deploy the Task Sequence
Run the Task Sequence on a device
On the Windows client you are ready to upgrade to Windows 10 a607 with the Task Sequence
Click Install in the Software Center
Click Install Operation System
Now the Inplace upgrade is starting
After the first reboot the device is being upgraded to Windows 10 1607
After the first user login it will take some time to prepare
When the desktop is ready the OS version is 1607 with a OS build 14393.51
Mobile-First Cloud-First 
Great post! Very helpful. I would add a couple items for clarification – like distributing out the content and on the reboot step specify to choose “The current installed operating system” because it defaults to “The boot image assigned to this task sequence.” Again, great post!
I have change the post 🙂
How many minutes have you seen the update take?
“[…] all the existing data on your computer will be removed.”
So they still haven’t fixed the misleading warning when you run the TS? Too bad.
Thank you for sharing now, you can use provided method to deploy Windows 10 ver 1607 Build 14393.82 released on August 23, 2016 https://support.microsoft.com/en-us/kb/3176934
Hi,
I’m sure I’m missing something somewhere, but under “Windows 10 Servicing” in SCCM 1606 there’s a list of all the various 1607 language and version builds.
From there, you can download it and deploy it to machines and it appears in software center (installing it is failing so this may answer my next question).
So as there appears to be a built in way of upgrading, say, 1511 to 1607, what’s the reason for using Operating System Upgrade Packages?
With the TS you can also run any other tasks you may need, such as removing modern apps or applying additional updates (as in this post). That said using a Software Update method is much more friendly from a user point of view because it acts like a normal update rather than showing task sequence progress etc.
I can upgrade my Windows 7 to windows 10 with guide successfully but only the Package with KB3176938 does not work. The installation is aborting while to install the KB3176938. with error code 0x4005(16389). Any Idea why?
Having the same problem with the patch package as Keywan.
Hello,
Your command line is missing a dash sign before x64:
“wusa.exe AMD64-all-windows10.0-kb3176495x64_a344b21f039bfc4c4c145af471da86005fa4288f.msu /quiet /norestart”
It should be:
“wusa.exe AMD64-all-windows10.0-kb3176495-x64_a344b21f039bfc4c4c145af471da86005fa4288f.msu /quiet /norestart”
Cheers.
Do you guys use 1607 before it goes CCB?
Yes – where we need the feature of 1607 oreskov starten with a new Windows 10 deployment.
Hello and thank you for the article!
Does it work the same with LTSB editions ?
Yes it does. From LTSB 2015 to LTSB 2016