UEFI Multiboot (without needing MBR\Legacy booting)
You can add a second FAT32 partition containing WinPE boot files to the E2B USB drive. You should then be able to use the UEFI BIOS pop-up Boot Selection menu to boot from that FAT32 partition to WinPE.
You do not need to MBR-boot to the E2B menu - this means that you can use a UEFI-only system (UEFI32 and UEFI64) and select any UEFI-bootable .imgPTN file that you want to boot from.
- UEFI-boot to WinPE from the E2B FAT32 partition
- From WinPE you can then run SWITCH_E2B.exe and 'switch-in' a .imgPTN file.
- If the .imgPTN file has a .imgPTN23 file extension, then the 2nd partition containing the WinPE files will be kept.
Instead of using .imgPTN23, you can select a file with a .imgPTNX4 file extension (v1.B0+) to add a FAT32 Partition 4 containing the WinPE files.
- You can then reboot and use the BIOS Boot Selection menu to boot from one of the two FAT32 partitions (payload or WinPE)
OR - if the .imgPTN file contains rEFInd (MPI v0.039+) you can load the rEFInd UEFI menu system (but rEFInd is not signed and so breaks Secure Boot).
How to use UEFI-multiboot
- First select any .imgPTN23 or .imgPTNX4 file (either using the E2B menu or by running SWITCH_E2B.exe from a Windows system or if your E2B drive has a FAT32 partition with WinPE files on it, you can UEFI-boot to WinPE and select any .imgPTN file using SWITCH_E2B.exe.)
- This will allow you to UEFI-boot to the .imgPTN file and run it's payload...
rEFInd menu - UEFI-boot and choose the payload (white arrow) or Easy2Boot icon to boot to 64-bit WinPE.
- Or you can UEFI-boot to the USB drive and run the Easy2Boot WinPE OS.
64-bit WinPE to run SWITCH_E2B.exe.
- In WinPE, use SWITCH_E2B.exe to select a different rEFInd .imgPTNX4 or .imgPTN23 image.
- Reboot - goto step 2...
- To MBR\CSM boot - simply MBR-boot to the E2B CSM menu and restore the E2B partition - OR - run SWITCH_E2B.exe to restore the E2B partition.
If no CSM boot option is available, UEFI-boot and click on 'Restore E2B Partition(s)'.
UEFI-boot from an E2B drive
- Use the MPI Tool Kit v0.094 or later
- Use E2B v1.B0 or later
- Make or obtain a bootable WinPE 10 64-bit boot.wim file (or 32-bit boot.wim or both) - download links are in UEFI-multiboot eBook #3
- (optional) A Windows 8/10 system will be needed if you wish to make a .imgPTN file containing the boot.wim using the 'W' option (DISM is required).
Required WinPE UEFI 64-bit boot files are:
- \boot\boot.sdi - standard MS file
- \EFI\Microsoft\Boot\BCD - modified using BootIce to load \Source\Switch_x64.wim
- \EFI\Boot\Extra\Switch_x64.efi - standard x64 bootmgfw.efi file but renamed
- \Sources\Switch_x64.wim - your 64-bit WinPE wim file
(optional) As well as the WinPE files, you can add extra efi payloads by adding a folder below the \EFI folder, e.g. add a \EFI\Memtest86 folder containing MemTest86 files (this is already included in the download linked to in eBook #3).
There are three options for multi-UEFI booting...
- imgPTN23 - Place the WinPE files on a FAT32 Partition 2 (this may prevent MBR-booting to the E2B menu of some UEFI+CSM BIOS systems)
- X4 file extension - Uses a second image file which contains the WinPE files (can be used with all rEFInd .imgPTN files)
- Integrated - Adds WinPE x64 into each .imgPTN file (but adds 200-400MB+ to each .imgPTN file) - UEFI64-only
Option 1 - .imgPTN23
The WinPE boot files are placed on the second partition of the E2B drive. If the second partition is FAT32, you will immediately be able to UEFI-boot from the E2B drive.
- Create a second Primary FAT32 partition on the E2B drive (FAT32 is required if you want to UEFI-boot)
- Add the four WinPE UEFI files to the second partition in the correct folders (see above)
- You can also copy the \EFI\Boot\Extra\Switch_X64.efi to \EFI\Boot\BOOTX64.efi if you have a FAT32 PTN2.
IMPORTANT: Note that some systems may not offer a CSM\Legacy boot option because they will only present you with a UEFI-boot option when a FAT32 EFI-bootable folder+boot file is present. There is no way to avoid this except to rename the \EFI folder on the 2nd partition.
Option 2 - Use an 'X4' file extension
- Add the four WinPE files to the CUSTOM_PE folder under the MakePartImage folder (see above).
- Drag-and-Drop the CUSTOM_PE folder onto the MPI_FAT32 Desktop shortcut to make a 'WINPEx64' file (no file extension - can be any name).
Tip1: Increase the size of the file so that you can add applications and extra files into the image at a later date.
Tip2: If you use the MakePartImage shortcut instead of the MPI_FAT32 Desktop shortcut, you can specify the Volume Name and skip the configuration file changes.
- Copy the new WINPEx64 file to the \_ISO folder or the same folder as the .imgPTN file. If possible, the file should be placed in the \_ISO folder on the second partition of your E2B drive.
E2B and SWITCH_E2B will search for the 'X4' file in this order:
- Partition 2 \_ISO (*recommended)
- Partition 1 (same folder as .imgPTN file)
- Partition 1 \_ISO
- Now make all your payload .imgPTN files by Drag-and-Drop onto the MPI_FAT32 Desktop shortcut - (optional) answer R for rEFInd (do not include WinPE) within 30 seconds when prompted. If you need Secure Boot, do not add rEFInd.
Copy the files to your E2B drive (e.g. \_ISO\MAINMENU, etc.) and give them a file extension of .imgptnX4winpex64 so that \_ISO\WINPEx64 will be loaded as partition #4 when the image is switched in. Make both files contiguous using \MAKE_THIS_DRIVE_CONTIGUOUS.cmd and double-click on the file in SWITCH_E2B.exe to switch them in. Example:
Before switching - two files:
E2B ptn: \_ISO\LINUX\Ubuntu64.imgPTNX4winpex64
Ptn2 (or E2B ptn): \_ISO\winpex64
Ptn1: (Ubuntu files or whatever)
Ptn4 (WinPE files)
- If you use a file name of Ubuntu64.imgPTN23X4winpex64 then partition 2 will not be removed after switching.
- If a \_ISO\LINUX\Ubuntu64 (with no file extension) partition image file also exists, the image will be switched into Partition 3.
2. After switching in the .imgPTN and the winpex64 file, I recommend you delete the \menu.lst file from inside the winpex64 image file to avoid accidentally loading the wrong menu when it CSM\Legacy boots.. The other folders (\e2b,\CLOVER and all files in the root can all be deleted). You can also change the Volume label to WINPEx64 if you wish. The second partition (actually Ptn4 after switching it in) can look like this after tidying it up:
Option 3 - Integrated WinPE 64-bit (most compatible)
- Add the four WinPE files to the CUSTOM_PE folder under the MakePartImage folder.
- Make your .imgPTN files by Drag-and-Drop onto the MPI_FAT32 Desktop shortcut - answer W (to include WinPE files) if prompted.
- If prompted about Secure Boot signed files, answer Y to install rEFInd.
Secure Boot from rEFInd
Out-of-order/overlapping UEFI partitions
Copy the secondary file (not the .imgptn* file) to a \_ISO folder on second partition on the E2B drive.
Example 1 (two files)
E2B Ptn 1 - \_ISO\LINUX\Ubuntu64.imgptnX4Winpe
E2B Ptn 2 - \_ISO\Winpe
Example 2 (three files)
E2B Ptn 1 - \_ISO\LINUX\Ubuntu64.imgptnX4Winpe and \_ISO\LINUX\Ubuntu64 (must be in order)
E2B Ptn 2 - \_ISO\Winpe
Windows 7 64-bit Install ISOs
The official Microsoft Win 7 64-bit ISO does not include the bootx64.efi UEFI boot file so you must add one into the imgptn file after you have made it using MakePartImage. MakePartImage 0.094 or later will try to add it in if it can find the file on your system disk.
You can load the .imgPTN file using ImDisk to add in the bootx64.efi file, or you can switch it in using SWITCH_E2B.exe and then add in the file using Windows Explorer. Find a Win8\10 bootx64.efi (either using a bootx64.efi or bootmgfw.efi file from a Windows x64 8\10 \Windows\Boot\EFI folder or from the \EFI\BOOT folder of a Windows x64 8\10 Install ISO). If the rEFInd file \EFI\Boot\bootx64.efi is already present, you must copy the file to the \EFI\BOOT\ORIGINAL folder (it can be named Windows7.EFI if you like, so it will appear in the rEFInd menu as Windows7.efi).
Tip: The \EFI\Boot\Extra\Switch_x64.efi file is a copy of bootmgfw.efi.
UEFI BIOS 'bugs'
1. If the start addresses of the four partition table entries in the MBR of the USB drive are not in ascending order, some UEFI BIOSes will not allow you to UEFI-boot even though one of the partitions contains a FAT32 partition with valid EFI boot files. e.g. many Asus BIOSes.
2. If the USB drive contains a FAT32 MBR partition with valid EFI boot files (or an \EFI\Boot folder?) then the BIOS may not allow you to MBR\CSM\Legacy boot from that drive. e.g. Fujitsu LifeBook AH532, some Samsung and Acer systems.
3. If the MBR partitions overlap, the UEFI BIOS will ignore all partitions on that disk and won't UEFI-boot from any of them.
Recommended for Easy2Boot (fastest!) - SanDisk Extreme SDCZ880-128G-G46