.VHD and .WIM files
Recent E2B versions can directly MBR-boot from certain types of .WIM, .VHD and .VHDX files.
- Use 'Fixed-size' VHDs only - dynamic VHD\VHDX files (as made by SysInternals Disk2vhd.exe) and BitLocker VHDs are not supported (use a .imgPTN file instead).
- XP-based .WIM files are not supported.
- MBR-booting only (see below for UEFI).
- VHDs should have a single partition.
- Copy them to a menu folder, e.g. \_ISO\WIN or \_ISO\WINPE (not \ISO\WINDOWS\xxxx folders).
- .WIM, .VHD or .VHDX files do not need to be contiguous
- NT6-based WinPE/Vista/7/8/10 etc. (non-XP) fixed-type .WIM, .VHD and .VHDX files are supported.
- For XP-based .VHD files (with Firadisk driver), change the extension to .VHDBOOT (also try .VHDFIRA).
- For 32-bit XP or Win7, try .VHDFIRA or .VHDBOOT file extension (depends on how VHD was made).
- If you have reliability problems with Windows 7 VHDs then convert them to a NTFS .imgPTN file and ensure that the .VHD, \bootmgr and \boot\BCD files are present inside the .imgPTN file. Use BootIce to configure the BCD if required.
- VHD's which first load grub4dos (look for \grldr file) - use .VHDGRLDR.
- Can be on the 2nd partition if you create a .mnu file.
- E2B v1.B5 and later allows for spaces in filenames and file extension suffixes (e.g. WinPE 10 (64-bit).wim64ncq).
Tip: Make a .txt file using \_ISO\TXT_Maker.exe for your .VHD or .WIM file - you can tick 'Only display if 64-bit' if it is a 64-bit OS so that it will not be listed in the E2B menu on 32-bit systems.
PTN1 - FAT32 containing the EFI folder and other Windows boot files, etc.
PTN3 - NTFS containing large VHD or WIM file.
Note that for BitLocker encrypted VHDs, you must specify the exact drive and partition that the VHD file is located on (you can use the 'LOCATE') option. Also, if using BootIce, you must use v1.3.4 or later and click on the >>> button to ensure that the MBR: BitLocker option is set.