Windows Hard Link [extra Quality] Guide

A hard link doesn't point to a path —it points directly to the raw data on disk. That data has no location except "wherever Windows put it." Junction points are volume-mounted directory links (only for folders, only local drives). They behave like symlinks for folders but have fewer features. Hard links don't work on folders at all in Windows (NTFS supports them, but Windows restricts creation for safety). Creating Hard Links on Windows Windows provides two built-in ways: mklink (Command Prompt) and New-Item (PowerShell). Using Command Prompt (Run as Administrator for some operations, but not strictly required for files) mklink /H LinkName TargetFile Example:

This isn't a shortcut, and it's not a copy. It's something far more powerful—and far more confusing if you don't understand how it works.

fsutil hardlink list "file.txt" Or with PowerShell: windows hard link

ni link.txt -ItemType HardLink -Target original.txt To confirm you've created a hard link (and not a copy or symlink), check the link count :

copy file.txt file_backup.txt # Wrong: uses 2x space mklink /H file_backup.txt file.txt # Right: zero extra space This is not a true snapshot. Changes to file.txt will appear in file_backup.txt because they're the same data. Use this only when you want simultaneous updates across paths, not historical versions. 3. Compatibility Layers for Legacy Software Some old software expects configuration files in hardcoded paths. Instead of copying (and then desyncing), use hard links: A hard link doesn't point to a path

But Windows has a secret: the . With a hard link, a single file can appear in multiple folders simultaneously, without duplicating any data. Change one, and the others update instantly. Delete one, and the others remain untouched.

(Get-Item "link.txt").LinkType # Output: HardLink In File Explorer, hard links appear as normal files—there's no special icon or overlay. This is both a feature (no clutter) and a danger (easy to forget they're linked). 1. Deduplication Without Deduplication Features You have the same large ISO file needed in three different project folders. Instead of using 6 GB, create hard links: Hard links don't work on folders at all

Workaround: Use directory junctions or symlinks with mklink /D or mklink /J . Hard links cannot span drives (C:\ to D:). Each volume maintains its own file reference table. For cross-volume needs, use symbolic links. ❌ The Deletion Trap This is the most common hard link mistake: