World Library  
Flag as Inappropriate
Email this Article

NTFS symbolic link

Article Id: WHEBN0007441268
Reproduction Date:

Title: NTFS symbolic link  
Author: World Heritage Encyclopedia
Language: English
Subject: NTFS reparse point, NTFS junction point, Technical features new to Windows Vista, ReFS, NTFS
Collection: Disk File Systems, Windows Disk File Systems
Publisher: World Heritage Encyclopedia

NTFS symbolic link

An NTFS symbolic link (symlink) is a filesystem object in the NTFS filesystem that points to another filesystem object. The object being pointed to is called the target. Symbolic links should be transparent to users; the links appear as normal files or directories, and can be acted upon by the user or application in exactly the same manner. Symbolic links are designed to aid in migration and application compatibility with POSIX operating systems, and were introduced with the modifications made to the NTFS file system with Windows Vista, but available through filter drivers[1] for Windows XP. Unlike POSIX symbolic links, however, Windows symbolic links to files are distinct from Windows symbolic links to directories and therefore cannot be used interchangeably.

Unlike an NTFS junction point (available since Windows 2000), a symbolic link can also point to a file or remote SMB network path. While NTFS junction points support only absolute paths on local drives, the NTFS symbolic links allow linking using relative paths. Additionally, the NTFS symbolic link implementation provides full support for cross-filesystem links. However, the functionality enabling cross-host symbolic links requires that the remote system also support them, which effectively limits their support to Windows Vista and later Windows operating systems.

An NTFS symbolic link is not the same as a Windows shortcut file, which is a regular file. The latter may be created on any filesystem (such as the earlier FAT32), may contain metadata (such as an icon to display when the shortcut is viewed in Windows Explorer), and is not transparent to applications.


  • Restrictions 1
  • Tools 2
  • Other properties 3
  • Limitations 4
  • Symbolic links in Windows XP 5
  • See also 6
  • References 7
  • External links 8


The default security settings in Windows Vista/Windows 7 disallow non-elevated administrators and all non-administrators from creating symbolic links. This behavior can be changed running "secpol.msc" the Local Security Policy management console (under: Security Settings\Local Policies\User Rights Assignment\Create symbolic links). It can be worked around by starting cmd.exe with Run as administrator option or the runas command.


The mklink command is used to create a symbolic link. It is a built-in command of cmd.exe in Windows Vista and later.[2]

In XP, junction utility by Mark Russinovich is capable of working with reparse points, now offered by Microsoft as a part of Sysinternals suite.

Windows exposes CreateSymbolicLink function in its API starting from Windows Vista. Since mklink command depends on cmd.exe it may not be possible to use it in all contexts. New-SymLink function uses aforementioned API to implement soft link functionality using Powershell. Community Extensions also contains function New-SymLink.

Other properties

Symbolic links can point to non-existent targets because the operating system does not check to see if the target exists.[3]


Symbolic links do not work at boot, so it's impossible to redirect e.g.:

  • folder containing hiberfil.sys (if it's configured to be outside root directory)
  • \Windows
  • \Windows\system32
  • \Windows\system32\Config

Windows Installer does not fully support symbolic links. A redirected \Windows\Installer will cause most .msi-based Windows installers to fail with error 2755 and/or error 1632.

Nevertheless, it is possible to redirect:

  • \Documents and Settings
  • \ProgramData
  • \Program Files
  • \Program Files (x86)
  • \Users

Creating symbolic links for \Users and \ProgramData pointing to another drive is not recommended as it breaks updates and Windows Store Apps.[4]

Creating symbolic links for \Users, \ProgramData, "\Program Files" or "\Program Files (x86)" pointing to other locations breaks installation resp. upgrade of Windows.[5]

Creating symbolic links for "\Program Files" or "\Program Files (x86)" pointing to another drive breaks Windows' Component Based Servicing which hardlinks files from its repository \Windows\WinSxS to their installation directory.

Symbolic links in Windows XP

Since Windows XP uses the same NTFS format version as later releases, it's feasible to enable symbolic links support in it. A third-party driver exists that does it by installing itself as a file system filter. [1]

See also


  1. ^ a b Hermann Schinagl (August 23, 2013). "ln - commandline hardlinks - Symbolic links for Windows XP". 
  2. ^ Mklink on
  3. ^
  4. ^ "Relocation of the Users directory and the ProgramData directory to a drive other than the drive that contains the Windows directory". Retrieved 2015-03-12. 
  5. ^ "You encounter an error when trying to install Windows 8.1 due to redirecting the Users or Program Files folder to another partition". Retrieved 2015-03-12. 

External links

  • Documentation for NTFS symbolic links on MSDN
  • CreateSymbolicLink function in the Win32 API
  • fsutil hardlink create - creates a hard link (Windows 2000 and later)
This article was sourced from Creative Commons Attribution-ShareAlike License; additional terms may apply. World Heritage Encyclopedia content is assembled from numerous content providers, Open Access Publishing, and in compliance with The Fair Access to Science and Technology Research Act (FASTR), Wikimedia Foundation, Inc., Public Library of Science, The Encyclopedia of Life, Open Book Publishers (OBP), PubMed, U.S. National Library of Medicine, National Center for Biotechnology Information, U.S. National Library of Medicine, National Institutes of Health (NIH), U.S. Department of Health & Human Services, and, which sources content from all federal, state, local, tribal, and territorial government publication portals (.gov, .mil, .edu). Funding for and content contributors is made possible from the U.S. Congress, E-Government Act of 2002.
Crowd sourced content that is contributed to World Heritage Encyclopedia is peer reviewed and edited by our editorial staff to ensure quality scholarly research articles.
By using this site, you agree to the Terms of Use and Privacy Policy. World Heritage Encyclopedia™ is a registered trademark of the World Public Library Association, a non-profit organization.

Copyright © World Library Foundation. All rights reserved. eBooks from World eBook Fair are sponsored by the World Library Foundation,
a 501c(4) Member's Support Non-Profit Organization, and is NOT affiliated with any governmental agency or department.