You plug in one pen drive and Windows greets you with two drive letters and a few hundred megabytes you cannot use. A full Linux install writes a small city of partitions — boot, system, swap, data — and Windows shows you every piece it can read.
Of all the ways a shrunken drive presents, the multi-letter mess confuses people most, because the pieces look like separate drives and one of them seems to work fine. It is one drive with a crowded map. This page names each piece, explains why formatting the wrong layer never merges them, and gives the cleanup in its shortest honest form.
A full operating-system install onto a pen drive builds the same layout it would on an internal disk. The small boot (EFI) partition — a few hundred megabytes of FAT32 — holds the files the firmware needs to start. The system partition holds the OS itself, in Linux's ext4 format, which Windows cannot read: Disk Management shows it as a healthy block with no letter and no option to open it. Many installs add a swap partition too. Add whatever space the installer left over, and one drive arrives in Windows as two letters, a mystery block, and a large invisible remainder.
Each letter is one partition, and Format works strictly inside the partition you clicked. Formatting E: a hundred times leaves F:, the ext4 block, and the unallocated space exactly as they were. This is the single most common reason people conclude the drive is 'still broken' after trying hard — they were cleaning one room of a four-room house. Merging requires deleting partitions, not formatting them.
The cleanup is the graphical route, applied to every piece on the row:
The Disk Management page in this set walks this route with pictures; the short version is: all pieces deleted, one volume created. Explorer then shows exactly one drive.
EFI and other protected partitions sometimes grey out their Delete option in Disk Management — Windows guards them against casual edits even on removable drives. That is the cue for the one-shot tool: DiskPart's clean removes every partition on the selected disk in a single command, protected pieces included. Use the DiskPart page in this set for that sequence — it carries the select-the-right-disk checks that command must never skip.
After the merge, give the drive a clear label (its name in Explorer) and confirm only one letter appears. A named drive is easy to recognise next time it plugs in — and if a second letter ever reappears, you will know immediately that something repartitioned it, because you have seen the tidy state. That recognition is half of drive hygiene.
Watch the video to see the drive's real layout exposed — the mess reads clearly once you have seen it once.
▶️ Watch Full VideoYou can — the readable pieces genuinely work, and their sizes add up. What you lose is the invisible remainder: the ext4 block and any unallocated space stay unusable by Windows. Merging is tidiness plus full capacity; using both letters is a valid stopgap, not a repair.
Because it is written in a format Windows does not read (ext4, from the Linux install) or it is a protected EFI partition. Windows shows such blocks in Disk Management for completeness but offers no way to open or format them from Explorer.
Some TVs and older players are picky: they may want a single FAT32 partition in the older MBR style rather than exFAT. If the drive's job is serving that device, format it FAT32 after the merge and keep files under 4 GB — compatibility beats capacity for that use.