Select edition from install.esd

[CyberC4p0]

On the wimboot section of the iPXE website

It mentions that multi-image wim files will work by specifying the index of the version we want to boot. I mounted the Windows 10 ISO but instead of finding the install.wim file, I found the install.esd. Will this work regardless? If not, how can I go on obtaining the install.wim file?

Thank you for the help provided :D

[NiKiZe]

You need boot,wim which contains the winpe system.
Once you have that system running it will need install.esd/wim to install to disk. - You should not boot install.x

[NiKiZe]

You need boot,wim which contains the winpe system.
Once you have that system running it will need install.esd/wim to install to disk. - You should not boot install.x

Thank you for this. This solved my issue. I will specify Index 1 for windows 10 home while still booting the boot.wim file. Then when it gets the install.esd, it will get the image located on index 1. Now I understand! Thank you 😄

No that is totally wrong. the index of boot.wim has nothing to do with any indexes in install.wim/esd

[CyberC4p0]

You need boot,wim which contains the winpe system.

Once you have that system running it will need install.esd/wim to install to disk. - You should not boot install.x

Thank you for this. This solved my issue. I will specify Index 1 for windows 10 home while still booting the boot.wim file. Then when it gets the install.esd, it will get the image located on index 1. Now I understand! Thank you 😄

No that is totally wrong. the index of boot.wim has nothing to do with any indexes in install.wim/esd

So then why specify an index? I want to be able to load different indexes of the install.esd when installing to a disk.

Something that will let me choose like the menu above.

[NiKiZe]

You might want to read about autounattend.xml

[oschroeder8]

An ESD file is not technically a WIM file, though they serve a similar purpose.

On the ISO you will find a boot.wim file. That WIM file contains the Windows Setup program which, when started, would allow you to deploy the images contained in the ESD file. But when using WIMBOOT, that ESD file will not be accessible because you didn't load the whole ISO, just the WIM file. That's why @NiKiZe is referring to a mounted path where the ESD file would be accessible (the remaining content of the ISO).

If the ESD file was like a WIM file and you then picked an image index, you would boot directly into a Windows installation, not the process of deploying the image itself.

Hope that clarifies things.

[CyberC4p0]

An ESD file is not technically a WIM file, though they serve a similar purpose.

On the ISO you will find a boot.wim file. That WIM file contains the Windows Setup program which, when started, would allow you to deploy the images contained in the ESD file. But when using WIMBOOT, that ESD file will not be accessible because you didn't load the whole ISO, just the WIM file. That's why @NiKiZe is referring to a mounted path where the ESD file would be accessible (the remaining content of the ISO).

If the ESD file was like a WIM file and you then picked an image index, you would boot directly into a Windows installation, not the process of deploying the image itself.

Hope that clarifies things.

Ohh ok! Thanks for the clarification 🤗

[CyberC4p0]

To answer my own question...

I had to add a ei.cfg to bring up the Select Edition menu during installation.

Credit: https://www.intowindows.com/how-to-select-pro-edition-while-installing-windows-10/