Jump to content

Recommended Posts

Posted (edited)

MSDN only at the moment. 1st May 2017 for VLSC ( :( ). The 1703 ADK can be downloaded from here.

 

What's New (Microsoft / ChangeWindows.org)

 

ZUdZlv.png

 

en_windows_10_education_version_1703_updated_march_2017_x64_dvd_10189297.iso
SHA-1: FDC69E1C3E588A8B96FA9AAD8F82458522E59365

en_windows_10_education_version_1703_updated_march_2017_x86_dvd_10188968.iso
SHA-1: 0DEC4D66434C7A2BC7BC7DFAEB3E8000FA8AE334

en-gb_windows_10_education_version_1703_updated_march_2017_x64_dvd_10195585.iso
SHA-1: DA2B5EE81549735AFFD8B111C0D32001A970A78B

en-gb_windows_10_education_version_1703_updated_march_2017_x86_dvd_10192285.iso
SHA-1: 2E36455F7C647F8F688162DD8F642607AFD0CCFB

 

en_windows_10_enterprise_version_1703_updated_march_2017_x64_dvd_10189290.iso
SHA-1: 77D5E7C91B5DBBEE410FB6C57CB944238BF7176A

en_windows_10_enterprise_version_1703_updated_march_2017_x86_dvd_10188981.iso
SHA1: DE7F15A1DE19BD9507B5B5693E3F56D10F662864

en-gb_windows_10_enterprise_version_1703_updated_march_2017_x64_dvd_10194889.iso
SHA-1: 129C4701F3DC518D49348B9463D01CF4DEA446D8

en-gb_windows_10_enterprise_version_1703_updated_march_2017_x86_dvd_10191843.iso
SHA-1: E9214D9039D6CB5B7534064C528124F3BCE3D436

 

en_windows_10_multiple_editions_version_1703_updated_march_2017_x64_dvd_10189288.iso
SHA-1: CE8005A659E8DF7FE9B080352CB1C313C3E9ADCE

en_windows_10_multiple_editions_version_1703_updated_march_2017_x86_dvd_10188977.iso
SHA-1: 1AF7B5B5914B718C3F2F6E58907F51C36F8A03C1

en-gb_windows_10_multiple_editions_version_1703_updated_march_2017_x64_dvd_10194881.iso
SHA-1: 9610F2DC13E101801379045F031074FB845AAE0E

en-gb_windows_10_multiple_editions_version_1703_updated_march_2017_x86_dvd_10191736.iso
SHA-1: 3476CA333B0AE0057E9D7D50BCD3B54F4FDB07FA

Edited by Arthur
Posted (edited)
I wonder if there be an upgrade tool like there was for 1607....

There's a brand new Media Creation Tool for 1703 (for the Home and Pro editions)...

 

http://download.microsoft.com/download/1/F/E/1FE453BE-89E0-4B6D-8FF8-35B8FA35EC3F/MediaCreationTool.exe

 

voYQAz.png

 

It's also possible to upgrade via the Update Assistant.

 

http://download.microsoft.com/download/0/4/7/047889D0-578C-4A44-A38F-7F30A6CB3809/current-version/Windows10Upgrade9252.exe

 

https://arstechnica.com/information-technology/2017/04/the-windows-10-creators-update-is-now-available-for-manual-upgrading/

 

The Windows 10 Update Assistant will upgrade any Windows 10 Home or Pro system to the Creators Update; you'll need to grab the latest version of the Assistant and then run it, but it should be straightforward enough. If you're upgrading more than one machine or want to perform a clean install, the Media Creation Tool, available from the same link, is the better bet; the Media Creation Tool can fetch an ISO to burn a DVD or create a bootable USB drive, and that can be used for bare metal installs.

 

jVRNX8.png

Edited by Arthur
  • Thanks 1
Posted
I rebuilt my PC today, used the Windows creation tool and it gave me 1703! Was a nice surprise.

That was exceptionally good timing! I think I will upgrade my home PC shortly too. :)

