Creating symbolic links (symlinks) in Windows normally requires administrator privileges, but there are ways to create them without admin access. This guide shows you how to create symlinks using built-in Windows features and a few workarounds, so you can link files and folders even on a restricted account.
What You’ll Need
- A Windows PC (Windows 10 or 11 recommended)
- A user account without administrator privileges (the method works on standard accounts)
- Access to Command Prompt or PowerShell (you can open these without admin rights)
- Developer Mode enabled (optional but recommended for the easiest method)
Step-by-Step
- Enable Developer Mode (if possible): Go to Settings > Privacy & Security > For developers (Windows 11) or Settings > Update & Security > For developers (Windows 10). Toggle on Developer Mode. If you don’t have permission to change this setting, skip to step 2—there are alternatives.
- Open Command Prompt or PowerShell without admin: Press
Win, typecmdorpowershell, and press Enter. Do not select “Run as administrator.” - Try the standard symlink command: Use the
mklinkcommand (in Command Prompt) or theNew-Itemcmdlet (in PowerShell). For example, to create a symbolic link to a file:mklink C:\path\to\link.txt C:\path\to\target.txt
Or for a directory:
mklink /D C:\path\to\linkfolder C:\path\to\targetfolder
If this works, you’re done. If you get an error about insufficient privileges, proceed to the next step.
- Use the “symlink” PowerShell cmdlet with a workaround: In PowerShell, you can try:
New-Item -ItemType SymbolicLink -Path "C:\path\to\link" -Target "C:\path\to\target"
If that fails, try using the
cmd /c mklinkfrom PowerShell—it sometimes bypasses the admin check if Developer Mode is on. - Create a hard link instead (for files only): Hard links don’t require admin rights. In Command Prompt, use:
mklink /H C:\path\to\link.txt C:\path\to\target.txt
Hard links work only for files on the same volume, and they behave like the same file—changes to one reflect in the other.
- Use a directory junction (for folders): Junctions are similar to symlinks but don’t need admin rights. In Command Prompt:
mklink /J C:\path\to\linkfolder C:\path\to\targetfolder
Junctions work for local directories only, not for files or network paths.
- If all else fails, use a symbolic link via a script: Some users have success by running a small script that calls
mklinkfrom a batch file, but this still requires the same privileges. The most reliable workaround is to use junctions or hard links.
Common Mistakes
- Using the wrong syntax: Forgetting the
/Dflag for directories, or mixing up source and target paths. - Not using full paths: Relative paths can cause errors. Always use absolute paths like
C:\Users\Name\Documents\link. - Assuming Developer Mode is enough: Developer Mode helps, but on some corporate-managed PCs, group policy may still block symlink creation.
- Using symlinks for network drives: Symlinks to UNC paths require admin rights; use a mapped drive letter instead.
- Forgetting that hard links only work on the same volume: If target and link are on different drives, hard links fail.
Tips
- Prefer junctions for folders: Junctions are the most reliable no-admin option for directories.
- Use hard links for files: They’re simple, don’t need admin, and work well for syncing files.
- Check if symlinks are already allowed: Some standard accounts on Windows 10/11 can create symlinks if Developer Mode is on—test before trying workarounds.
- Run as administrator once: If you have a one-time chance to run an admin command, enable Developer Mode or grant yourself the “Create symbolic links” right via Local Security Policy (if permitted).
- Use third-party tools cautiously: Tools like Link Shell Extension can create links, but they still require the same underlying privileges.
Troubleshooting
“You do not have sufficient privilege” error: This means your account lacks the SeCreateSymbolicLinkPrivilege. Try enabling Developer Mode (if possible), or switch to a junction or hard link.
Junction creation fails: Ensure the target path exists and is a local directory. Junctions cannot point to files or network locations.
Hard link fails with “Access is denied”: Check that the target file exists and that you have write permission to the destination folder. Also, the target and link must be on the same NTFS volume.
Symlink works but apps don’t follow it: Some older applications don’t support symlinks. Try a junction or hard link instead.
PowerShell says “The term ‘New-Item’ is not recognized”: This is rare; make sure you’re in PowerShell, not Command Prompt.
Frequently Asked Questions
Can I create a symbolic link without admin if Developer Mode is off?
Generally no, but you can use junctions or hard links, which don’t require admin rights.
What’s the difference between a symlink and a junction?
Symlinks can point to files or directories, local or remote. Junctions can only point to local directories, but they don’t need admin rights.
Can I create a symlink to a network drive without admin?
No, that requires admin privileges. Use a mapped drive letter instead.
Will hard links work for folders?
No, hard links only work for files. For folders, use a junction.
Why does mklink say “You do not have sufficient privilege” even though I’m an admin?
Your account might not have the SeCreateSymbolicLinkPrivilege, or UAC is blocking it. Run Command Prompt as administrator or enable Developer Mode.
Can I create a symlink using PowerShell without admin?
Only if Developer Mode is enabled and your account has the privilege. Otherwise, use New-Item with the SymbolicLink type—it will fail without admin.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Disable Autocorrect on iPhone or iPad: Quick Guide
- Custom Keyboard Shortcuts on Windows 11 & macOS
- Restore Windows 11 Display Scaling to Recommended
- Semiconductor Cycle: How Investors Track It0.0
- Microsoft Store Error 0x80073d12: Fixes That Work
- View Notification Count on iPhone: Full Guide