Windows Hard Link -

fsutil hardlink list "file.txt" Or with PowerShell:

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 : windows hard link

fsutil hardlink list "link.txt" Or in PowerShell: fsutil hardlink list "file

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: For cross-volume needs, use symbolic links

In this guide, you'll learn exactly what hard links are, how to create them, when to use them, and the critical pitfalls to avoid. A hard link is an additional directory entry that points directly to the same underlying file data on disk.

echo Hello > original.txt mklink /H link.txt original.txt type link.txt # Output: Hello echo World >> original.txt type link.txt # Output: Hello World /H is the crucial flag—without it, mklink creates a symbolic link by default. New-Item -ItemType HardLink -Path "C:\links\link.txt" -Target "C:\data\original.txt" Or with the shorter alias:

| Feature | Hard Link | Symbolic Link | |---------|-----------|----------------| | Points to | File data (inode) | Pathname (string) | | Survives target deletion | Yes (data still exists) | No (becomes broken) | | Works across volumes | No | Yes | | Works with directories | No (by design) | Yes (with privilege) | | Relative paths | N/A | Yes | | Network paths | No | Yes (UNC paths) |