Skip to main content

How to Create a Symbolic Link to a Directory in Batch Script

A Symbolic Link (or "symlink") is a modern and flexible type of file system pointer, similar in concept to a Directory Junction. It creates a reference at one location that transparently points to a folder in another. When a user or application navigates to the symbolic link, they are seamlessly redirected to the target directory.

The key advantage of a symbolic link over a directory junction is its ability to point to network shares (UNC paths), making it an invaluable tool for mapping shared resources to a local file path. This guide will teach you how to use the mklink /D command to create directory symbolic links, explain how they differ from junctions, and show you how to leverage their network capabilities.

The mklink (Make Link) command is the standard Windows utility for creating links. To create a symbolic link specifically for a Directory, you must use the /D switch.

Critically, mklink requires elevated privileges. You must run your batch script from a command prompt that has been "Run as Administrator."

The syntax is: mklink /D "LinkName" "TargetFolder"

  • "LinkName": The path for the symbolic link you are creating. This path must not already exist.
  • "TargetFolder": The path to the existing folder that the link will point to. This can be a local path or a network UNC path.

While they behave similarly for local paths, there is one crucial difference that determines which one you should use.

FeatureDirectory Symbolic Link (/D)Directory Junction (/J)
Target LocationLocal OR Network. Can point to D:\Data or \\Server\Share.Local drives only. Can point to D:\Data but cannot point to \\Server\Share.
ResolutionCan be understood by remote systems. The link is parsed on the client accessing it.Processed by the local server. Can be slightly faster for local-to-local links.
Typical Use CaseLinking to network shares; modern standard for local links.Older, more compatible standard for local-only folder redirection.

Rule of Thumb: Use a Symbolic Link (/D) unless you have a specific need for the older Junction (/J) format.

Let's create a symbolic link from a user's profile to a central data folder on another drive.

@ECHO OFF
REM This script must be run as Administrator.

SET "TARGET=D:\CentralUserData\John.Doe"
SET "LINK=%USERPROFILE%\Documents\CentralData"

ECHO Creating Symbolic Link...
mklink /D "%LINK%" "%TARGET%"

Output:

Creating Symbolic Link...
symbolic link created for C:\Users\John.Doe\Documents\CentralData <<===>> D:\CentralUserData\John.Doe

Now, navigating to C:\Users\John.Doe\Documents\CentralData will transparently show the contents of the D:\CentralUserData\John.Doe folder.

The Killer Feature: Linking to a Network Share​

This is the primary reason to use a symbolic link over a junction. You can make a network resource appear as if it were a local folder on your computer.

This script links a local C:\ProjectAssets folder to a shared server location.

@ECHO OFF
REM Run as Administrator.

SET "TARGET=\\FileServer\Shared\CreativeAssets"
SET "LINK=C:\ProjectAssets"

ECHO Creating network-targeted Symbolic Link...
mklink /D "%LINK%" "%TARGET%"

Output:

Creating network-targeted Symbolic Link...
symbolic link created for C:\ProjectAssets <<===>> \\FileServer\Shared\CreativeAssets
note

Any program on your local machine can now access C:\ProjectAssets and be seamlessly redirected to the network share, which is incredibly useful for tools that don't work well with UNC paths.

  • /D: (Required for Directory Symlinks) Creates a Directory symbolic link.
  • Link: The path for the new symbolic link. This directory should not already exist.
  • Target: The existing directory that the link will point to.

Common Pitfalls and How to Solve Them​

Problem: The Script is Not Run as Administrator​

This is the most common reason for failure. mklink is a protected command.

The error will be:

You do not have sufficient privilege to perform this operation.

Solution: Run as Administrator​

Your script must be executed from a command prompt with administrative privileges. Right-click your .bat file or cmd.exe and select "Run as administrator."

  • If the path you specify for the Link already exists, mklink will fail.
  • If the path you specify for the Target does not exist, mklink will also fail.

The following is the error if Link exists:

Cannot create a file when that file already exists.

Solution: Check Before Creating​

A robust script should always verify the paths before attempting the operation.

IF EXIST "%LINK%\" (ECHO [ERROR] Link path already exists. & GOTO :EOF)
IF NOT EXIST "%TARGET%\" (ECHO [ERROR] Target path does not exist. & GOTO :EOF)
mklink /D "%LINK%" "%TARGET%"

Practical Example: Creating a Local Path for Shared Tools​

This script creates a convenient local folder, C:\DevTools, that points to a centralized repository of development tools maintained on a network server.

@ECHO OFF
SETLOCAL
REM This script must be run as Administrator.

SET "TOOLS_SHARE=\\fileserver\engineering\SharedDevTools"
SET "LOCAL_LINK=C:\DevTools"

ECHO --- Shared Tools Linker ---
ECHO.
ECHO Target: %TOOLS_SHARE%
ECHO Link:   %LOCAL_LINK%
ECHO.

IF NOT EXIST "%TOOLS_SHARE%\" (
    ECHO [ERROR] The network share is not accessible or does not exist.
    GOTO :End
)
IF EXIST "%LOCAL_LINK%\" (
    ECHO [INFO] The local link already exists. Nothing to do.
    GOTO :End
)

ECHO Creating symbolic link...
mklink /D "%LOCAL_LINK%" "%TOOLS_SHARE%"

ECHO.
ECHO [SUCCESS] The link C:\DevTools is now available.

:End
ENDLOCAL

Conclusion​

The mklink /D command is the modern and flexible way to redirect directories in Windows. Its ability to handle both local and network paths makes it superior to Directory Junctions for most use cases.

To successfully create a Directory Symbolic Link, always remember:

  1. You must run the script as an Administrator.
  2. The link name must not exist, but the target folder must exist.
  3. Use a symbolic link (/D) whenever you need to point to a network UNC path.

Symbolic links are a powerful tool for simplifying complex file system layouts and improving the usability of shared network resources.

Table of Contents