Every sysadmin has been there. You need to reinstall a system, test a new distro, or run a rescue tool, and you end up reformatting your USB drive for the third time that week. It kills productivity. The solution to that problem is learning how to install Ventoy on Ubuntu 26.04, a process that takes under ten minutes and saves hours of repeated work.

Ventoy is an open-source tool that installs a bootloader onto your USB drive. After that, you simply copy ISO files onto the drive and they show up in a clean boot menu automatically. No reformatting. No re-flashing. Just copy, boot, and go.

Ubuntu 26.04 LTS, codenamed “Resolute Raccoon,” shipped on April 23, 2026, with Linux kernel 7.0, GNOME 50, and a fully Wayland-only desktop. X11 has been removed entirely in this release. That means if your Wayland session breaks or a display driver causes a black screen at login, you need a reliable multi-boot USB ready to go. Ventoy fills that role perfectly.

In this guide, you will learn the complete Install Ventoy on Ubuntu 26.04 setup process: how to download, extract, identify your USB device safely, install using both the command line and the WebUI, verify the setup, copy ISOs, boot from the drive, update Ventoy without losing your files, and fix the most common errors sysadmins run into. Every step includes an explanation of not just what to do, but why you are doing it.

Prerequisites

Before you start, make sure you have the following ready. Skipping any of these will cause problems later.

• Ubuntu 26.04 LTS (Resolute Raccoon) installed and fully updated
• A user account with sudo privileges (required to write to block devices)
• A USB drive of 8GB or larger (16GB or more is strongly recommended for multiple ISOs)
• An active internet connection to download Ventoy from GitHub
• Basic comfort with the GNOME 50 terminal (Ptyxis is the new default terminal in Ubuntu 26.04) or any terminal emulator of your choice
• All data on the USB drive backed up before you start. Ventoy formats the drive during installation and deletes all existing data permanently.

Step 1: Update Your Ubuntu 26.04 System

Before you install any tool on a Linux system, updating your package index and installed packages is always the right first move. This ensures you have the latest security patches and that system libraries are current.

Run these two commands in your terminal:

sudo apt update
sudo apt upgrade -y

What this does: apt update refreshes the list of available packages from Ubuntu’s repositories. apt upgrade -y installs all available updates without asking for confirmation on each one.

Why you need to do this first: Ubuntu 26.04 runs Linux kernel 7.0. If your kernel headers or firmware packages are out of date, certain USB drivers may behave unpredictably when Ventoy writes to the drive. A fresh, fully updated system eliminates those edge cases before they become problems.

Expected output when the update finishes:

Reading package lists... Done
Building dependency tree... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

If packages were upgraded, reboot before continuing. This is especially important if a new kernel version was applied.

Step 2: Download the Latest Ventoy Release for Linux

Ventoy does not have an official APT package in Ubuntu’s repositories. You download it directly from the official GitHub releases page. This is the only source you should use, because Ventoy runs as root and has full write access to your block devices.

Use wget to download directly from the terminal:

wget https://github.com/ventoy/Ventoy/releases/download/v1.1.10/ventoy-1.1.10-linux.tar.gz

What this does: wget sends an HTTP request to GitHub and saves the Ventoy Linux archive to your current working directory. The filename ventoy-1.1.10-linux.tar.gz confirms you have the Linux-specific package.

Why you must use the Linux .tar.gz file and nothing else: The Windows .zip package does not contain Ventoy2Disk.sh or VentoyWeb.sh, which are required for Linux installation. Downloading the wrong file means the installer does not exist when you look for it in the next step.

After the download finishes, confirm the file is present and non-zero in size:

ls -lh ventoy-1.1.10-linux.tar.gz

You should see a file around 14 to 16 MB. A 0-byte result means the download failed and you need to retry.

Field note: Always check the GitHub releases page for the current latest version before downloading. Replace v1.1.10 in the URL above with whatever the current release number shows. Running an outdated version means missing bug fixes and compatibility updates for newer hardware.

Step 3: Extract the Archive and Review Its Contents

Extract the compressed archive:

tar -xzf ventoy-1.1.10-linux.tar.gz

Change into the extracted directory:

cd ventoy-1.1.10

List the contents:

ls -la

You will see files including:

