Disks, partitions, and volumes
How physical or virtual disk space becomes manageable logical storage.
Guided paths in this branch
Follow a short sequence step by step. Each path links to the first topic; use Read next on each page to continue.
Storage path
Volumes, NTFS, cache, and reparse points.
Step 2 of 5 in this path
Official Microsoft docs
Closest official references related to this topic on Microsoft Learn.
Why it matters
This layer explains the difference between a raw disk, a partition, a volume, and the namespace users actually see.
Mental model
A disk is raw capacity; a volume is the logical surface Windows chooses to expose for I/O.
How it works
- 1Disk drivers expose block devices to the storage stack.
- 2Partition and volume layers carve and describe logical storage regions.
- 3Namespaces such as drive letters or volume GUID paths expose those regions to higher layers.
Key terms
- Partition
- A defined region on a disk used to organize storage.
- Volume GUID path
- A stable namespace path Windows can use for a volume independent of drive letters.
Why one disk can expose multiple drive letters
Several logical volumes can share the same physical device while still appearing as separate storage units to apps.
Common misconception
A partition is not automatically the same thing as a volume or file system.
You should read next
Ranked from your current topic, related links, branch depth, and any active guided path.
intermediate
File systems
NTFS and friends translating raw storage into directories, files, and metadata.
Next step in your guided path
expert
Cache Manager
How Windows speeds file access by coordinating cached file data with memory.
Natural next depth in this branch
beginner
Startup & shutdown
How Windows goes from firmware to an interactive session, and how it tears systems down safely.
Related topic