www.easy2boot.xyz is the new official website for Easy2Boot

Copy all ISO files to your USB drive and then Legacy or UEFI boot!

IODD Mini SSD can load any ISO\VHD as a virtual drive and then boot from the new virtual DVD or HDD. Store 100's of different ISOs and VHD files on just one small device!

E2B - the USB multiboot solution for professionals

Boot to (almost) anything from just one USB drive for free!
E2B includes the E2B grub4dos, agFM/grubfm and Ventoy menu systems for the best chance of booting any payload!
E2B and agFM use a generic method of booting Linux ISOs. This means it is often more successful than Ventoy.
Over 1 million downloads - E2B is used by techs, repair shops, schools and Universities all over the world.

Latest versions:

  • E2B v2.09 (Beta v2.10g with grub4efi, Windows 11 support, latest PassPass to bypass latest Windows 10/11 local password account)
  • agFM v1.73 (Beta v1.74a)
  • Ventoy for Easy2Boot v1.0.51

Latest Beta downloads here.

YouTube videos here.

  • Easy2Boot supports up to 3 different menu systems.
    1. Easy2Boot - original E2B Legacy\MBR booting based on grub4dos.
    2. agFM (a1ive grub2 File Manager) (optional) - for Legacy\MBR and UEFI32\UEFI64 booting based on open source a1ive's version of grub2 and grubfm.
    3. Ventoy for Easy2Boot (optional) - for Legacy\MBR and UEFI32\64 booting based on open source grub2-based version of Ventoy.
  • Secure UEFI64 booting is supported (unless blocked by UEFI DBx blacklist in BIOS) - Once booted to the agFM menu, secure boot is temporarily disabled so all ISOs can be booted,
  • MemTest86 and FreeDOS are already included.
  • Boot .ISO, .WIM, .EFI, .IMA, .IMG, .VHD, .VHDx, .HFS + others (files can be over 4GB as NTFS is used).
  • Generic method of booting Linux ISOs (no need to update E2B every few months because a new Linux distro no longer works!).
    E2B and agFM use the 'Easy2Boot/partnew' technique which is successful in booting over 99% of all Linux ISOs. Unlike other solutions such as YUMI, Ventoy, Multiboot, etc. which may break when a new distro is released.
  • Legacy boot to DOS, Win98, XP with SATA\RAID Mass Storage drivers automatically added, Linux, Windows Vista-10, ISOs, Windows VHDs, WIM files, etc..
  • Add multiple HFS (Mac OSX) partition images using .imgptnREP3 file extension for UEFI-booting.
  • Add partition Image files (.imgPTN files) - switch in any partition image and then boot to it. You can even make a partition image from other bootable USB drives.
  • Always have the latest version of Ventoy by downloading the latest release as an official Ventoy image.
  • You can add your own files and folders to the USB drive.
  • Implement fully automated Windows installs with automatic driver and app installation, etc. (SDI_CHOCO).
  • eBooks (PDFs) written by the developer are available with step-by-step exercises, explanations, details, and advanced topics.
  • E2B, agFM and 'Ventoy for Easy2Boot' can be updated without losing your own files or configuration settings.
  • Free online help (GMT+0 time zone).

Note: E2B requires a writeable USB disk and some payload files may need to be made contiguous for best results.

Up to three different menu systems

  1. Easy2Boot Legacy - developed over many years to be reliable and compatible. Boots most payloads including DOS, Win98, XP Install ISOs, Win7-10, Linux, Windows VHDs and WIM files, .ima floppy images files, etc,
  2. agFM Legacy & UEFI - directly Legacy\UEFI-boot (with Secure UEFI64-boot bypass) - variety of boot methods (for Linux ISOs the 'E2B/partnew' method is the most compatible and successful)
  3. Ventoy for Easy2Boot Legacy & UEFI - may be more successful with some types of payload (e.g. some WinPE ISOs or FreeBSD) but sometimes not as successful on other payloads. When it works it is usually faster and slicker!

These three menu systems should give you the maximum chance of successfully booting from any of the payload files that you copy onto your E2B USB drive.

Easy2Boot Legacy menu system (grub4dos-based)
Ventoy for Easy2Boot Legacy+UEFI menu system (grub2-based, fork of Ventoy)
agFM Legacy+UEFI menu system (grub2-based)

You can configure each menu system separately (colours, style, font, theme, language, keyboard, etc).

How to make an E2B USB drive

Please note: For best results use a Windows 10 system if using a USB Flash drive.

1. Download E2B

E2B can be downloaded as a self-extracting .exe (or download the .zip file if you have a Windows XP system). You may need to ignore the Windows Defender SmartScreen warning about running a downloaded .exe file and choose 'Run anyway'.
A new folder will be created on your Windows Desktop which contains the E2B install files.

Tip: If you have a Windows XP system, download the .zip version because the .exe self-extracting version does not run under XP. Extract the files to a new folder on your Desktop.

2. Make a USB drive (Win10 recommended)