Ventoy2Disk.sh
VentoyGUI.x86_64
VentoyGUI.aarch64
VentoyWeb.sh
ventoy/
boot/

Here is what each file does:

• Ventoy2Disk.sh: The command-line installer. This is what most sysadmins use.
• VentoyWeb.sh: Starts a local web server at http://127.0.0.1:24680 with a browser-based installation interface.
• VentoyGUI.x86_64: A native GTK graphical installer for 64-bit x86 desktops.
• ventoy/: The core bootloader files written to the USB drive’s second partition.

Why reviewing the file list matters: Knowing what each script does before you run anything as root prevents mistakes. Running the GTK GUI without understanding it or picking the wrong installer wastes time and can create unexpected results.

Step 4: Identify Your USB Drive Device Name

This is the most critical step in the entire Linux server tutorial. Running the Ventoy installer on the wrong device will destroy all data on that drive permanently. If that device happens to be /dev/sda, your main system disk, you will wipe your entire operating system. There is no undo.

Plug in your USB drive, then run:

lsblk

Output example:

NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda      8:0    0  512G  0 disk
├─sda1   8:1    0    1G  0 part /boot/efi
├─sda2   8:2    0    2G  0 part /boot
└─sda3   8:3    0  509G  0 part /
sdb      8:16   1   32G  0 disk
└─sdb1   8:17   1   32G  0 part /media/youruser/MyUSB

In this example, sdb is the USB drive because it is marked RM 1 (removable media), its size matches the physical drive you plugged in, and it has a mount point under /media/.

The device name you need is /dev/sdb, not /dev/sdb1. Ventoy targets the whole disk, not a single partition.

A reliable field method to confirm the right device: Run lsblk before plugging in the USB drive. Then plug it in and run lsblk again. The new entry that appears is your USB drive. This before-and-after comparison eliminates any guesswork.

For additional detail, run:

sudo fdisk -l

This shows the full partition table for every connected disk including model name and vendor, making device identification even clearer. Write down the device path, for example /dev/sdb, before you move to the next step.

Step 5: Install Ventoy on Ubuntu 26.04 on Your USB Drive

Step 5A: Install via Command Line (Recommended for Sysadmins)

The CLI method is fast, repeatable, and the approach most Linux administrators use. Make sure you are inside the ventoy-1.1.10 directory, then run:

sudo ./Ventoy2Disk.sh -i /dev/sdb

Replace /dev/sdb with your actual device from Step 4. Ventoy will display a warning and ask you to confirm twice. Type y and press Enter both times.

What the -i flag does: It installs Ventoy only if the device does not already have Ventoy on it. This is a built-in safety check. If Ventoy is already present, the command stops rather than overwriting blindly.

Here is a reference for the flags you will use most often:

For Ubuntu 26.04 on modern UEFI hardware, use this command:

sudo ./Ventoy2Disk.sh -i -s /dev/sdb

Why the -s flag is critical on Ubuntu 26.04: Ubuntu 26.04 runs on UEFI hardware with Secure Boot enabled by default. Without this flag, the USB drive will not boot on those machines. The -s flag tells Ventoy to include its MOK (Machine Owner Key) so the firmware can verify the bootloader as trusted before handing off control.

A successful install produces this output:

Install Ventoy to /dev/sdb successfully finished.

Step 5B: Install via WebUI (Beginner-Friendly Alternative)

If you want a visual confirmation before committing, the WebUI is a strong alternative. From inside the ventoy-1.1.10 directory, start the local web server:

sudo ./VentoyWeb.sh

The terminal outputs:

===============================================================
  Ventoy Server 1.1.10 is running ...
  Please open your browser and visit http://localhost:24680
===============================================================

Open Firefox and navigate to http://127.0.0.1:24680. Then:

1. Select your USB device from the dropdown
2. Click Options and enable Secure Boot Support if on UEFI hardware
3. Click Install and confirm the two warning dialogs

Why the WebUI only runs on localhost: It binds exclusively to 127.0.0.1 by design. This means no remote user or process can trigger a USB format over your network. It is a local operation only.

Stop the WebUI server when finished by pressing Ctrl+C in the terminal.

Step 6: Verify the Installation

