E2B works best with large Removable USB Flash drives.
Most USB Flash drives (aka 'pen drives' or 'thumb drives') are of the Removable type, but some USB Flash drives are of the Fixed Disk type. You can check this using RMPrepUSB. Windows 10 Explorer will display 'USB Drive' for the Removable type and 'Local Disk' for the Fixed Disk type.
E2B is intended to be used with a large USB drive - so use at least a 16GB USB drive. To make a non-contiguous 6GB file contiguous, you will need at least 6GB of free space on your USB drive. If you have a small USB drive, try using Rufus instead of E2B which is not multiboot! E2B will work on smaller drives if you use small ISOs/payloads of less than 3GB in size.
The maximum partition/USB drive size for E2B is 2TB (GPT USB drives are not supported by E2B).
Recommended USB drives
Tip: Always buy USB 3.0/3.1 drives if possible - they are faster and are fully backwards compatible with USB 2.0, so there is no reason to buy USB 2.0 drives!
Removable USB Flash drive - I highly recommend theSanDisk Extreme range 64GB/128GB USB 3.1 - it is the best and fastest USB drive for E2B that I have found (note: avoid older versions which may be of the Fixed-disk type. Also, avoid 'fast' USB drives such as the Lexar P20 Flash drive or Kingston HyperX because they are very slow with small files and WindowsToGo!). See here for an interesting comparison between the SanDisk Extreme Pro, Pro 3.1 and Sandisk Extreme. I do not recommend flash drives over 128GiB - there can be BIOS compatibility issues with USB drives >137GB.
External USB HDD (max 2TB), for best compatibility, I recommend a non-UASP USB 3.0 SATA drive enclosure (such as the IT-CEO USB 3.0 IT-700 - see blog post on enclosures here). I also highly recommend the IODD 2531 HDD enclosure- see blog post here, this drive can emulate USB CD/DVD drives and can also be used to boot E2B without needing a 'Helper' USB flash drive and you can write-protect the HDD whilst in use.
Beware of some native 4K-sector external USB Hard Disk drives - they do not MBR-boot!
Note that some BIOSes cannot access files on USB drives which are past the 137GB point. Keep the first E2B partition below 137GB. You can create a 2nd partition for file/data storage when using Windows or linux (the small 2nd hidden E2B partition - PTN2 - should be deleted first).
If possible, use Windows to make the E2B USB drive because it will be more compatible on a wider range of systems (2 partitions should be created for best compatibilty).
Write-Protected USB - When booting from an E2B drive, the drive must not be write-protected. However, when connecting it to a Windows\Linux system to run software from the drive, it is useful to write-protect the USB drive to prevent infection from the user's OS. WP USB3 drives are available from Kanguru or Netac.
Note for Windows 10 Redmond Update (1607+) - this version of Windows may prompt you to format the small 2nd partition on the E2B USB drive. You can simply cancel this Format pop-up box, or if it annoys you, simply format the partition so Windows does not complain again. The 2nd partition is very small (11.5K) and is not used by E2B at all - it just needs to be there!
If you are getting 'Cannot write to MBR' errors or Write-protect errors, run diskmgmt.msc, right-click on the USB drive volume coloured bar and choose Delete Volume. Then try unplugging the USB drive and re-connecting it. This is needed when Windows locks a 'WindowsToGo' USB drive.
To make an E2B drive, use the large red button...
Other buttons are:
Make_E2B_USB_Drive.cmd - you can choose a different drive, use a partition size larger than 137GB, choose FAT32 or NTFS and choose various language/keyboard combinations and menu 'stamps' - see below.
Extract E2B - extract all the files in the download to a new folder on your Desktop (USB drive must be detected - bug fixed in Make_E2B.exe v0.0.14 and later versions)
Update E2B Drive - updates any connected E2B drive to this version of E2B
Test with QEMU - use this to check that your USB drive boots to the E2B menu correctly - you may even be able to boot to some 32-bit ISOs too!
Note: To support direct booting of Windows .VHD, .VHDX and .WIM files using E2B, bootmgr must be copied to \_ISO\e2b\grub\DPMS\NTBOOT.MOD\bootmgr on the E2B USB drive. The Make_E2B utility will usually download or find and copy the correct version for you.
E2B will warn you if the bootmgr file is not compatible. Only certain Windows 8/8.1 versions of bootmgr will work. Windows 10 versions of bootmgr will give a BSOD but most Windows 8/8.1 boot managers should be compatible. Bootmgr versions that work have sizes of 389720, 389720, 398144, 398156, 398356, 427680, 404250, 409154, 403390 or 400517 bytes. You can obtain the correct version from an official Microsoft Windows 8.1 Install ISO.
Tip: Download and run Add_bootmgr_to_E2B to automatically add the correct version of bootmgr to all your old E2B drives (internet connection required).
Applications that may interfere with Make_E2B.exe
The following applications are known to cause issues when making E2B USB drives, you may need to uninstall/disable them:
For more experienced users, you can also extract the E2B files from the self-extracting (rar) executable.
1. Extract the E2B download to a new folder using the Extract E2B button in the Make_E2B.exe GUI.
You can add payload files to the new folder now if you wish, or directly copy your payload files to the E2B USB drive later, after you have made it.
Now insert your USB drive.
I recommend you temporarily turn off anti-virus protection for the next step...
2. Run the MAKE_E2B_USB_DRIVE (run as admin).cmd script (NTFS is recommended choice when prompted) - the USB drive must have a drive letter assigned by Windows (C: to Z:). If using a large USB HDD, I recommend a maximum of 128Gib for the E2B partition - you can create a 2nd Primary partition late for any other files.
3. Copy any more payload files (ISOs, etc.) into the correct sub-folders under \_ISO (e.g. \_ISO\MAINMENU) of the USB drive.
4. Run \MAKE_THIS_DRIVE_CONTIGUOUS.cmd from the USB drive. This step is only required if the payload files are fragmented, but you might as well do it now.
Expert Instructions (more details)
WARNING: If using a large USB drive (>128GB), use this method instead and make sure that E2B is in the first partition and it is below 137GB in size.
This is because many BIOSes (even modern ones!) have problems accessing USB sectors beyond 137GB (internal system hard drives >137GB may be OK, but USB drives >137GB may not work because the BIOS USB driver code in many BIOSes has still not been updated!).
1. Download Easy2Boot (either the basic download, or the DPMS version of E2B with XP 32-bit Mass Storage drivers if you want to install XP to SATA systems).
2. Insert the USB drive which is to be wiped, into your Windows computer's USB port.
3. Run the download .exe file which runs the Make_E2B.exe GUI, and click the 'Make_E2B_USB_Drive.cmd' button.
4. Turn off AV.
Note: Some AntiVirus programs such as Trend Micro may interfere with the copy process. Either disable the AV program, whitelist the autorun.inf file or delete the autorun.inf file from the download first (autorun.inf just displays an E2B icon when the E2B USB drive is displayed in Windows Explorer - it does NOT run any program). Note that a 'PUP' or 'PUA' warning is NOT the same as a virus!
Defraggler may also interfere with the script (see below for a list of known 'problem' software).
5. Enter the USB drive number (e.g. 4) and then choose F=FAT32, or choose N=NTFSif you want to add files larger than 4GB to the E2B drive.
NTFS is recommended for UEFI-booting using .imgPTN files.
Note: You can UEFI-boot from an NTFS E2B USB drive by creating .imgPTN files.
If you want to support UEFI booting, instead of copying over ISO files, you will need to create FAT32 .imgPTN partition image files. You can UEFI-boot from .imgPTN files, even if the E2B USB drive partition is formatted as NTFS, so there is very little disadvantage in using NTFS and many advantages.
If you have a small USB Flash drive (1-16GB) and all your files are less than 4GB in size, I suggest you use FAT32 which is easier to defrag (especially under linux). Also, E2B will enumerate files on a FAT32 E2B drive twice as fast as a NTFS formatted drive, so the Main menu will load twice as from a FAT32 volume.
Even if you are booting a linux distro ISO file that does not support NTFS, it should still boot from an E2B NTFS drive!
6. Make_E2B_USB_Drive.cmd will ask you to specify a language, keyboard and other options and will create a \_ISO\MyE2B.cfg file for you.
If you don't want to use a MyE2B.cfg file, type S to skip that section for default USA settings.
Add an E2B animated icon, QR code (E2B site URL) and/or E2B Boiler Plate
Tip: If you add the QR Code stamp to the E2B menu, you can use your mobile phone to go straight to the 'list of tested ISOs' page on the E2B website!
7. Finished! - The E2B drive is now ready for use. You can test the E2B menu by running \QEMU_MENU_TEST (run as admin).cmd from the USB drive.
To boot on a real system from a USB drive, you will typically need to press a Function key (e.g. F8 or F12) to get a BIOS Selection Menu pop-up - see here for more details.
If it fails to format the USB drive as NTFS, run it again and select FAT32 - then re-run the script again to format it as NTFS.
You can run \_ISO\docs\Make_E2B_USB_Drive\Make_MyE2B.cfg.cmd if you just want to change the MyE2B.cfg file settings (e.g. keyboard type or language) or change the QR and Boiler Plate options.
E2B will work from an exFAT USB drive, however SWITCH_E2B.exe will not work - see this page if you want to make an exFAT USB E2B drive.
Note: To boot Windows .VHD and .WIM files using E2B, the file bootmgr must be copied to the E2B USB drive folder \_ISO\e2b\grub\DPMS\NTBOOT.MOD\bootmgr. Only certain Windows 8/8.1 versions of bootmgr will work, do not use the Windows 10 version of bootmgr as it will give a BSOD. Most Windows 8/8.1 boot managers should be compatible. Bootmgr versions that work are sizes 389720, 389720, 398144, 398156, 398356, 427680, 404250, 409154, 403390 or 400517 bytes. E2B will warn you if the version is not compatible.
Download the latest version (you can update E2B+DPMS USB drives using the non-DPMS version) and click on the Update E2B Drive button.
Or - extract E2B to an empty folder and then run .\UPDATE_E2B_DRIVE.CMD.
If you wish, you can add all the ISOs and .mnu and .txt files, etc. into the extracted folder too, so that when you run UPDATE_E2B_DRIVE.CMD, any new or updated files will be copied across to your E2B USB drive (but no files will be deleted from the USB drive).
If you run the MAKE_E2B_USB_DRIVE (run as admin).cmd file from an E2B USB drive, then a new E2B USB drive will be made and all your payload files, etc. will be copied across to the new USB drive as well.
If you have more than one E2B USB drive and you want to update them all, just connect as many E2B USB drives as possible to the Windows computer (e.g. use a multi-port USB hub) and double-click on \_ISO\docs\make_E2B_USB_Drive\Update_all_E2B_drives.cmd.
More things to do...
Looking for things to do with your new E2B USB drive? Look here.
If you are very short of space, you can delete the500MB\_ISO\CONTIG.ISO file (but you will have to remember to defrag all your ISOs).
Problems using MAKE_E2B_USB_DRIVE.cmd?
Some AntiVirus products may block the \AutoRun.inf file from being copied to the USB drive (or may warn of a possible virus) - this file is not essential. You can either disable your AV or just not have a nice E2B icon displayed in Explorer. There is no virus and the E2B autorun.inf file does not run any program.
Some products which may interfere with process of making or using an E2B USB drive are: