Two technicians can carry the same ISOs and have completely different days - the difference is layout. A rescue drive organised by job, on the right filesystem, with persistence set up only where it truly works, is faster and calmer at every breakdown.
Ventoy is forgiving about layout - it boots ISO files from anywhere on the drive - which tempts people into one flat pile of forty files. Forgiveness is not the same as wisdom. This guide covers the three layout decisions that matter: how to folder the drive, which filesystem to run, and what persistence really is - including the honest boundary where persistence stops working.
/Install windows-11.iso, windows-10.iso /Rescue Hirens-BootCD-PE.iso, ubuntu-live.iso /Antivirus rescue-disk.iso /DiskTools clonezilla-live.iso, gparted-live.iso /Docs toolkit-index.txt
Ventoy scans the whole drive, subfolders included, and presents what it finds. So your folder tree is your menu structure. Group by the job you will be doing under pressure: Install for Windows images, Rescue for WinPE and live systems, Antivirus, DiskTools for clone and partition work.
Name files like a human who will read them at 2 a.m.: ubuntu-24-live.iso explains itself; final-v2-NEW.iso does not. Rename files freely - Ventoy displays the file name, and renaming an ISO changes nothing about how it boots.
Ventoy installs its data partition as exFAT by default, and for a rescue drive that default is right: no practical file-size limit, and it reads and writes happily in Windows for quick ISO swaps.
The trap is FAT32: it cannot hold any single file larger than 4 GB, and many Windows and WinPE images are bigger than that - the copy simply fails near the end. NTFS also works for the Ventoy partition and suits a Windows-only workshop, but exFAT remains the least-surprise choice for a drive that visits many machines. Whatever you pick, pick it knowing the 4 GB rule exists.
During installation, Ventoy offers to preserve space at the end of the disk. That reserved area can become an ordinary partition of your own - handy when the same physical stick must also carry plain files in a way older devices accept, or when you want a small documents area kept separate from the boot side.
Decide this at install time; it cannot be added later without reinstalling Ventoy. Most rescue sticks do not need it - ISOs and a small index file live happily in the main partition - but technicians who share one big drive between toolkit duty and file-carrying duty use it deliberately.
Live systems normally forget everything at shutdown. Persistence gives a supported live Linux a memory: Ventoy's Persistence plugin points the ISO at a data file on the drive - created with Ventoy's own image-creation tool and declared in ventoy.json - and changes are written into that file:
{ "persistence": [ { "image": "/Rescue/ubuntu-live.iso", "backend": "/persistence.dat" } ] }
Now the honest boundary. Persistence works only with live Linux distributions that support it, configured one image at a time. WinPE environments do not use it at all. A corrupted persistence file can stop that one entry booting, so keep a plain non-persistent entry for the same distro as your guaranteed way in. Persistence is a convenience for your Linux tools' settings - never a place to store a customer's only copy of anything.
The rescue stick gets plugged into infected, failing and untrusted PCs for a living. So it carries tools, not treasure: no personal documents, no password files, no backups that exist nowhere else. Keep a cheap second stick or an external drive for carrying data out of rescues.
And keep one small thing on it that pays for itself constantly: the toolkit-index.txt from the maintenance guide - what is on the drive, which versions, and when each was added.
Watch the video for the full toolkit tour - what goes on the drive and how each part earns its place on a real repair job.
▶️ Watch Full VideoNo. Ventoy finds ISO files in subfolders automatically, several levels deep. The root-only habit is a leftover from older boot tools - folders are fully supported and strongly recommended.
No. Ventoy boots the file whatever it is called, and shows the file name in the menu. Clear names are pure profit - just keep the .iso extension intact.
It is the wrong tool for that job. Rescue disks are meant to be re-downloaded fresh so their definitions are current; a persistent old rescue disk preserves exactly the staleness you are trying to avoid. Persistence belongs to your Linux live tools, if anywhere.