After installation, confirm that Ventoy wrote its two-partition structure correctly. A drive with a missing bootloader partition will not boot regardless of what ISO files are on it.

Run lsblk targeting your USB device:

lsblk /dev/sdb

Expected output:

NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
sdb      8:16   1   32G  0 disk
├─sdb1   8:17   1 31.9G  0 part /media/youruser/Ventoy
└─sdb2   8:18   1   32M  0 part

This is exactly what you want to see:

• sdb1: The large exFAT partition where you copy ISO files. GNOME 50 Nautilus will auto-mount this as “Ventoy.”
• sdb2: The 32MB partition holding the Ventoy bootloader. This is not a formatting error. It is intentional and required.

Use Ventoy’s own verification command to check the installed version:

sudo ./Ventoy2Disk.sh -l /dev/sdb

Expected output:

           ventoy in disk : 1.1.10
          ventoy in local : 1.1.10

If both version numbers match, the installation is valid. If ventoy in disk shows nothing, the bootloader partition was not written correctly and you need to reinstall.

Step 7: Copy ISO Files to the Ventoy Drive

Ubuntu 26.04 with GNOME 50 auto-mounts the Ventoy partition in Nautilus as a standard drive. Copy ISOs using the terminal:

cp ~/Downloads/ubuntu-26.04-desktop-amd64.iso /media/$USER/Ventoy/

For a well-organized multi-boot setup, create folders by category:

mkdir -p /media/$USER/Ventoy/Linux
mkdir -p /media/$USER/Ventoy/Rescue
mkdir -p /media/$USER/Ventoy/Utilities

cp ~/Downloads/ubuntu-26.04-desktop-amd64.iso /media/$USER/Ventoy/Linux/
cp ~/Downloads/kali-linux-2026.2-live-amd64.iso /media/$USER/Ventoy/Linux/
cp ~/Downloads/systemrescue-11.01-amd64.iso /media/$USER/Ventoy/Rescue/

What Ventoy does with folders: It recursively scans all subdirectories on the first partition for ISO, WIM, IMG, VHD, and EFI files. Every file it finds appears in the boot menu by filename. Folders do not affect bootability in any way.

Why folder organization matters: When you have 8 to 10 ISOs on one drive, a flat unsorted list is slow to navigate during high-pressure recovery situations. A clean folder structure turns the boot menu into a usable tool rather than a wall of filenames.

A few practical notes:

• The Ubuntu 26.04 desktop ISO is over 6GB. Copy time varies based on USB drive speed.
• Use USB 3.0 drives whenever possible. Boot times from USB 2.0 on a live system are significantly slower.
• Never unplug the drive mid-copy. Wait until the terminal prompt returns or the file manager shows the copy is complete.

Step 8: How to Boot from the Ventoy USB Drive

With ISOs on the drive, you are ready to boot from any machine.

1. Plug the USB drive into the target computer
2. Restart the machine
3. Access the BIOS/UEFI boot menu. Common keys: F12 (most systems), F2, ESC, or DEL
4. Select your USB drive from the boot device list
5. The Ventoy menu appears listing all detected ISOs
6. Use arrow keys to highlight your ISO and press Enter

First Boot: Secure Boot MOK Enrollment

If you installed with the -s flag, the first boot on a Secure Boot system shows a blue screen titled “Perform MOK management.” This is expected and normal.

Steps to enroll the Ventoy key:

1. Press Enter on “Verification failed” screen
2. Press any key on “Shim UEFI key management” screen
3. Select Enroll key from disk and press Enter
4. Select VTOYEFI and press Enter
5. Select ENROLL_THIS_KEY_IN_MOKMANAGER.cer and press Enter
6. Select Continue, then Yes
7. Select Reboot

Why you only do this once: After enrolling, your UEFI firmware stores Ventoy’s certificate in its trusted key database. Every subsequent boot recognizes Ventoy automatically without re-enrollment.

From the Ventoy menu, three boot modes are available:

• Default mode (Enter): Boots the ISO directly. Works for the vast majority of modern Linux distributions.
• GRUB2 mode (F6): Passes boot control to the ISO’s internal GRUB2. Use this when an ISO does not boot cleanly in default mode.
• Memdisk mode: Loads the entire ISO into RAM before booting. Useful for very small ISOs or legacy tools that require it.

