Why Windows 11’s New CLI Removes the 32 GB FAT32 Limit and What It Means
Microsoft’s latest Windows 11 preview lifts the long‑standing 32 GB FAT32 partition size cap to 2 TB for command‑line formatting, revealing the historic origins of the original limit and its impact on modern usage.
Microsoft announced on its official blog that the newest Windows 11 preview removes the 32 GB size restriction on FAT32 partitions when using the format command, allowing partitions up to 2 TB.
Important note: this change applies only to the command‑line interface; the graphical formatting dialog still enforces the 32 GB limit.
The original 32 GB limit was set roughly 30 years ago by Microsoft engineers as a quick workaround. Dave Plummer, a senior engineer who contributed the Task Manager, Windows Pinball, and native ZIP support, explained that the limit stemmed from an intuitive decision on cluster size, which unintentionally capped FAT32 volumes at 32 GB.
Plummer recounted how, in 1994, he and his team migrated massive codebases from Windows 95 to Windows NT, prompting a redesign of the formatting dialog. Using VC++ 2.0’s resource editor, they built a simple vertical‑list UI to let users select options in a logical order. The design was intended as a temporary solution, not a polished interface.
Surprisingly, that “temporary” UI persisted for three decades, remaining unchanged in the latest Windows 11 builds. Plummer reflected on the longevity of such shortcuts, warning developers to be cautious when labeling solutions as “temporary.”
While the CLI now supports up to 2 TB FAT32 partitions, users who rely on the GUI must still adhere to the 32 GB ceiling until the graphical tool is updated.
Liangxu Linux
Liangxu, a self‑taught IT professional now working as a Linux development engineer at a Fortune 500 multinational, shares extensive Linux knowledge—fundamentals, applications, tools, plus Git, databases, Raspberry Pi, etc. (Reply “Linux” to receive essential resources.)
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
