Windows still asks about this floppy-era setting every time you format a drive

Published Oct 7, 2026, 1:30 PM EDT After a 7-year corporate stint, Tanveer found his love for writing and tech too much to resist. An MBA in Marketing and the owner of a PC building business, he writes on PC hardware, technology, and Windows. When not scouring the web for ideas, he can be found building PCs, watching anime, or playing Smash Karts on his RTX 3080 (sigh). Over four decades, Windows has undergone massive changes, including the underlying kernel. Windows 11 traces its roots back to Windows NT in the early 90s, completely separate from the DOS-based versions that came before. Many underlying features and concepts of Windows NT and 95 are still present in modern-day Windows, and one of them is something people use fairly regularly. Specifically, I'm talking about the drive format utility on Windows 11. Despite Microsoft overhauling several of its flagship OS' aspects for Windows 11, the drive format tool still uses a dialog box with the same UI and options designed back in 1994. A snippet of code meant to be temporary has persisted to this day, along with a setting created in an era of drastically different storage. Windows' drive format utility has remained virtually unchanged since the 90s Sometimes, simplicity is all you need Most of you would be familiar with the drive format utility on Windows. After all, formatting USB drives was fairly common only a few years ago, and it's something that many folks (including yours truly) still rely on when clearing all data on external HDDs and SSDs. Firing up the utility shows a simple UI with a handful of toggles for the format type, disk label, drive capacity, and a couple of other options. You might be surprised to know that this utility looked nearly the same back in 1994, when Microsoft engineer David Plummer created it as a placeholder for Windows NT 4.0. In fact, he also arbitrarily decided on the 32GB partition limit of FAT32, and it stayed that way until Microsoft finally decided to raise this cap up to 2TB earlier this year. But that's a story for another time... Anyway, the drive formatting utility didn't need to be complicated, so Microsoft probably decided it didn't need to be reworked. In the mid-90s, floppy drives and early hard drives were small enough that the operating system only needed a basic table to track which physical parts of the drive were holding a particular file. To manage this, the file system combined physical disk sectors into "clusters" or "allocation units." And the size of these allocation units is the setting Windows still asks you to choose. For the uninitiated, an allocation unit is the smallest unit of storage that the OS can assign to a file. The default size is usually 4096 bytes (4KB), which works for most users and storage drives, but you can change it if that suits your use case. A file that's only a few bytes in size will occupy the full 4KB allocation unit. In a nutshell, smaller allocation units are ideal for millions of tiny files, whereas larger sizes work better for a drive with bigger files to minimize wastage. The underlying logic changed over the years Physical sectors went away, but the communication remained the same As we transitioned from tiny floppy drives to large hard drives with terabytes of storage, the conventional mechanical tracking system had to be replaced. Mapping the exact physical head, cylinder, and sector to parts of a file was no longer efficient on a large drive. So, the industry introduced Logical Block Addressing (LBA) to act as a universal translator. The internal drive controller translates the logical addresses into physical ones whenever Windows accesses data. Your modern SSD does not store data in "sectors," using pages and blocks instead. However, for compatibility with Windows and legacy software, it emulates logical sectors using LBA, typically using 4KB allocation units. When SSDs arrived on the scene, manufacturers simply designed them to work with LBA instead of forcing operating systems to rewrite how they talked to storage drives. Hence, the three-decade-old practice of combining drive sectors into allocation units has persisted to this day, despite NAND flash not using sectors at all. This practice maintains compatibility with modern storage, avoids needless rework at the fundamental disk level, and makes no difference to how people use their drives and PCs. Backwards compatibility often trumps every other consideration Windows' drive format utility is a prime example of how backwards compatibility is more important than design overhaul. A lot of what goes on underneath the Windows UI you use every day traces back to decades-old code and concepts. Modern operating systems might break down if every new version decided to do things differently just for the sake of it. This is why some things are best left unchanged, even across decades of development. Windows 11 Home