Disk Management: volumes, partitions, drive letters and the things that go missing

Why this matters

Disk Management is where a disk goes from being hardware to being somewhere you can put files, and it is also where the most permanent mistakes in this exam are available. There is no undo. A partition deleted here is a partition deleted, and the tool asks once.

The examinable content is the order of operations and the vocabulary — what initialising does that formatting does not, why a disk can be present and invisible, and why a shrink stops well short of the free space available. Every one of those shows up as a scenario, and every one of them has a specific answer rather than a general one.

The lesson

Initialising, partitioning and formatting, and the order they happen in

Three things happen to a new disk, in this order, and confusing them is the most common source of "the disk isn't working".

1. Initialise. Write a partition table so the disk can hold partitions at all. This is where you choose MBR or GPT. A new disk that appears in Disk Management as "Not Initialized" has had none of this done, and it will not appear in the file explorer at all.
2. Partition. Divide the disk into one or more volumes. A disk with no partitions shows as "Unallocated" — it is initialised, and there is nowhere to put files yet.
3. Format. Write a file system into a partition so it can hold files. A partition with no file system shows as "RAW", and Windows will offer to format it. It is a volume with no structure inside it.

The states map directly onto the symptoms, which is what makes this worth learning as a sequence:

• Not in Disk Management at all → hardware, cabling, or the controller.
• Present but "Not Initialized" → step 1.
• Initialised but "Unallocated" → step 2.
• Partitioned but "RAW" → step 3, unless it used to work, in which case formatting destroys the data and recovery comes first.

That last caveat matters. A volume that was NTFS yesterday and is RAW today has a damaged file system, and the offer to format it is the worst available option.

Basic against dynamic disks, and why most machines should stay basic

Windows disks are either basic or dynamic, and the short version is that basic is right and dynamic is a legacy answer to a problem solved better elsewhere.

Basic disks use the ordinary partition table. Each volume lives in one contiguous area of one disk. This is what everything expects.

Dynamic disks use a separate database to describe volumes and can do things basic disks cannot: spanning a volume across disks, striping, mirroring, and RAID-5 in software.

Why most machines should stay basic:

• The dynamic layout is a Microsoft-specific structure. Recovery tools, other operating systems and disk utilities understand it poorly or not at all.
• Converting basic to dynamic is a one-way trip in practice: converting back requires deleting every volume on the disk.
• The features it offers are better served by Storage Spaces, by hardware RAID, or by not doing them on a workstation at all.

The examinable point is the conversion's asymmetry — basic to dynamic is offered casually in the interface and going back is destructive — and that seeing "Dynamic" on a machine you are troubleshooting is worth noticing, because it narrows what recovery tools will work.

Extending, shrinking and the unmovable file that stops a shrink

Extending and shrinking are the two operations people reach for most, and one of them has a famous limitation.

Extending a volume needs unallocated space immediately after it on the same disk. Free space before it, or on another disk, does not help. This is why deleting a recovery partition that sits after the system volume is such a common temptation — and it is also how machines end up unable to run a feature update.

Shrinking reduces a volume and creates unallocated space after it. The limitation is that Windows will only shrink up to the last unmovable file. A volume with 400 GB free may offer to shrink by 20 GB, because a page file, a hibernation file, a shadow copy or an unmovable system file sits near the end.

The order that actually works when a shrink stops short:

1. Disable hibernation temporarily.
2. Disable the page file and restart.
3. Delete shadow copies / restore points if they are expendable.
4. Shrink.
5. Turn everything back on.

Each of those releases a specific unmovable file, and the sequence is worth remembering because the tool gives no hint about which one is in the way.

If that still does not free enough, the honest answer is a third-party tool that can move files, or a backup-repartition-restore cycle. Both are legitimate; guessing repeatedly at the shrink dialog is not.

Drive letters, mount points, and a disk that is present but invisible

A drive letter is a label, not a property of the disk, and treating it as a label explains most of the odd behaviour here.

• Changing a letter is instant and mostly harmless, except that applications installed to that letter will stop working, and shortcuts break. Changing the letter of the system volume is not offered, for good reason.
• Letters can be omitted entirely. A volume with no letter is mounted and usable but invisible in the file explorer, which is exactly how recovery and EFI partitions stay out of the way.
• Mount points attach a volume to an empty folder on another volume instead of to a letter. This is how you add space to a path that must not change, and it is the answer when a scenario says a full folder cannot be moved.

A disk that is present but invisible has a short list of causes:

• It has no drive letter assigned.
• It is unallocated, RAW, or uninitialised — the previous sections' states.
• It is offline, which Disk Management shows explicitly and fixes with one right-click. Disks attached to a machine that has been imaged, or moved from another machine, commonly arrive offline.
• Its file system is one Windows does not read — an ext4 disk from a Linux machine is perfectly healthy and perfectly invisible, and offering to format it is the wrong answer.

That last case is worth flagging as a professional judgement: a disk Windows does not understand is not a broken disk, and the right response is to read it on a system that does.

Reading the layout before changing it, which is the whole safety procedure

There is a safety procedure for this tool and it is one sentence: identify every volume before you change any of them.

Concretely, before touching anything:

• Note the disk numbers and sizes, and match them to the physical hardware. Two identical disks in a machine are indistinguishable in the tool except by number and content.
• Note which volume is marked System, Boot, and Active. Deleting the System partition on a UEFI machine — the small EFI one — leaves an intact operating system that cannot start.
• Note which volume holds data you cannot replace, and confirm it is backed up before anything else happens.
• Take a screenshot. It takes three seconds and it is the only record of what the layout was.

The reason to insist on this is that Disk Management's mistakes are silent and immediate. There is no confirmation beyond a single dialog, no recycle bin, and no undo. A partition deleted from the wrong disk is gone, and the recovery options from that point are specialist and expensive.

The same procedure generalises to everything in the operational procedures objective at the end of this course: record the current state, make one change, confirm the result. Disk Management is simply the place where forgetting it is most expensive.