The copy finished, the file is on the USB - but the Ventoy boot menu shows nothing, or shows your other ISOs and not this one. Ventoy is picky about exactly three things: where the file sits, what type it is, and whether the copy truly completed. Check them in this order.
By Technical AnshuVentoy USB Guide7 minute read
The video demonstrates the file detection checklist on a real drive - including the partition mistake almost everyone makes once
A Ventoy drive has two partitions, and only one of them is scanned for bootable files. On top of that, Ventoy's menu is not a file explorer - it lists only image files it knows how to boot, and it says nothing about the rest. So a "missing" ISO is almost never a broken drive. It is a file in the wrong partition, a file of the wrong type, or a copy that never fully arrived. Work through the three checks below in order - most people find their problem in the first one.
The Ventoy drive in File Explorer - where your file actually landed
Ventoy (E:) - big data partitionwindows11.iso - listed in the menu
VTOYEFI - 32 MB boot partitionnever copy ISOs here
ubuntu.zip on E:archive - never listed
install.esd on E:ESD image - never listed
Only real image files on the big Ventoy data partition appear in the boot menu - archives and ESD files are ignored silently
1
Check the Partition - the File Must Be on the Big Ventoy Partition
Plug the drive into Windows and open File Explorer
Find the large partition labelled Ventoy - this is where all your ISOs from the boot menu live
If your new file is sitting on the tiny VTOYEFI partition (about 32 MB), move it to the Ventoy partition - Ventoy never scans VTOYEFI for images
Files inside normal folders on the data partition are fine - Ventoy scans subfolders too - but while testing, place the file in the root of the partition so you can rule folders out
2
Check the File Type - Only Real Image Files Are Listed
Ventoy's menu lists exactly these types: .iso, .wim, .img, .vhd, .vhdx and .efi. Anything else is invisible in the menu, including:
Archives - .zip, .rar, .7z: many downloads arrive packed; extract the ISO out first, then copy the ISO
Compressed images - .iso.gz and similar: decompress before copying
Windows ESD files - .esd: Ventoy cannot boot these at all; they must be converted to ISO/WIM with proper tools first
Turn on file extensions in File Explorer (View - File name extensions) so you can see what the file really is - a file named setup.iso.zip is still a ZIP
3
Check the Copy Itself - Size Limits and Interrupted Copies
The 4 GB trap: a file larger than 4 GB cannot exist on a FAT32 partition. If your data partition was reformatted to FAT32 at some point, big ISOs fail to copy - Ventoy's default exFAT format has no such limit
Interrupted copy: if the USB was pulled out while copying, the file can look present but be incomplete. Delete it, copy it again, and use Safely Remove Hardware before unplugging
Compare sizes: the copied file's size must match the downloaded original exactly, byte for byte (right-click - Properties)
As a pure test, rename the file to a short simple name like test.iso - a handful of firmwares and old Ventoy versions stumble on very long paths or unusual characters
4
Still Missing - Update Ventoy and Test on the PC
Run Ventoy2Disk.exe and use Update to bring the drive to the latest version - new image formats and new releases are recognised by new Ventoy versions first
Boot the drive and read the menu again - also scroll down; with many files the list continues below the visible area
If one specific file still refuses to list while others do, re-download that file from the publisher and verify its SHA-256 checksum - a corrupt header makes Ventoy skip the file entirely
If the file now lists but stops or errors while booting, that is a different problem with a different fix list - see the "ISO shows but fails to boot" guide in this series.
Watch the Detection Checklist in the Video
See the two Ventoy partitions side by side and which files the boot menu lists - and which it silently ignores.
Yes. Ventoy scans subfolders on the data partition and lists images with their folder path in the menu. Keeping one folder per operating system is a perfectly good way to organise a large drive.
Why is my Windows install.esd file not showing in Ventoy?
Ventoy does not support the ESD format at all - it only boots ISO, WIM, IMG, VHD, VHDX and EFI images. An ESD must first be converted into an ISO or WIM using proper Windows imaging tools; the raw ESD will never appear in the menu.
The menu shows some ISOs but not the one I just copied. The file is definitely an ISO. What else can it be?
Most likely the copy did not finish cleanly, or the file is on the small VTOYEFI partition instead of the big Ventoy partition. Compare the file size with the original download, move it to the data partition root as a test, and safely eject before testing again.
This guide is based on the Ventoy Complete Guide video by Technical Anshu - Update, Secure Boot and File Detection Fix - Stuck on a step? Ask in the video comments, help is always there.