[Batch] Create a Windows 10 All.In-One (AIO) DVD5 ISO

The best answer for many questions

 

If I create an autounattend.xml file in the root directory of the media and insert this block

Code:

<UserData>
   <ProductKey>
      <WillShowUI>Never</WillShowUI>
   </ProductKey>
</UserData>

I avoid displaying the input window of the product keys during the first phase of installation and therefore, the window, which lists the editions included in the install.wim file, is displayed immediately. Right?

Thanks

Bye

 

You need to login to view this posts content.

 

Created an AIO ISO with Feb 2016 updated MSDN ISOs using this batch. AIO ISO's size was 5.92 GB.

My ISO containing 32 and 64 bit architecture WIMs of Core, Single Langauge, Pro, Education and Enterprise.

 

Haven't tested with February updated ISOs (don't have them in my language yet), but b10240/v1507/Threshold 1 and b10586/v1511/Threshold 2 (weee, so many designations!!) fit within 4.37GB/DVD5. February 2016 ISOs are just Threshold 2 with updates on top and that might make the final ISO slightly bigger than a "normal" release. We will see what happens with Restone 1 ISOs when they're released, but there's no guarantee that the combined ISO or even single ISOs will never go beyond 4.37GB/DVD5. Better yet, that's almost a certainty that they will eventually go bigger and bigger.

 

Yeah, it is common that ISOs will grow up. Just wanted to let you know that, Feb ISOs did not fit into DVD5 since this thread title says "[Batch] Create a Windows 10 All.In-One (AIO) DVD5 ISO"

 

You need to login to view this posts content.

 

I will update the script as soon as I get my hands on the ISOs, meanwhile you can use genenioo's suggestion

 

You need to login to view this posts content.

 

Figured it out. Too much messing with the wimlist.txt. If you just make changes to the wimlist and save it without getting prompted to replace the file it should be ok. If you wind up actually replacing the file (which I did before) that might spell trouble. If you’ve done upgrades you’d notice that at the same point where the error would come up a prompt with the x86 and x64 version of the version you’re upgrading to comes up instead of the error, so it looks like replacing the wimlist file was too much for the system to sort out to determine the proper upgrade. This time I just repositioned Pro for both x64 and x86, saved it without replacing the file, and everything worked fine.

 

I guess there won't be any trouble for upgrading Windows 10 10586 to 14393 for both 32 and 64 but architectures using that 4.25 GB ISO you made first?

 

You need to login to view this posts content.

 

Is there a way to include Enterprise and still fit on a DVD5?

Pretty much looking to do Home, Pro, Enterprise, and Education, all x64 versions.

Is that doable on one?

 

Don't know about the Anniversary Edition (don't have them yet), but 10586 could fit Education, Education N, Enterprise, Enterprise N, Multiple, Multiple N and single Language in a single ISO of 4GB.

 

Those sound lovely but I just want the Home, Pro, Enterprise, Education (all x64) without the extra ones that add minute differences to these existing 4.

Where do you find out about the other Windows 10 editions? This list neglects the ones you mentioned. http s://en.wikipedia.org/wiki/Windows_10_editions (had to space the link cause I'm a new user, sorry)

P.S. That Media Creation Tool only gives Windows 10, Windows 10 Home Single Language, and Windows 10 N. How am I suppose to get Pro and the other ones or am I on my own to find them?

 

N and KN editions are versions without Media Player/Center and DVD Player, due to limitations set by the European Union and South Korea.

You can find any ISO you need in the Windows 10 SVF Repository. Usually they use Windows 10 Multiple (Home/Pro) x64/x86 as source and the SVF are used to "extract" the other ISOs.

 

I didn't and didn't have a problem. I wasn't able to find a later download--have you?

 

If you look at mine it fit.

 

See my post #209. By the way the problem mentioned there is resolved--see post 210.

 

You need to login to view this posts content.