How to Update Ventoy Without Losing Your ISO Files

When a new Ventoy version releases, use the update flag instead of reinstalling from scratch.

Download and extract the new version, then run:

sudo ./Ventoy2Disk.sh -u /dev/sdb

What -u does: It rewrites only the 32MB bootloader partition (Partition 2) with the new version. Your ISO files on Partition 1 are completely untouched.

Why you must never use -I when updating: The capital -I flag is a force-install that wipes and reformats the entire drive. It is for starting fresh on a drive, not for version upgrades. Using it by mistake will delete every ISO you stored on the drive.

Verify the update succeeded:

sudo ./Ventoy2Disk.sh -l /dev/sdb

Both ventoy in disk and ventoy in local should now show the new version number.

Configure Ventoy on Ubuntu 26.04: Best Practices

Getting Ventoy running is the first step. Running it well over time is what separates a clean setup from a chaotic one. These are the practices worth building into your workflow from day one.

Use GPT partition style on all modern hardware:

sudo ./Ventoy2Disk.sh -i -s -g /dev/sdb

GPT supports drives larger than 2TB and is standard on all modern UEFI systems. MBR is only the default for maximum compatibility with old legacy BIOS hardware. If your environment is all UEFI, always use GPT.

Keep a consistent folder structure on the drive:

/Ventoy/
  Linux/
  Windows/
  Rescue/
  Utilities/
  README.txt

A README.txt at the root should document the Ventoy version installed, the last update date, and which ISOs live in each folder. When you hand this drive to a colleague during an incident at 2 AM, that file saves time.

Check for Ventoy updates whenever a major Ubuntu or kernel release lands. Newer kernels occasionally change USB driver behavior, and a Ventoy update often addresses those changes.

Use a high-quality USB 3.0 drive. Boot times from a USB 2.0 drive on a live Linux system are noticeably slow. A USB 3.0 drive cuts ISO load times significantly, which matters during system recovery work.

Troubleshooting Common Errors

Error 1: USB Drive Not Detected by lsblk

Symptom: The USB drive does not appear after running lsblk.

Why this happens: Some USB 3.0 ports on Ubuntu 26.04 systems with kernel 7.0 have a brief device enumeration delay.

Fix: Wait five seconds and run lsblk again. Try a different port if it still does not appear. Check kernel logs for USB errors:

dmesg | tail -20

A failed device shows an error like unable to enumerate USB device on port X.

Error 2: “Device is Write-Protected” During Installation

Symptom: Ventoy fails with a write-protection error.

Why this happens: Some USB drives have a physical write-protect switch, or the drive has entered a software read-only state.

Fix: Check the physical body of the USB drive for a small toggle switch and set it to the unlocked position. If no physical switch exists, clear the software read-only flag:

sudo hdparm -r0 /dev/sdb

Error 3: Ventoy USB Does Not Show Up in BIOS Boot Menu

Symptom: The USB drive is not listed as a boot option.

Why this happens: Either the two-partition structure is incomplete, or the system’s UEFI requires a GPT partition table for recognized boot entries.

Fix: First verify both partitions exist with lsblk. If sdb2 is missing, reinstall Ventoy. If partitions look correct, try reinstalling with the GPT flag:

sudo ./Ventoy2Disk.sh -I -s -g /dev/sdb

Error 4: Secure Boot Verification Error on First Boot

Symptom: The machine shows “Verification failed: (0x1A) Security Violation” and refuses to boot.

Why this happens: Ventoy was installed without the -s flag on a Secure Boot-enabled UEFI system.

Fix: Re-run the installation with the -s flag, using capital -I since Ventoy is already on the drive:

sudo ./Ventoy2Disk.sh -I -s /dev/sdb

Error 5: ISO Selects But Boots to Black Screen

Symptom: Selecting an ISO from the Ventoy menu results in a black screen with no output.

Why this happens: Some older rescue tools and specialized distributions do not boot cleanly in Ventoy’s default mode.

Fix: At the Ventoy menu, press F6 to switch to GRUB2 mode before selecting the ISO. GRUB2 mode hands boot control to the ISO’s own internal bootloader, resolving compatibility issues for most problematic ISOs.