Restoring the space, then watching it vanish again after one bootable use, feels exactly like a broken drive. It is doing precisely what it was told: nearly every bootable write replaces the entire partition map with the image's own small map.
The comments under every capacity-restore video carry the same sequel: 'it worked, then I made it bootable and it shrank again — is my drive fake?' Almost never. The restore and the shrink are two different tools redrawing the same map in turn. Understanding the cycle takes the fear out of it — and points at the two methods that end the cycle for good.
An ISO file is not a folder of files — it is a sector-by-sector photograph of an entire small disk, partition table included, sized for the disc or image it came from. Writing it in image (DD) mode stamps that photograph onto your drive, whatever the drive's real size. A 14 GB image therefore leaves a 14 GB map on a 64 GB drive, every single time, by design. The leftover space is not damaged or hidden by malice — the photograph simply does not mention it.
Writers like Rufus offer two modes, and the choice decides your capacity afterwards. ISO mode extracts the image's files onto a partition the tool formats — typically spanning the whole drive, so nothing goes missing. DD mode clones the image exactly, partition table and all — the guaranteed shrink. DD mode exists because some images only boot correctly as exact clones. If you pick DD, accept the shrink as part of the deal, or restore the drive afterwards with the usual clean.
Ventoy takes the opposite approach: it installs its bootloader once, reserves a small EFI partition, and leaves the rest of the drive as one large exFAT partition. You then copy ISO files onto it as ordinary files — no image is ever stamped over the map, so the capacity survives every use, and one drive can carry many bootable images at once. For anyone who makes bootable drives weekly, this is the honest end of the restore-after-every-use routine.
clean plus a fresh partition takes about a minute; many technicians treat it as the standard last step after bootable dutyWhat does not help: formatting the small partition repeatedly. Format lives inside the map; only redrawing the map changes the size.
Some live-USB creators add a persistent storage partition so the live system can save files between boots. That partition is deliberate and useful — but it is still extra layout on the map, and Windows will still only show the pieces it can read. The drive has not shrunk by accident here either; it is partitioned on purpose, and the same clean restores it when the live drive retires.
Watch the restore once in the video — then choose the method that means you only ever do it once.
▶️ Watch Full VideoNo — there is no setting for it, because the shrink is not something Windows does. It is the writing method: an image clone carries its own partition table. Choose ISO mode or Ventoy to avoid the clone, or restore the map afterwards.
Almost certainly they made it bootable, or plugged it into a device that repartitioned it (some set-top boxes and TVs do). Open Disk Management and read the map — leftover boot partitions tell the story plainly, no malware hunt required.
Ventoy boots a very wide range of images as plain files, and it is the daily tool of many technicians. A small number of exotic images still prefer an exact image write. Keep the dedicated-drive option for those, and Ventoy for everything else.