Guided path: Storage path
Step 5 of 5
Reparse points & symlinks
Junctions, symlinks, and filter-driver namespaces that redirect paths.
Official Microsoft docs
Closest official references related to this topic on Microsoft Learn.
Why it matters
Cloud sync, deduplication, and directory redirection rely on reparse points. Misunderstanding them breaks path forensics.
Mental model
A reparse point tags a directory or file so the I/O manager invokes a filter to interpret the path.
How it works
- 1The file system stores a reparse tag and optional data on a file object.
- 2Opens traverse the tag; a filter or the file system resolves the target.
- 3Junctions, symlinks, and OneDrive-style placeholders all use this mechanism differently.
Key terms
- Reparse point
- A file system object marked for special interpretation.
- Mount point
- A junction that redirects a directory to another volume path.
dir shows <SYMLINK> or <JUNCTION>
These are reparse-backed redirects. The real content may live on another path or volume.
Common misconception
Symlinks and hard links are not the same. Reparse-backed symlinks differ from hard link directory entries.
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.
Related topic
expert
Cache Manager
How Windows speeds file access by coordinating cached file data with memory.
Natural next depth in this branch
intermediate
Drivers & device stacks
Function, filter, bus, class, and miniport drivers in layered request handling.
Related topic