YUMI (Your Universal Multiboot Installer) is a tool used to create Bootable USB drives. Quickly create a Multiboot USB Flash Drive containing multiple Bootable ISO files. Use it to boot your favorite Live Linux Operating Systems, Linux and Windows Installers, antivirus utilities, disc cloning, backup, penetration testing, diagnostic tools, and much more. YUMI makes it easy for anyone to create their very own custom All-In-One Multi use diagnostic USB PC Repair Toolkit.
This is the recommended successor to our Universal USB Installer and MultiBootISO tools. These were amongst the first tools made for the purpose of creating a USB bootable flash drive. Files are stored within the Multiboot folder, making for a nicely organized Portable Multiboot USB Drive that can still be used for other storage purposes.
Though YUMI was originally intended to be used to store and run various "LIVE Linux" Operating Systems and tools from USB, Using it to install Linux from USB to a Hard Drive works with most distributions. If you find a distribution where the installer does not work, please let me know.
YUMI Multiboot Bootable USB Flash Drive Creation
The tool works much like Universal USB Installer, except it can be used to run more than one distribution from your Thumb Drive. Distributions can also be uninstalled using the same tool!
Warning: The YUMI exFAT variant has been temporarily removed and should not currently be used, as it could prompt to update the wrong disk.
YUMI Legacy (BIOS only)
Legacy Setup Screen
Legacy Multiboot USB Boot Menu
YUMI Legacy Download and Changelog:
Jan 11, 2021 YUMI-22.214.171.124.exe: Moved persistent file creation to local drive when using NTFS formatted USB. Note: You'll need to make sure you have enough empty space to store the persistent file locally while it is being created. Created additional checkpoints for drive selection.
YUMI SHA-256: 5FC56FBB6773B7338A2DB4CF224156D8FD40CECF11A444842938C7C3D4CF2186
YUMI fat32 (UEFI+BIOS)
The UEFI version listed below utilizes GRUB2 for both UEFI and BIOS booting. Note that the UEFI variant is not compatible with the legacy variants. Supported distributions are limited, and your USB drive must be Fat32 formatted to support booting in UEFI mode. It includes a fat32format utility that can be used to format drives larger than 32GB as Fat32. Just be sure to backup your content from all partitions on the selected disk before formatting, as your drive will be wiped clean! You will also need to disable secure boot (if it is enabled).
YUMI UEFI/BIOS fat32 Download and Changelog:
Jan 11, 2021 YUMI-UEFI-0.0.3.3.exe: Updated to use Grub2 MBR instead of chainloading from Syslinux. Add additional drive checkpoints.
YUMI UEFI SHA-256: B92163B1E1DD99DE32BA09D7F554FE3C377B6CD4E350322075D7959CC0616DB5
Running YUMI from LINUX: WINE had previously worked for running YUMI from a Linux OS, with the exception of Formatting the USB drive. See How To
IMPORTANT NOTES: Your USB drive must be Fat32/NTFS formatted, otherwise Syslinux will fail and as a result, your drive will NOT Boot. For Legacy YUMI, NTFS may not work with every distribution but is required for storing files over 4GB. YUMI UEFI currently must use Fat32 format.
YUMI can be used to format your select USB drive, but be aware that all partitions on the select disk will also be deleted. Ensure that you have made a backup of any information you want to keep before using YUMI on any drive.
Basic Essentials to create a MultiSystem Bootable USB Drive
It is highly recommended you use a Fast SSD Flash Drive with YUMI
- Fat32 or *NTFS Formatted USB Flash or USB Hard Drive
- PC that can boot from USB
- Windows Vista/7/8/10 or Linux/Mac OS with (WINE)
- Your selection of ISO Files
Please inform me of unlisted "FREE" Live Linux distributions or version revisions, and I will attempt to update YUMI to support them, as I find time. Additionally, Bootable Software developers who wish to have their "PAID" software added, can send me a copy to try.
YUMI UEFI Changelog
01/11/21 Version 0.0.3.3: Updated to use Grub2 MBR instead of chainloading from Syslinux. Add additional drive checkpoints.
12/26/20 Version 0.0.3.2: Added back Show All Drives option. Fixed persistent file path (broken in 0.0.3.1). Updated to create a persistence casper-rw or writable file and label based on the ISO name. Supports persistent feature for Linux Mint and Ubuntu version 16 through 20+. Added feature to check for Legacy YUMI on selected drive.
11/19/20 Version 0.0.3.1: Switch to use Fat32Format only on partition/volume drive letter.
11/18/20 Version 0.0.3.0: Updated to use loopback method for Rescatux. Set to use Windows Diskpart with Fat32Format.
11/15/20 Version 0.0.2.9: Updated to detect exFAT/NTFS format type and suggest to reformat as Fat32 before proceeding. Otherwise syslinux fails to install and your drive won't be bootable.
10/04/20 Version 0.0.2.8: Updated to support Puppy Linux 9.5 (Fossapup64), and also Fixed broken CentOS 7 Live link.
09/01/20 Version 0.0.2.7: Updated to support KDE Neon, and also newer Ubuntu Server 18.04 + 20.04.
08/05/20 Version 0.0.2.6: Updated to support Endeavour OS, Bluestar, and also Cublinux. Fixed broken links for EasyPeasy, Avira Rescue CD, and also Xpud.
07/26/20 Version 0.0.2.5: Updated to support LinuxFX (AKA: WindowsFX – which is also an Ubuntu Based variant that looks and feels much like Windows 10).
07/17/20 Version 0.0.2.4: Add support for Ubuntus' newer "writable" casper persistence file label.
06/29/20 Version 0.0.2.3: Updated to support Rescuezilla, Q4OS, and also POP!OS.
04/29/20 Version 0.0.2.2: Updated to support Solus, Feren OS, and also Hiren's BootCD PE.
03/16/20 Version 0.0.2.1: Updated to support Linux Mint Debian Edition, Manjaro 19.0x, and also the newer ESET Sysrescue CD.
Legacy YUMI Changelog
01/11/21 Version 126.96.36.199: Moved persistent file creation back to local drive when using NTFS format (You'll need to make sure you have enough empty space to store the persistent file locally while it is being created). Created additional checkpoints for drive selection.
12/16/20 Version 188.8.131.52: Added checkpoint for Ubuntu partnew non-persistent menu entry.
12/04/20 Version 184.108.40.206: Added back support for casper persistence on NTFS. Updated Grub4Dos version. Now using Nullsoft Scriptable Install System compiler version 3.
11/26/20 Version 220.127.116.11: Added support back for older Ubuntu and Linux Mint casper-rw persistence. Limited max persistence file size creation for NTFS partitions to 20GB.
11/18/20 Version 18.104.22.168: Updated to use newer method for Rescatux.
11/01/20 Version 22.214.171.124: Fixed several links (still more to check). Updated to support newer Android-x86 and pmagic_2020_10_12.iso.
10/26/20 Version 126.96.36.199: Moved casper writable file creation to occur on USB. Implemented a fix to check for NTFS format before copying over ISO files larger than 4GB. Added Other OS entry for Sergei Strelec.
10/23/20 Version 188.8.131.52: Updated to support Ubuntu 20.10 Groovy Gorilla and derivatives. Also changed System Rescue CD to System Rescue.
10/05/20 Version 184.108.40.206: Updated to support Puppy Linux 9.5 (Fossapup64), and also the newer Ultimate Boot CD.
08/04/20 Version 220.127.116.11: Updated to support Endeavour OS. Also fixed broken links for Antergos, EasyPeasy, Xpud, Bluestar, and CubLinux.
07/26/20 Version 18.104.22.168: Updated to support LinuxFX.
07/17/20 Version 22.214.171.124: Support Ubuntu's "writable" casper persistence file label.
06/27/20 Version 126.96.36.199: Updated to support Q4OS, Rescuezilla, and also newer Memtest86+ 5.31. Corrected grub partition 4 Warning to read "Fourth partition table entry is not empty".
04/29/20 Version 188.8.131.52: Updated to support booting Debian Live, Linux Mint, and also Linux Mint Debian Edition via NTFS using Grub Partition 4.
How to Create a MultiBoot USB Flash Drive (Windows)
- Run* YUMI-184.108.40.206.exe following the onscreen instructions.
- Then, Run the tool again to Add More ISOs/Distributions to your Drive.
- Restart your PC. But be sure to set it to boot from the USB device.
- Select a distribution to launch. Then, boot and enjoy!
That's really all there is to it. If all went well, then you should be booting your favorite distributions from your custom Multi-Boot USB device!
Creating a MultiBoot USB Flash Drive (Linux)
The following instructions were performed from an Ubuntu host environment.
NOTE: YUMI persistence option is currently broken when using YUMI-220.127.116.11.exe within WINE. As a result, don't choose persistence and set the slider or the process will freeze while trying to build the persistent file and you will be forced to close YUMI.
I. Format your USB Flash Drive to use a Single Partition:
- Open a terminal and type
fdisk -l(and note which device is your USB Drive)
fdisk /dev/sdx(replacing x with your actual usb device)
d(to delete the existing partition)
n(to create a new partition)
p(for primary partition)
1(to create the first partition)
Press Enter(to use the first cylinder)
Press Enteragain (to use the default value as the last cylinder)
1(to mark the first partition active "bootable")
t(for partition type)
c(to use fat32 partition)
w(to write the changes and close fdisk)
II. Create a Fat32 Filesystem on the USB Flash Drive:
umount /dev/sdx1(to unmount the mounted partition)
mkfs.vfat -F 32 -n MULTIBOOT /dev/sdx1(to format the partition as fat32)
- Remove and reinsert your USB flash drive, or remount it
III. Install WINE:
- To install WINE from within an Ubuntu operating environment, first open a terminal and type sudo apt install wine, then press enter. Once WINE is installed, launch YUMI as you normally would by simply clicking the YUMI-18.104.22.168.exe
How YUMI Works
YUMI (Your Universal Multiboot Installer) enables each user to create their own custom Multiboot UFD containing only the distributions they want, in the order by which they are installed. A new distribution can be added to the UFD each time the tool is run.
If you run YUMI from the same location you store ISO files, then they should be auto detected (*See Known Issues Below), eliminating the need to browse for each ISO.
Other Notes: If MultibootISOs was previously used, you must reformat the drive, and start over. YUMI uses Syslinux directly, and chainloads to grub only if necessary, so it is not compatible with the older Multiboot ISO tool. Although I do plan to add back most of the capabilities of MultibootISOs as time permits.
Not all Unlisted ISO's can be booted (thus adding Unlisted ISOs is an UNSUPPORTED option).
YUMI can Create a Bootable UFD of the following distros/tools
— Debian Live 32/64 Bit —
- Debian Live
— Fedora 32/64 Bit —
— Linux Mint 32/64 Bit —
- Linux Mint
— OpenSUSE 32/64 Bit —
- OpenSUSE 32bit
- * OpenSUSE 64bit
— Puppy Linux 32/64 Bit —
- DPup Exprimo
- Lucid Puppy Linux
- Precise Puppy Linux
- Racy Puppy Linux
- Slacko Puppy
- Wary Puppy Linux
— Ubuntu 32/64 Bit —
- * Ubuntu Gnome
- ** Ubuntu Server Installer
- *** Ubuntu Secure Remix
- **** Ubuntu Studio
— Other Distros Alphabetical —
- CAELinux (Computer Aided Engineering)
- CentOS Live
- Damn Small Linux (DSL)
- gpxe (Net Bootable Distros)
- OSGeo Live
- Peach OSI Linux
- Pear Linux
- Pinguy OS
- Scientific Linux CERN
- Semplice Linux
- SLAX (Tiny Slackware Based Distro)
- Slitaz (Another Tiny Distro)
- Sparky Linux
- Sugar on a Stick
- System Rescue CD
- Tails (Anonymous Browsing)
- Liberte (Anonymous Browsing)
- TinyCore (A Tiny Linux Distribution)
- Ultimate Edition 3
- Zorin OS Core
———— NetBook Distributions ————
- EasyPeasy (NetBook Distro)
- Jolicloud (NetBook Distro)
- Ubuntu Netbook Remix
- xPUD (Netbook Distro)
————— Antivirus Tools —————
- Acronis Antimalware CD
- AOSS (Malware Scanner) system\stage1
- AVG Rescue CD (Antivirus Scanner)
- AVIRA AntiVir Rescue CD (Virus Scanner) ; does install to root of drive
Bitdefender Rescue Disk (Antivirus Scanner)
- Comodo Rescue Disk (Antivirus Scanner)
- Dr.Web Live CD ; does install to root
- F-Secure Rescue CD
- GDATA Rescue CD
- Kaspersky Rescue Disk (Antivirus Scanner)
- Panda SafeCD
- Windows Defender Offline
—————– System Tools —————-
- Acronis True Image
- BackBox (Penetration Testing)
- BackTrack5 (Penetration Testing)
- Boot Repair Disk
- Clonezilla (Backup + Clone Tool)
- DBAN (Hard Drive Nuker)
- Deft (Forensics)
- DRBL (Diskless Remote Boot in Linux)
- EASEUS Disk Copy (Disk Cloning Tool)
- FreeDOS (Balder img)
- GParted (Partition Tools)
- GRML (system rescue)
- HDT (Hardware Detection Tool)
- Kali (Penetration Testing)
- Memtest86+ (Memory Testing Tool)
- Matriux (Penetration Testing)
- Offline NT Password & Registry Editor
- Ophcrack (Password Finder)
- Parted Magic (Partition Tools)
- PING (Partimg Is Not Ghost)
- Partition Wizard (Partition Tools)
- Redo Backup And Recovery (Recovery Tools)
- Rip Linux (Recovery Distro)
- Trinity Rescue Kit ; does install to root of drive
- Ultimate Boot CD (Diagnostics Tools)
- Web Converger (Web Kiosk)
- —————– Other OS/Tools —————-
- Linux Live Tools for OCZ
- Hiren's Boot CD ; does install to root of drive
- Falcon 4 Boot CD ; does install to root of drive
- Kon-Boot Floppy Image
- Windows Vista/7/8/10 Installer
- Windows XP Installer
—————– Bootable ISOs —————-
- Try an Unlisted ISO (SYSLINUX)
- * Try an Unlisted ISO (GRUB)
- ** Try an Unlisted ISO (GRUB Run from RAM)
YUMI Troubleshooting, Known Issues, Bugs
NOW FIXED in the latest YUMI revision. – casper-rw Persistence is not currently working with Ubuntu-20.04 and variants due to an upstream filename requirement change. To fix the persistent feature, simply rename the "casper-rw" file to "writable" but without the quotes. This file can be found on your YUMI USB drive in folder I.E. /Multiboot/Ubuntu-20.04-desktop-amd64.
The Persistence feature is currently broken with Newer Debian based distributions due to significant changes upstream. Debian now requires the persistent block file and label to be named persistence instead of live-rw, and it must hold a persistence.conf file containing / Union. I am hoping to make the necessary changes and provide a fix soon.
If you encounter a message stating
An error (1) occurred while executing syslinux. Your USB drive won't be bootable.
Make sure your USB drive is formatted using a Fat32 or NTFS partition with an MBR (Master Boot Record). An exFAT formatted Partition will not work. GPT (GUID Partition Table) Fat32 or NTFS Partitions are also not currently supported.
If you encounter a message stating
Insane primary (MBR) partition. Can’t find myself on the drive I booted from
First, replace your chain.c32 file located at multiboot/chain.c32 with (you'll need to unzip the file) -> This zipped chain c32 File
If replacing the chain.c32 file does not fix the problem, your USB drive may be improperly formatted, contains more than one partition or MBR, or your BIOS is not properly detecting the USB drive as USB-HDD, and/or its firmware needs to be updated. You can try these methods to Format and Restore your USB Drive
Windows to Go/Installers – Options Explained
The Windows to Go option creates a VHD file that is 20GB in size. As such, it requires the drive to be formatted NTFS. Fat32 cannot support a file more than 4GB in size. Many flash drives you might find at local department stores won't be fast enough. You'll need a Very Fast Flash Drive. When Windows boots from the USB for the first time, it'll go through the setup process and then reboot. You'll need to boot using your Windows to Go menu option a second time to finalize the setup process and finally boot into your full Portable Windows.
The Single Windows Installer/PE options are most likely to work for both stock and modified ISO files. When using it, you are limited to storing one Windows Installer per USB drive (I.E. one Win XP and one Win Vista 7 or 10). The Multiple Windows Installer/PE options allow for storing more than one stock Windows Installer per drive. Generally, only unmodified Windows ISO files will work with this option.
-wimboot option stores the extracted Multi Windows Installers in their own directory. -bootmgr option moves the bootmgr and bcd files to root of drive. (note: -bootmgr option does require a Windows Vista or later host to run bcdedit).
Traditional YUMI is not natively UEFI capable. However, it is possible to boot and run your Windows Installers from UEFI. To switch between added Windows versions, navigate to the multiboot/win-directory (replacing win-directory with the Windows version you want to boot) on your USB. Once there, move the bootmgr, bootmgr.efi, and entire boot folder to the root of your USB drive. Then reboot, booting your computer from the UEFI compatible USB. If all went well, it should boot straight into your chosen Windows Installer.
Try an Unlisted ISO – Options Explained
- Try Unlisted ISO (Grub Partition 4) – This boot option will attempt to boot the ISO file using Grub. Additionally it adds a 4th partition table to the USB device and uses this as a placeholder for the ISO. This option has been shown to successfully boot almost all Linux based distributions.
- Try Unlisted ISO (Grub) – Same as boot option 1, but attempts to boot the ISO without using a 4th partition as a placeholder for the ISO.
- Try Unlisted ISO (Grub From RAM) – Same as boot option 2, but attempts to store the ISO in system memory and boot it from there. Useful for cases where the ISO is small, and you'd like to boot the OS and then move the USB to different machines and subsequently boot the OS from them as well.
- Try Unlisted ISO (via Syslinux) – The original default YUMI supported boot option. Syslinux works to boot many distributions, but not all.
Multiboot folder and volume name.
YUMI attempts to store most added distributions within the multiboot folder. This is also the root directory set for syslinux. In some cases, YUMI also expects the Volume Label of your USB drive to be MULTIBOOT in order for OpenSUSE, CentOS and several other distributions to boot. YUMI will attempt to automatically create this Volume Label, however it can sometimes fail. So please ensure that the Volume Label of your USB remains MULTIBOOT if you expect your distributions to boot.
When booting linux distributions from some laptops such as the Lenovo Yoga with a touchscreen, the acpi=off boot parameter might be necessary in order to successfully boot.
My PC wont Boot from my Flash Drive, but BIOS supports USB boot!
Some Flash Drives ship formatted (without a partition), as a result, YUMI requires the drive to contain a partition with a MBR (Master Boot Record). To ensure compatibility, you can use YUMI to format your device as NTFS or Fat32.
How to force a rebuild of the Syslinux MBR:
This is useful if your YUMI prepared USB drive is somehow no longer bootable.
For YUMI Legacy:
From the multiboot folder on your flash drive, delete the hidden file ldlinux.sys and then rename the libcom32.c32 file to _libcom32.c32. Then use YUMI to install any menu item. YUMI will notice that the file is missing and will attempt to reinstall syslinux and repair the master boot record. Once finished, rename _libcom32.c32 back to libcom32.c32.
Other Known Issues:
TAILS – If your USB is detected as a "fixed" hard drive and not a "removable" disk, (a few Sandisk drives have the removable bit flipped this way), you'll have to remove occurrences of the boot parameter "live-media=removable" from the Live64.cfg file found at "\multiboot\tails-amd64-3.3\EFI\BOOT\" or consequently TAILS will fail to find the live filesystem.
The files for Flacon 4, Hiren's Boot CD, Trinity Rescue Kit, Backtrack, Avira Antivir, and Dr.Web Live are all stored outside of the multiboot folder. Most other distribution files remain contained within the multiboot folder. I am open to a simple working solution!
YUMI supports Windows XP Install from USB via ISO. In order for the Windows XP installation to succeed, you must perform the following steps;
1.) To begin an install, select (Stage 1)
2.) Upon first reboot, you must select (Stage 2)
3.) Finally, after (Stage 2) is complete – upon the second reboot, select (Stage 3) to boot the drive where you installed Windows XP. If this option fails, simply remove the USB and reboot!
* YUMI does support NTFS, however not all distributions will boot from an NTFS formatted device. NTFS is required for Windows to Go and distributions containing files over 4GB.
Troubleshooting Boot Errors:
While trying to run an ISO from USB, If you get a Boot error saying:
Error 60: File for drive emulation must be in one contiguous disk area
This generally happens on the persistence file, when using YUMI Legacy with NTFS format. Because the persistence file is generated on the USB, it needs to be defragmented. You'll likely have to do this right after adding an Ubuntu based distro with persistence on an NTFS drive. Fat32 won't encounter this issue.
You'll need to defragment your ISO using one of the following tools to defragment the ISO or persistence file:
Defraggler <— recommended (free version works fine).
contig – Command line tool used to defragment ISO files.
wincontig – GUI tool used to defragment ISO files.
When using Legacy YUMI, any non-booting or broken menu entries for ISO files added via the "Try an Unlisted ISO (GRUB)" options, can be fixed by editing each corresponding entry in \multiboot\menu\menu.lst
If you don't have a floppy drive and get fd0 errors while booting, simply add floppy.allowed_drive_mask=0 to the append line for the troubled entry. Although the best fix is to simply disable floppy in BIOS.
Persistently Saving Changes: YUMI currently enables the casper-rw persistence feature for some (but not all) Ubuntu based distributions. Yes, you can also have multiple persistent distributions, as each distro utilizes its own casper-rw file. * Persistence will NOT work on NTFS formatted USB drives. Additionally, some distributions will not even boot via NTFS!
Ophcrack Tables. In order to load Ophcrack tables, the tables folder needs to exist at the root directory of the USB device; (example F:\tables\vista_free). You can Get Ophcrack Tables from the Official Ophcrack site. Once downloaded, simply unzip them to the root of your USB. Because you're using this method, you can have your Windows XP and Vista/7/10 tables all working together on the same device.
YUMI on Linux:
You can run YUMI on a Linux Host via WINE. Current versions of YUMI might no longer properly run from WINE. Partially due to the fact that YUMI requires (Root) permissions to modify the boot sector of a device. Please do let me know if you find success running YUMI from Wine so I can update this section accordingly.