Reparing Windows by booting from an ISO:
Windows setup will not offer the Repair option if you select an XML file.
If you want to REPAIR an existing Windows 8/10 system, when you select a Windows 8/10 ISO, press any key quickly within 4 seconds, when prompted.
Once it boots to Windows Setup, you can choose the 'Repair' option (but you cannot install Windows).
If you want to install Windows 8/10/2016, simply wait 4 seconds and then you can choose an XML file or Product Key and install WIndows (E2B v1.86+).
Windows 8/10 Product Key requirements
When installing Windows 8/10 from an Install DVD, it will usually request a Product Key from the user. You can remove the requirement for a product key during Installation from a CD\DVD by editing the contents. See here for details.
Windows Setup will obtain information about which Edition or version of Windows to install from the \Sources\EI.cfg file (if present). However, when using E2B to install from an .ISO file, Setup will use the \AutoUnattend.xml file that is created by E2B and Setup will ignore the EI.cfg file. Most Windows Install ISOs contain an Install.wim/Install.esd file which contains more than one image. Setup needs to know which image to install and so Win8/10 usually needs the Product Key to be specified in the XML file.
To install the correct SKU of Windows using an XML file:
For an automated install, ensure you specify the correct Image Number (usually 1=Pro and 2=Home for standard Microsoft ISOs - but not always!)
Ensure the Product Key matches the version you want to install - you can use a generic installation key but it must be for the correct Edition (Home/Pro/Ultimate/Enterprise, etc.)
If using E2B with a Windows Install .ISO and Autounattend.xml file (E2B on a Removable USB flash drive), the Product Key must be specified in the AutoUnattend.xml file. E2B will thus ask you to choose a product key and will then write the key into the AutoUnattend.xml file. You can use a 'generic' install key (it cannot be activated) and then change the key later.
Many Windows 8\10 ISOs will not install unless a Product Key is specified in the AutoUnattend.xml file first. For this reason, E2B will ask you to choose the correct Product Key for the version of Windows that you want to install. This is the main difference between installing Vista/Win7 and Win8/SVR2012/10 ISOs.
You may find it easier to convert the ISO file to a .imgPTN file. This will allow you to both MBR and UEFI-boot and you will not need a 'Helper' Flash drive or an XML file. You can add .imgPTN files to the \_ISO|WINDOWS\xxxx folders (except for the XP folder) or any of the standard E2B folders.
If you are booting Easy2Boot from a USB Hard disk and using a Windows Install Vista+ ISO file, you will also need a Removable-type of ' Helper' USB flash drive containing these 3 files -
AutoUnattend.xml (overwritten - required for Win Vista and later OS Install ISOs),
Unattend.xml (overwritten - required for WinPE ISOs and some Windows Install scenarios)
WINHELPER.USB (marker file to find correct USB drive)
These 3 files must be on the root of your USB 'Helper' Flash drive.
Additional Files (.key, .txt, .xml)
Add a .txt file to change the text in the menu
For Win8/10 and SVR2012 ISOs you can also add a 10.txt file of the same filename and add an alternate title (rather than have the filename listed in the menu).
If you also add a .txt file of the same filename containing a single line of text such as:
then that text will be used as the menu title instead of the name of the file itself(note that the line must start with the lower-case word'title'). See here for more details.
Note: .iso files of 0 length are not listed (but may add to the total file count displayed in the menu!).
Add a .key file to hold Product Keys
For Win8/10/SVR2012, the product key can be typed in manually by the user, after selecting an ISO in the Easy2Booty menu. To use your own pre-defined set of Product Keys, make lots of .key files (copy the format from the other files) - OR if you have lots more product keys you can add all the keys to the CHOOSE FROM A LIST.key file. You can delete any .key files you don't want. Another alternative is to make a .xml file with your Product Key already in it and not use .key files at all.
1a - Example Win8 Preview Pro.key file
1b - Example CHOOSE FROM A LIST.key file
CHOOSE FROM A LIST.key
echo WINDOWS 8 PRODUCT KEYS
echo -e ======================
echo Build 6.2.9200
echo 1=XKY4K-2NRWR-8F6P2-448RF-CRYQH Pro
echo 2=FB4WR-32NVD-4RW79-XQFWH-CYQG3 Core
set /p ask=Choose a key :
if "%ask%"=="1" set KEY=XKY4K-2NRWR-8F6P2-448RF-CRYQH
if "%ask%"=="2" set KEY=FB4WR-32NVD-4RW79-XQFWH-CYQG3
Add an .xml file to automate an install
You can also have your own unattend.xmlfiles in the same folder. This can contain all your settings and a product key - you can just choose any xml file and run the ISO. If you delete all .xml files from the WIN/8/SVR2012 folders, then the default unattend.xml will be automatically used and the user will not be prompted to select an xml file.
1c - Windows 8/10/Server 2012 Product Keys
After you have selected a Win8/SVR2012 ISO, E2B will prompt you to select any unattend.xml file that is present in the \_ISO\Windows\Win8 folder from a list or CHOOSE A PRODUCT KEY or from any *.xml file or NO KEY.
Note that 'Single Language' versions usually contain a single image of Windows Home\Core only.
You can define your own Unattend.xml files which should contain the correct product key and can contain your own settings too. These must contain a special entry for LOADISO.CMD (see below). Any extra .xml files will also be automatically listed. If you delete all .xml files from the Vista/7/8/SVR2012 folders, then the default unattend.xml will be automatically used and the user will not be prompted to select an xml file.
CHOOSE A PRODUCT KEY - Alternatively, you can use the Easy2Boot default Unattend.xml file and then pick a key from a list of user predefined product keys using the Select a Product Key file menu. Product keys can either be contained in separate .key files and/or in one single 'CHOOSE FROM A LIST.key' file (see above for an example of the contents). You can tailor the CHOOSE FROM A LIST.key file to show only the product key entries that you want to allow (you can edit it using NotePad - see above for details).
The pre-defined .key files can be deleted or altered or added to. These can be selected by using the E2B menu (items 2-6 in the example above).
If you select the ...
CHOOSE FROM A LIST.key menu option (1) then you will be presented with a pre-defined list of different keys:
You must choose the correct key - if you use a key for a different version, Widows may report a 'license' error or other error.
How to remove the 'Repair' prompt
If you don't want the blue console window to prompt you to repair Windows (see screenshot above), then create an .XML file for your ISO by copying one of the XML files already present. Make sure the Product Key is correct and make sure that all references to LOADISO.CMD are changed to LOADISONP.CMD (NP=No Prompt).
Add your own .xml file to automate an install
You can also have your own unattend.xml files in the same folder as your ISO file (any name but must end in .xml). This can contain all your settings and a product key - you can just choose any xml file before you run the ISO. If you delete all .xml files from the Vista/7/8/SVR2012 folders, then the default unattend.xml will be automatically used and the user will not be prompted to select an xml file.
For an example look at the \_ISO\e2b\firadisk\auWin8.xml file (for Win8\10). These contain a special RunSynchronous section which runs LOADISO.cmd - this is responsible for loading the ISO so that Windows Setup can access it as a DVD.
E2B will copy the contents of your XML file to \AUTOUNATTEND.XML before it boots from the ISO. You XML file must be modified so that it runs LOADISO.cmd which will run ImDisk and install the ISO as a virtual DVD drive.
An alternative is to use SDI_CHOCO to install drivers and applications automatically.
You may find the Unattend.XML generator here useful - but you must add the RunSynchronous code required by E2B afterwards.