Symlinks and junctions on Windows

What you will achieve

Create directory symlinks, junctions, and hard links on Windows for redirecting folders or deduplicating paths — knowing which type to use.

1) Symlink vs junction vs hard link

1. Directory symlink — points to another path (local or UNC); can cross volumes; needs admin or Developer Mode.
2. Junction — directory link to local absolute path only; works without Developer Mode for admins via mklink /J.
3. Hard link — alternate name for the same file on one volume; both names share data.

2) Enable symlink creation without admin (optional)

1. Settings → System → For developers → turn on Developer Mode.
2. Standard users can then create symlinks in some contexts — still use carefully.

3) Create links with mklink

Admin Command Prompt:

mklink /D "C:\Users\you\Documents\Projects" "D:\Dev\Projects"
mklink /J "C:\OldPath" "D:\NewPath"
mklink "C:\file-link.txt" "C:\original.txt"

4) PowerShell New-Item alternative

New-Item -ItemType SymbolicLink -Path "C:\Link" -Target "D:\Target"
New-Item -ItemType Junction -Path "C:\Junction" -Target "D:\Target"

5) Identify link type

dir /AL
fsutil reparsepoint query "C:\Path\To\Link"

6) App compatibility

1. Some installers break when parent folder is a junction — test before redirecting Program Files or user profile roots.

7) Directory junction to UNC

1. Junctions cannot target UNC paths — use directory symlinks with Developer Mode or admin for network redirect scenarios.

8) Move Users folder (not recommended)

1. Some guides junction entire Users tree to D: — breaks Windows upgrades. Prefer Known Folder Move via OneDrive or relocate specific large folders only.

9) mklink requires elevation

Without Developer Mode, standard users get “You do not have sufficient privilege” — expected behaviour.

Verification checklist

Dir /AL lists junctions — audit quarterly on dev machines for forgotten redirects before disk migrations.

1. Reboot once after changes that affect services, drivers, or firmware.
2. Confirm the original problem is resolved under normal daily use, not only immediately after the fix.
3. Note date, Windows version (Settings → System → About), and what changed in your personal runbook for next time.

Quick reference paths

• mklink
• fsutil reparsepoint query
• Settings → For developers
• Admin tools: press Win + X for Terminal (Admin), Device Manager, and Computer Management.

Git for Windows respects symlinks when core.symlinks=true — use symlinks in repos only when all team members run Windows with Developer Mode or admin rights.

Related guides

• Map a network drive
• NTFS permissions basics