Posted
Been waiting for this, hopefully this will be the version I deploy across the school this Summer. Gives enough time for some of the quirks to be found!
Posted

1703 doesn't seem to work properly with SCCM yet either.

 

When deploying a 1703 image, after the first reboot where it runs the "Setup Operating System" group it doesn't show anything other than the spinning dots and a message saying "Just a Moment", instead of showing the actual task sequence running, a little annoying but it still works :)

Posted (edited)

Oooh I used the upgrade assistant to update my 10 Edu VM, now copied the policy definitions across. No Control Panel is freaky. Half of the disk space now taken up by Windows.old again. Time to play with the GPs.

 

Arggghh. Stopping the Microsoft Edge Tips tab from loading will become a personal mission it seems.

Edited by 3s-gtech
Posted (edited)

No, of course I hadn't seen it - I've been searching in User Configuration like a confused, drunken old fool. You know, User Configuration - where MS used to put the user settings before they decided to put them all in Computer Configuration.

 

I've set that so time to try it! *Edit* Hoorah it works!

 

I'm impressed the the Start XML still works. Not looking forward to yet another new build without the Apps and fluff.

Edited by 3s-gtech
Posted
No, of course I hadn't seen it - I've been searching in User Configuration like a confused, drunken old fool. You know, User Configuration - where MS used to put the user settings before they decided to put them all in Computer Configuration.

 

I've set that so time to try it!

 

I'm impressed the the Start XML still works. Not looking forward to yet another new build without the Apps and fluff.

 

I was surprised to see the Start XML still working too :p Do you not use a script to remove the Apps?

Posted
Not after imaging no - that adds too much time to each user logon for me. I strip them out of the ISO itself (from @Arthur's instructions) which gives a much cleaner OS image.

 

The script I have runs during the deployment of the machine. The script I was using to remove them from the WIM no longer works for me :( do you have a script that works on 1607 and above ISOs/WIMs?

Posted
http://www.edugeek.net/forums/windows-10/165029-how-get-rid-candy-crush-soda-saga-other-windows-10-start-menu-junk-good-8.html#post1559851

 

During deployment sounds okay - I still use FOG so not so easy for me, that's why I stripped them out early.

 

The reasons I do it during deployment is because the below part of the script doesn't work for me; it works in 1511 but nothing above that, I always get an error saying that the file wasn't found.

 

Remove-AppxProvisionedPackage -PackageName $App.PackageName -Path "$ScriptDir\Mount" -ErrorAction Stop | Out-Null

 

It does the same if I run the command manually too

Posted
I can't believe they named the build 1703... come on, it's screaming out that they should have release Windows 10 Enterprise 1701! ;)

 

well yes but all 5 enterprises have gone boom iirc

Posted
The reasons I do it during deployment is because the below part of the script doesn't work for me; it works in 1511 but nothing above that, I always get an error saying that the file wasn't found.

 

Remove-AppxProvisionedPackage -PackageName $App.PackageName -Path "$ScriptDir\Mount" -ErrorAction Stop | Out-Null

 

It does the same if I run the command manually too

 

There's a few funny things I have to do when building these - obviously it has to be done from a Windows 10 machine, but the ISO etc must be hosted locally (due to network authentication not extending to the Powershell prompt). Always takes me a few tries but it does work for me, on the English International ISO of 1607.

  • Thanks 1
Posted
There's a few funny things I have to do when building these - obviously it has to be done from a Windows 10 machine, but the ISO etc must be hosted locally (due to network authentication not extending to the Powershell prompt). Always takes me a few tries but it does work for me, on the English International ISO of 1607.

 

How strange, I'm running it in Windows 10, the WIM file is on the C:\ and I've tried running Powershell as an Administrator and also running it as the local administrator and no matter what I try I always get the message "Remove-AppXProvisionedPackage : The system cannot find the file specified."

  • Thanks 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...