Allowing Regular Users to Create Symbolic Links on Windows 10
If you've ever tried to run mklink in a standard Command Prompt only to be met with "You do not have sufficient privilege to perform this operation," you're not alone. By default, Windows requires an elevated (Administrator) token to create symlinks. To bypass this as a regular user, you must either modify the Local Security Policy or enable Developer Mode.
Method 1: The Local Security Policy (Professional/Enterprise)
This is the most "surgical" approach. It grants a specific user or group the SeCreateSymbolicLinkPrivilege without lowering other security barriers. Note: This tool is not available on Windows 10 Home edition.
- Press
Win + R, type secpol.msc, and hit Enter. - Navigate to Local Policies > User Rights Assignment.
- Find the policy named Create symbolic links and double-click it.
- Click Add User or Group... and type the name of the user or group (e.g.,
Users) you want to authorize. - Click OK and restart your computer (a log-off is often not enough to refresh the security token).
Method 2: Developer Mode (All Editions)
Starting with the Windows 10 Creators Update (Version 1703), Microsoft introduced a "Developer Mode" toggle that allows anyone on the machine to create symlinks without elevation. This is the only built-in option for Windows 10 Home users.
How to Enable:
- Open Settings > Update & Security > For developers.
- Toggle Developer Mode to On.
- Accept the warning prompt.
Once enabled, you can run mklink in a standard, non-elevated cmd.exe or use the New-Item -ItemType SymbolicLink command in PowerShell.
3. The "Junction" Alternative (No Setup Required)
If you only need to link folders on the same local drive, you can use a Directory Junction. Junctions do not require any special privileges or Developer Mode.
mklink /J "C:\LinkPath" "C:\TargetPath"
Comparison: Symlinks vs. Junctions
| Feature | Symbolic Link (/D) | Junction (/J) |
|---|---|---|
| Permissions | Requires Admin/Dev Mode | Standard User |
| File Support | Yes | No (Folders only) |
| Network Paths | Yes | No |
| Relative Paths | Yes | No (Absolute only) |
Troubleshooting "Access Denied"
If you have enabled Developer Mode or adjusted the Security Policy and still face errors:
- Check the Path: Ensure the user has "Write" permissions to the folder where the link is being created.
- Quotes: Always wrap paths in double quotes if they contain spaces:
mklink "C:\My Link" "C:\Original Folder". - Existing Files:
mklinkcannot overwrite an existing file. Delete the destination path before running the command.
Conclusion
For most users, Developer Mode is the path of least resistance. However, if you are in a corporate environment or on a Pro/Enterprise machine, using secpol.msc is the best practice for maintaining a secure system while granting necessary dev-tools access.
Keywords: Windows 10 Symbolic Link, mklink without admin, SeCreateSymbolicLinkPrivilege, Developer Mode Windows 10, Local Security Policy symlinks, Create symbolic links standard user, Directory Junction vs Symlink.