Run Make_E2B.exe to make your E2B USB drive. You can use a USB Flash drive or a USB hard disk.
Note that all partitions and contents on the USB drive will be erased.
1. Select E2B Menu options.
2. Select USB drive (if drive letter is visible).
3. Click on the Big Red Arrow button (or click on the Gear Wheel button if you want special options/partitions or if no drive letter is visible).

Make_E2B.exe Windows utility - use the 'Gear Wheel' button if you have a large USB drive and want 3 partitions.

Type 'Y'es to install agFM if you want direct UEFI-booting.
Type 'Y'es to install 'Ventoy for Easy2Boot' if you also want to add the alternative Ventoy for Easy2Boot menu system.

Note: To add the UEFI agFM files to the second partition for UEFI-booting, you will need a Windows 10 system if your USB drive is a 'Removable' flash drive. If your USB drive is a Hard Disk or the 'Fixed Disk' type of flash drive, then you can use XP/Win7/Win8 or Win10 to prepare the E2B USB drive. This is because only (recent) Windows 10 systems can access multiple partitions on USB Flash drives.

3. Add payload files (ISO, WIM, EFI, VHD, etc.)

3.1 Simply copy over your bootable files to one of the pre-defined menu folders on the first partition.

  • \_ISO\DOS
  • \_ISO\WIN (e.g. WindowsToGo VHD/VHDx files)
  • \_ISO\WINPE (e.g. HBCD_PE, Strelec, DLCBoot, Gandalf)
  • \_ISO\WINDOWS\xxxx (Windows Install files)

The menu folders are in capital letters just under the \_ISO folder on the first partition. For example, copy a Windows 10 install ISO into the \_ISO\WINDOWS\WIN10 folder or copy a Linux ISO to the \_ISO\MAINMENU or \_ISO\LINUX folder.
Add your own new sub-menu folders by using a special batch file.

3.2 After copying over all your payload files, run the Windows batch file \MAKE_THIS_DRIVE_CONTIGUOUS.cmd file on the USB drive. This makes all the payload files contiguous. This should also be run again if you later add any new payload files. Contiguous files are needed for some types of operation (not required for Windows ISOs).

Tip: Use the \E2B Launcher.exe utility on the E2B USB drive to help you configure and use E2B.

E2B Launcher will help you use E2B.
Configure the E2B Menu system using E2B_Editor

Booting from your E2B USB drive

Don't use a cheap, slow USB 2.0 drive! I recommend a fast 16GB+ USB 3.0 USB flash drive like this one

If you want to know how to add a certain ISO or payload to E2B, your first step should be to find it on the 'List of tested ISOs' page. Note that the same ISO/payload/software may be listed in more than one place. 

If no special instructions or links are given, then the ISO/payload should 'just work' if you copy it to a normal menu folder on the E2B USB drive. 

For most payloads (except VHD\WIM fles) you will need to run \MAKE_THIS_DRIVE_CONTIGUOUS.cmd too. 

Test Legacy booting using QEMU

Check it boots by running \QEMU_MENU_TEST (run as admin).cmd from the USB drive (it should at least boot to the E2B Main menu). If it does not boot to the Main menu, you have done something wrong! If it does boot, then it should work on a real system - if not then the problem is with your system's BIOS/firmware settings - refer to the FAQ and Troubleshooting pages. The QEMU is a 32-bit emulator and should fully boot 32-bit ISOs (as if booting from a hard disk) too! The 32-bit QEMU used will not fully boot 64-bit ISOs. VHDs or WIM files, etc. 

Legacy/MBR booting on a real system

To boot from the E2B USB drive, first configure the BIOS for Legacy booting from a USB drive:

  • Disable Fast Boot - this causes the BIOS to detect bootable USB drives
  • Disable Secure Boot - You usually cannot enable Legacy booting unless this is disabled
  • Enable Legacy\CSM - modern UEFI BIOSes often have this option to enable Legacy booting also
  • First Boot Device; Internal Hard Disk - do NOT set the USB drive as the first boot device

To ensure that it boots from the E2B USB drive, connect the E2B USB drive, press the BIOS Boot Selection hotkey after switching on the system (depends on Make\Model): 

ACER:              Esc, F9, F12
APPLE:             Option/Alt key
ASUS:              Esc, F8
COMPAQ:            Esc, F9
DELL:              F12
EMACHINES:         F12
HP:                Esc, F9
INTEL:             F10
IBM LENOVO:        F12 (or Fn+F12), F10, F8
NEC:               F5
SAMSUNG:           Esc, F12
SONY:              F10, F11
TOSHIBA:           F12

Tip: If a laptop, try also holding down the Fn key first and then tapping the other Fxx key - e.g. Fn+F12. (check BIOS setting for Fn key option)

You may find this list of BIOS keys useful. 

E2B menu (no user ISOs have been added yet)

