Windows 10: Clean Install Windows 10 Anniversary

Hiya....Has the Media Creation tool been updated to this version so I can do a clean install...there is no way of telling? TIA

:)

 

Is possible to do Clean Install the Anniversary update of Windows 10

Hey Jaya, Yes you can. The installation media has been updated to windows 10 to the anniversary update. Once you download the in media install media creation tool you can convert your flash drive to bootable media or create .ISO
File. Once you created either both you can easily clean install Windows 10 anniversary update. If you experience any issue a page exists on the web which has elaborated How
to Clean Install Windows 10 Anniversary Update

 

Anniversity upgrade

Yes you will be able to perform a clean install. ISO's will be available on August 2nd.

Are there any instructions about how to install the Windows 10 Anniversary Update?

• How
  to Upgrade to Windows 10 Anniversary Update version 1607 using Windows Update
  
• How
  to Upgrade to Windows 10 Anniversary Update version 1607 using ISO File
  

also

How to Perform a Clean Install of Windows 10 with the ... - groovyPost

 

MCT ISO is version 1607 build 14393.

You can always check any Windows ISO by yourself: double click the ISO to mount it as virtual DVD, check the drive letter it got and give the following command replacing drive letter X with your actual one:

Code: dism /Get-WimInfo /WimFile:X:\sources\install.esd /index:1[/quote]
Notice that above command applies only to MCT ISO images as they use install.esd instead of install.wim file. For all other ISO images with install.wim simply replace the ESD extension with WIM:

Code: dism /Get-WimInfo /WimFile:X:\sources\install.wim/index:1[/quote]

 

Notice that above command applies only to MCT ISO images as they use install.esd instead of install.wim file. For all other ISO images with install.wim simply replace the ESD extension with WIM:

Code: dism /Get-WimInfo /WimFile:X:\sources\install.wim/index:1[/quote]




[/quote] Thank you so you are saying the MCT is up to date with Windows 10 Anniversary *Biggrin

 

Yes. Anyway, I always check my ISO images as told in my previous post before using them, just to be sure. An old school geek, hard to forget old habits: five most important things in computing are backup, backup, backup, backup and check that you are using correct install media.

 

Kari I used this to check the iso I downloaded using option #1 in this tutorial https://www.tenforums.com/tutorials/9...-download.html It states the download is both Home and Pro versions https://www.microsoft.com/en-us/soft.../windows10ISO/

When I used the dism /Get-WimInfo /WimFile:X:\sources\install.wim /index:1 (needed a space between the wim and / ) I get the same thing you show with the Pro version, I've used this USB iso to successfully install the AU in two laptops that are the x64 Pro version. It fails when I try in the x64 Home version, I'm wondering if the iso is not really both Home and Pro. It is over 4G so being larger than the Home version I though that was why, now I'm not so sure.

A screenshot of my iso is below, only shows Pro version, is that correct, or is the Home version hidden due to maybe only showing the highest level version on the iso, or is Pro the only one on it?

 

If you want to see what versions are in the WIM file, you need to leave the /index:1 off the end of the command.

Or change it to /index:2


Index:1 should be Pro.
Index:2 should be Home
Leave the /Index parameter off the end of the command and it will list all the indexes in the file.

 

Thank you NavyLCDR, I did that and here's what I got:

Details for image : g:\sources\install.wim
Index : 1
Name : Windows 10 Pro
Description : Windows 10 Pro
Size : 14,747,431,455 bytes
Index : 2
Name : Windows 10 Home
Description : Windows 10 Home
Size : 14,586,404,734 bytes
The operation completed successfully.

 

Thanks for clarifying this.

My apologies for giving partly false information.

 

You gave entirely the correct answer for the first question asked You have to include the /index:x parameter in order to determine the build number.