Fix mklink Symbolic Link Permission Denied Without Developer Mode on Windows 11

You run the mklink command in Command Prompt on Windows 11 and see the error You do not have sufficient privilege to perform this operation. This happens because creating symbolic links requires the SeCreateSymbolicLinkPrivilege right, which is not granted to standard user accounts by default. Many online guides tell you to enable Developer Mode, but that setting is not always available or desirable in business environments. This article explains why the permission error occurs and provides three reliable methods to fix it without turning on Developer Mode.

Why mklink Returns Permission Denied on Windows 11

The mklink command is a built-in Windows tool for creating symbolic links, also called symlinks. A symbolic link is a file system object that points to another file or folder. Unlike a shortcut, a symlink is treated by the operating system as the actual file or folder. This makes symlinks useful for redirecting application data, syncing folders, or managing development environments.

Windows 11 requires the SeCreateSymbolicLinkPrivilege user right to create symbolic links. By default, only members of the Administrators group have this privilege. Standard users, even those with administrative rights through User Account Control, do not have it. When you run mklink without the required privilege, Windows returns the error You do not have sufficient privilege to perform this operation.

Developer Mode is one way to grant this privilege, but it also enables other features like device portal and SSH server. In business environments, IT policies often restrict Developer Mode for security reasons. The methods below avoid Developer Mode entirely.

Method 1: Run Command Prompt as Administrator

The quickest fix is to run Command Prompt with administrator rights. This grants the SeCreateSymbolicLinkPrivilege for the current session. The privilege is not permanent and must be repeated each time you open a new Command Prompt window.

1. Open Start Menu and search for Command Prompt
   Type cmd in the search box. The Command Prompt app appears in the search results.
2. Select Run as administrator
   Right-click Command Prompt and choose Run as administrator. Click Yes in the User Account Control prompt.
3. Run the mklink command again
   Type your mklink command, for example mklink /D C:\Link C:\Target. The symbolic link should now be created without the permission error.

If the error persists, your user account may not be a member of the Administrators group. Check this by typing net user %username% in the elevated Command Prompt and looking for Local Group Memberships. If it does not show Administrators, contact your IT administrator.

Method 2: Grant Create Symbolic Links Privilege via Local Security Policy

Windows 11 Pro, Enterprise, and Education editions include the Local Security Policy console. You can use it to permanently add the SeCreateSymbolicLinkPrivilege to a specific user or group. This method does not require a reboot and works until the policy is removed.

1. Open Local Security Policy
   Press Win + R, type secpol.msc, and press Enter. If this command fails, your edition of Windows 11 does not include secpol.msc. Use Method 3 instead.
2. Navigate to User Rights Assignment
   In the left pane, expand Security Settings and then Local Policies. Click User Rights Assignment.
3. Locate the Create symbolic links policy
   Scroll down in the right pane and double-click Create symbolic links.
4. Add a user or group
   Click Add User or Group. Type the username or group name, for example domain\username or BUILTIN\Users. Click Check Names to validate, then click OK.
5. Apply the change
   Click OK to close the policy window. The change takes effect immediately. You do not need to restart Windows 11.
6. Test the mklink command
   Open a new Command Prompt window as a standard user and run your mklink command. The permission error should no longer appear.

Method 3: Grant Create Symbolic Links Privilege via Group Policy (Windows 11 Pro, Enterprise, Education)

The Group Policy Editor provides an alternative interface for the same policy setting. This method is useful when you are already managing other policies through Group Policy.

1. Open Group Policy Editor
   Press Win + R, type gpedit.msc, and press Enter. If this command fails, your edition of Windows 11 does not include gpedit.msc. Use Method 2 instead.
2. Navigate to User Rights Assignment
   In the left pane, go to Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment.
3. Locate and edit Create symbolic links
   Double-click Create symbolic links in the right pane. Click Add User or Group, enter the user or group name, and click OK.
4. Apply the policy
   Click OK to close the policy window. The change applies immediately to the local machine.
5. Verify the fix
   Open a new Command Prompt window as a standard user and run mklink. The symbolic link should be created without the permission error.

Common Issues After Fixing mklink Permission

mklink Still Fails After Adding the Privilege

If the error persists, the user account may not have refreshed its token. Log off and log back on, or restart the computer. Also verify that the policy is applied by running gpresult /r in Command Prompt and checking for Create symbolic links under User Rights.

Symbolic Links Not Working for Network Shares

Creating symbolic links that point to network locations requires the SeCreateSymbolicLinkPrivilege and the SeBackupPrivilege. Grant both privileges using the same policy method. Additionally, the target network share must allow symlink traversal, which is not always enabled by default on remote file servers.

Symbolic Links Deleted After Windows Update

Windows updates can reset local security policies to defaults. After a major update, check the Create symbolic links policy to confirm your user or group is still listed. If it was removed, reapply the policy using Method 2 or Method 3.

Run as Administrator vs Grant Privilege via Policy: Which to Use

Item	Run as Administrator	Grant via Local Security Policy
Persistence	Per session only	Permanent until policy is removed
Required privilege	Administrator group membership	Administrator group membership to set policy
Works for standard users	No	Yes
Reboot required	No	No, but logoff/logon needed for token refresh
Best for	Occasional use by admin	Frequent use or automated scripts

The mklink permission denied error on Windows 11 is caused by a missing user right, not a bug. You can fix it by running Command Prompt as administrator for one-time use, or by permanently granting the Create symbolic links privilege through Local Security Policy or Group Policy. Neither method requires Developer Mode. After applying the fix, test the mklink command with a simple symlink to confirm the change works. For automated scripts or regular symlink creation, the policy-based approach saves time and avoids repeated elevation prompts.