0 Set default menu entry and timeout – set the Main menu default menu option and countdown timeout
1 a1ive grub2 File Manager – loads the agFM grub2 menu system (Legacy mode)
2 Clover 64-bit UEFI Boot – Clover is a substitute UEFI BIOS, use it to boot various .EFI files from a Legacy BIOS (it is better to directly UEFI-boot from Partition 2, if possible)
3 Clover 32-bit UEFI Boot – Clover is a substitute UEFI BIOS, use it to boot various .EFI files from a Legacy BIOS (it is better to directly UEFI-boot from Partition 2, if possible)
4 Ventoy – loads the Legacy grub2-based USB multiboot Ventoy menu system
5 Disable UEFI64 secure Boot (blank screen BUGFIX) – some BIOSes will not load the Kaspersky shim which is used for bypassing Secure Boot. If you have Secure Boot enabled in your BIOS and you try to UEFI64-boot from partition 2 and get a blank screen on some systems, you will need to use this option to replace the Kaspersky Secure Boot shim and disable Secure Boot in your BIOS. Then UEFI64-boot using non-secure booting.
6 Disable UEFI-booting from Partition 2 – this is a workaround for another BIOS bug. Some UEFI BIOSes will not offer the choice to Legacy-boot from the E2B USB drive unless you remove the UEFI boot files. This option renames the EFI folder so that these BIOSes will allow you to Legacy boot from the E2B drive (the same menu option is available if you UEFI64-boot to agFM). To re-enable UEFI-booting from the E2B USB drive, you must first use the ‘Enable UEFI-booting from Partition 2’ menu entry.
7… – sub-menus and other options


Easy2Boot v2 adds agFM which allows you to UEFI-boot directly from the second FAT32 partition of the E2B USB drive and select an ISO, WIM file, VHD file, IMG file, etc. 
You can also load the Ventoy menu system from the agFM menu system (use F5).
You can also switch a Ventoy partition image into Partition 2 and directly UEFI-boot to Ventoy.

Partition Images

E2B and agFM can replace a partition on the USB drive with a different partition.
You can have any number of partition image files.
The partition image files can contain anything (FAT/NTFS/exFAT/ext4/hfs/linux swap, etc.)
You can then reboot to the replacement partition.
.ISO/.IMG/.VHD/.ZIP. etc, files or disk volumes can be converted to partition image files.
Partition image files have a file extension beginning with .IMGPTN

  • *.imgPTN - replaces Partition 1 (removes Partition 2 and Partition 3)
  • *.imgPTN23 - replaces Partition 1 (keeps Partition 2 and 3)
  • *.imgPTREP3 - replaces or adds Partition 3 (keeps Partitions 1 and 2)
  • ventoy.disk.image - replaces Partition 2 (keeps Partitions 1 and 3) - used only for official Ventoy partition contents

For UEFI and MBR booting (especially Secure Boot), you can switch-in a bootable partition image (.imgPTN/.imgPTN23 files): 

  1. Install the MPI Tool Kit onto your WIndows system.
  2. Convert the ISO (or payload file or existing USB drive volume) to a FAT32 .imgPTN23 file by dragging-and-dropping the ISO onto the MPI_FAT32 Desktop shortcut.
    For best speed, the source ISO should be on your hard disk and NOT on the USB drive.
  3. Copy the new .imgPTN file to your E2B drive (e.g. \_ISO\MAINMENU folder).
  4. Rename the file extension to .imgPTN23 so that partitions 2 and 3 are not removed.
  5. Run \MAKE_THIS_DRIVE_CONTIGUOUS.cmd from the E2B drive.
  6. Boot to E2B or agFM and select the .imgPTN23 file from the E2B menu - OR - run \_ISO\SWITCH_E2B.exe in Windows and double-click on the .imgPTN23 file.
    The USB drive's E2B partition #1 will be replaced by the new image.
  7. Now MBR/UEFI-boot from the E2B USB drive.

To make a sector-for-sector partition image of a non-Windows readable partition such as hfs or ext4, you can use RMPrepUSB.exe - Drive -> File (see .imgPTNREP3 for more details).

If your system does not have an MBR-boot option, you can UEFI-boot to the agFM menu or add WinPE files to a 2nd partition so that you can UEFI-boot to WinPE and select a .imgPTN file.

You can also copy partition image files onto Partition 3 of your E2B USB drive. The file should have a .imgPTNREP3 extension. When selected, it will replace the current Partition 3 with the contents inside the image file. This means you can switch in any partition containing any filesystem or swap file or raw partition. For instance, you could UEFI64-boot to agFM and switch-in an hfs partition image for installing Mac OSX onto a system.

https://easy2boot.xyz/ventoy/official-ventoy-image/agFM also allows you to replace Partition 2 with an official Ventoy partition image instead of the agFM partition. This means you will be able to boot to the latest version of Ventoy.

Need more help?

Look for the 'Chat' icon

Blog: rmprepusb.blogspot.com
RMPrepUSB: www.rmprepusb.com

I recommend the Sandisk Extreme Pro USB 3