Open source · UEFI & BIOS
Ventoy formats your drive once, then you simply copy ISO, WIM, IMG, VHD(x), and EFI files onto it. Reboot, choose a menu entry, and go—no need to reflash the stick for every new image.
This site is an independent English guide. Ventoy is developed by longpanda; always verify downloads using SHA-256 hashes from the official Ventoy download page or release notes.
Compared with writing one image at a time, Ventoy is built around a simple idea: treat the USB like storage that also happens to boot. That workflow saves time for IT staff, students, and hobbyists who juggle several live systems or installers.
Keep Ubuntu, Debian, Windows 11, memtest, and a recovery ISO on the same drive. Swap files when you need to—no second tool required for each ISO.
Download a new nightly or point release, copy it over, reboot. Ideal when you are testing distros or building a classroom image set.
Ventoy supports UEFI and Legacy BIOS. Secure Boot often works after enrolling Ventoy’s key or following the documented MOK process—details vary by machine and firmware.
Optional plugins extend themes, auto install scripts, and persistence for supported Linux ISOs—check the official plugin documentation for your distro.
Run the Ventoy installer (Windows executable or Linux script). It partitions the device: a small EFI/boot area for Ventoy itself and a large exFAT/NTFS/FAT32 space for your files.
Use your file manager. You can organize subfolders; Ventoy can scan them depending on version and settings. Very large files are supported when the filesystem allows.
Firmware loads Ventoy, which presents a menu mapped to your ISOs. The selected image is exposed to the OS installer or live session without extracting to the stick first.
Use the direct download card below (link refreshes each page load). For classic mirrors, browse SourceForge or the Gitee card. Always compare the SHA-256 hash with the official Ventoy download page or the mirror you used.
Primary download link (new URL each visit). You can still use SourceForge or Gitee below for mirrors and checksums.
Official project mirror: release packages and release notes. Use this if SourceForge is slow or you prefer downloading from Gitee.
Security habit
Do not trust random re-uploads on file hosts. Prefer SourceForge, Gitee, or links listed on ventoy.net/en/download.html. Verify hashes every time you download a new version.
Full Ventoy2Disk window on Windows. Double-check the selected device before installing.
sudo ./Ventoy2Disk.sh -i /dev/sdX—replace sdX with your device, never guess).lsblk to confirm the block device before you wipe it.cp.The following patterns come from common forum posts and FAQs (paraphrased for clarity). They are not quotes from identified individuals; treat them as starting points and confirm against your hardware and Ventoy version.
“I support a small office. One Ventoy stick carries our Windows image, a live Linux for disk checks, and firmware update ISOs. When Windows 11 revisions ship, I only replace one file.”
“My laptop only likes exFAT for large ISOs. I formatted the Ventoy data partition accordingly after checking the docs—then Fedora and Ubuntu live images both appeared in the menu.”
“Secure Boot blocked Ventoy until I followed the MOK enrollment steps. After that, BitLocker and corporate policies still applied to the internal drive—only the USB chain changed.”
“A single ISO failed with a black screen; others worked. Updating Ventoy to the latest release and retrying with the ISO’s ‘compatible’ mode in the Ventoy menu solved it.”
Open firmware settings (UEFI). Disable “fast boot” where relevant, enable USB boot, and move the USB device above the internal disk in the boot order. On some boards you must use a one-time boot menu (often F8, F11, or F12).
Read Ventoy’s Secure Boot section in the official documentation. You may need to enroll the Ventoy key, temporarily disable Secure Boot for installation only, or update firmware. Corporate-managed laptops may block unsigned bootloaders entirely.
Verify the ISO checksum from the distributor. Try Ventoy’s GRUB2 or memdisk modes if offered for that entry. Search the Ventoy forum for your distro name plus “Ventoy” and your symptom—often someone already posted a workaround.
When installing an OS from Ventoy, installers still show all disks. Never format the Ventoy USB by mistake. Read size labels carefully; disconnect spare drives if you are unsure.
Linux kernels and Windows media evolve. If a brand-new ISO fails, update Ventoy first, then retest. The official news / changelog lists fixes per release.
These links go straight to the Ventoy project—use them to verify releases, read documentation, and reach community support.
Extended reference — 33 deep-dive topics
The sections below expand on workflows, hardware, firmware, and edge cases. They complement (rather than repeat) the overview, features, and primary FAQ above.
GPT (GUID Partition Table) pairs naturally with UEFI machines built in the last decade. It supports large disks and many partitions. MBR (Master Boot Record) is the older scheme; it is still relevant when you must boot the same stick on very old systems that lack UEFI or when firmware is finicky about hybrid setups.
If your target fleet is mostly UEFI laptops and desktops from roughly 2012 onward, GPT is usually the default. If you still maintain a legacy lab or industrial PC with only BIOS, confirm whether those machines can boot USB at all—some need updated firmware or a different USB port.
The large partition that holds your ISOs behaves like normal storage. exFAT avoids the 4 GiB per-file limit of FAT32 and is widely readable on Windows and many Linux desktops—useful for single large Windows images. NTFS is native to Windows and handles large files well; some Linux live environments mount NTFS read/write reliably, others are read-only unless you add drivers. FAT32 maximizes compatibility with older firmware but breaks when any single file exceeds 4 GiB.
When in doubt, check the Ventoy documentation for your release: supported filesystems and default behaviour can shift between versions.
Debian-family installers often probe firmware and disks early; if an ISO fails only in Ventoy, try the distro’s “safe graphics” or “compatibility” boot option from the menu. Rolling releases such as Arch ship frequent kernel bumps—pair them with a current Ventoy build. Ubuntu and Fedora sometimes change their live session layout between LTS and interim releases; always verify checksums after download.
Specialized security or forensics distros may assume read-only media or expect specific partition labels. Read that distro’s Ventoy notes if boot stalls at initramfs.
Microsoft’s consumer media is large; ensure your Ventoy data partition’s filesystem accepts the file size. Windows Setup still asks where to install—double-check you are targeting the internal NVMe or SSD, not the Ventoy USB. Feature updates and new builds refresh the installer UI slightly; screenshots you see online may not match pixel-for-pixel.
TPM and Secure Boot requirements for Windows 11 are enforced by Setup, not by Ventoy. If Setup refuses to continue, resolve firmware settings on the target PC first.
Ventoy only organizes boot entries; the installers you launch are third-party software with full disk access. Develop a habit: note the capacity and model name of your internal drive before you start. Disconnect secondary drives when performing risky partitioning if the machine allows it. On laptops with a single drive, read every confirmation dialog twice.
Treat “Erase disk” and “Format” as irreversible. When uncertain, stop and photograph the partition map.
USB 2.0 flash drives work for small Linux images but feel slow when copying multi-gigabyte ISOs. USB 3.x drives and quality controllers reduce wait time when refreshing your library. External SSDs in USB enclosures can outperform spinning disks and survive travel better than cheap thumb drives—useful for consultants who rebuild sticks weekly.
Avoid hubs that under-power devices during install operations; a dropped link mid-write can corrupt files on the stick.
Many users copy ISOs to a backup folder on another disk, upgrade Ventoy in place per official instructions, then copy ISOs back. In-place upgrade paths depend on version—read the release notes. After upgrading, smoke-test one Linux live image and one Windows installer before you rely on the stick for travel.
Schools can standardize one approved Ventoy image per cart of laptops, swapping only the ISO folder each semester. Repair shops keep diagnostic Linux, memory testers, and vendor-specific recovery images on one high-quality drive. Field technicians benefit from a rugged enclosure and a printed checksum list taped inside the toolkit—offline verification when cellular coverage fails.
Download Ventoy only from SourceForge, Gitee, or links published on ventoy.net. Compare SHA-256 hashes after every download. For ISOs, verify against the distributor’s published digest—many projects sign releases with GPG as an additional layer.
If a mirror looks “too fast” to be true or serves executables over plain HTTP on unfamiliar domains, abort and retry from an official mirror.
Menu load time grows with the number and depth of scanned folders—organize ISOs into clear top-level folders if you maintain hundreds of files. Extremely large images stress both USB bandwidth and firmware USB stacks; patience during first boot is normal.
Corporate networks sometimes block Windows Update during imaging. Keep vendor-specific network or storage drivers on the Ventoy partition as separate ISOs or folders, but never mix unsigned driver bundles from untrusted forums with production machines.
When a laptop will not boot Windows, a live Linux ISO from Ventoy can mount volumes read-only for inspection—avoid writes until you understand BitLocker status. Forensics-oriented distros assume legal authorization; use them only within policy.
| Approach | Strength | Typical trade-off |
|---|---|---|
| Ventoy | Drop-in ISO/WIM files, frequent updates | Some exotic images need per-entry tweaks |
| Single-image tools (e.g. Rufus) | Simple, one job at a time | Reflash for every image swap |
| Grub-only custom USB | Fine-grained control | Higher manual maintenance |
Comparisons are illustrative; tool features change over time.
Business lines often ship with “boot guard” or custom firmware policies. IT departments may whitelist only certain boot loaders—coordinate with your administrator before using Ventoy on corporate hardware. Consumer lines usually offer a one-time boot key but hide it behind “advanced startup” flows in Windows.
Hypervisors can boot from a physical USB passed through to the VM—useful for quick validation without rebooting metal. USB passthrough quirks vary: assign the whole stick to the VM, not a single partition, unless the docs say otherwise.
Teams sometimes script copying ISOs from a network share to the Ventoy partition overnight. Use robust copy tools that verify file size after transfer, and log failures—silent partial copies cause mysterious boot errors.
The Ventoy installer destroys data on the target USB. Anything not backed up elsewhere is gone. For sticks that also held personal files, sync to cloud or a second drive first.
Ventoy exposes ISO contents; unlocking encrypted volumes is still the job of the operating system you boot. If you need to rescue BitLocker-protected disks, have recovery keys available before you boot a live environment.
Some ARM laptops use UEFI with ACPI or DeviceTree—compatibility with generic x86 ISOs is impossible. Always download ARM-specific installer images for ARM hardware. Ventoy’s role is unchanged: it routes boot to the image you select, but the image must match the CPU architecture.
Old systems may cap bootable USB sizes or require ZIP-drives-style tricks. If BIOS offers only “USB-FDD” versus “USB-HDD,” experiment once with documentation in hand—mis-clicks here waste hours.
Post firmware version, Ventoy version, partition style, and the exact ISO filename plus checksum status. Screenshots of the Ventoy menu help; blurry photos of unrelated errors do not. Search before opening duplicate threads.
Releases often call out specific ISO families, Secure Boot changes, or filesystem fixes. Skim the entire notes—not only the headline feature—before you blame user error for a regression that was already fixed upstream.
Release assets on SourceForge, Gitee, and other official mirrors may propagate slowly after a publish. If hashes do not match, you might have caught a partial download—clear browser cache, retry, or switch mirrors before filing a bug.
Ventoy advertises support for multiple payload types. Each has caveats: VHD scenarios may assume Hyper-V or specific boot loaders; EFI files must match firmware architecture. Validate against the official compatibility tables for your exact Ventoy version.
Community themes can make menus friendlier for non-technical users—label entries clearly (“Windows 11 24H2”, “MemTest”, “Ubuntu 24.04”). After theme updates, confirm text remains readable on both UEFI and legacy boot paths if you support both.
Allocate enough space for package updates on persistent live systems—small persistence files fill quickly. Periodically prune package caches from the persistent volume using the live environment’s tools.
Pair this page with the official plugin list, tested ISO list, and news archive. Translate forum advice cautiously—hardware from 2014 and 2024 behaves differently even when symptoms sound identical.
This extended block ends here; scroll up for downloads, installation steps, and primary troubleshooting.