Every failed extend starts the same way: clicking before reading. The Disk Management strip is a physical map of your disk — learn to read it and the right route chooses itself.
Technicians do not start partition work by opening a tool. They start by reading the map — the strip of blocks Disk Management draws for each disk. Those blocks sit in their true physical order, and that order, plus a few size numbers, decides whether your extend takes five minutes or needs a different plan entirely. This page is the survey every other page in this series assumes you have done.
Disk Management's lower pane draws each disk as a horizontal strip, and the blocks on it are not a list — they are a to-scale map in physical order. The block on the far left starts the disk; the block on the far right ends it. When you plan an extend, this map is the entire decision: C can only swallow the block drawn immediately against its right edge, and only if that block says Unallocated. Everything else — shrinking, moving, deleting — is just rearranging the map until the right block sits in the right place.
Walk the strip for your system disk and identify each block out loud:
For a text version of the same map, open an elevated command prompt and run diskpart, then list disk and list volume. The order matches the drawing — and writing down the volume numbers now prevents the classic wrong-volume mistake later, when commands ask you to select one by number.
Many PCs have two disks: a small fast SSD holding Windows and a large HDD holding data. The strips stack vertically — Disk 0, Disk 1 — and it is easy to read the wrong one and plan around space that belongs to another disk entirely. Extending happens strictly inside one disk. C on Disk 0 can only consume unallocated space drawn on the Disk 0 strip. The generous free space on Disk 1 cannot join C; it can only take over storage duty — games, media, documents — and relieve C that way. Both are legitimate fixes, but they are different fixes, and the map tells you which one you actually have.
Finish the survey with numbers, because they choose the route for you. How much space does C realistically need — most home and office PCs breathe again with 30 to 60 GB added. Where can that much come from: existing unallocated space, a D drive with that much genuinely spare, or nowhere on this disk at all? If the answer is nowhere, extending is the wrong project and the honest project is cleanup plus moving libraries to another disk. Five minutes with the map and a calculator beats an afternoon of greyed-out buttons — every route in this series starts from this same survey.
Watch how the layout is read and the extend is planned on a real machine in the full video.
▶️ Watch Full VideoRight-click the Start button and choose Disk Management, or press Windows key + R, type diskmgmt.msc and press Enter. The lower half of the window shows the graphical map — one strip per physical disk, blocks drawn in their real left-to-right order.
Then nothing can be extended yet — unallocated space has to be created first, usually by shrinking a data partition like D. Be aware that shrinking D places the freed space at the far end of D, not beside C, which is why the shrink case in this series explains the two-step reality honestly.
Having no letter is normal — Windows hides it deliberately. Do not ignore it in your planning though: if it sits between C and your free space it blocks the built-in extend completely, and it holds the recovery environment, so removing or moving it deserves the careful treatment in its own case.