World Library  
Flag as Inappropriate
Email this Article

NTFS junction point

Article Id: WHEBN0000483838
Reproduction Date:

Title: NTFS junction point  
Author: World Heritage Encyclopedia
Language: English
Subject: ReFS, Hard link, List of Microsoft Windows components, .NET Framework, Directory structure
Collection: Disk File Systems, Windows Disk File Systems
Publisher: World Heritage Encyclopedia

NTFS junction point

An NTFS junction point is a symbolic link to a directory that acts as an alias of that directory. This feature of the NTFS file system offers benefits over a Windows shell shortcut (.lnk) file, such as allowing access to files within the directory via Windows Explorer, the Command Prompt, etc.

Unlike NTFS symbolic links Junction points can only link to a local volume; junction points to remote shares are unsupported.[1]

Junction points are a type of NTFS reparse point. They were introduced with NTFS 3.0, the default file system for Windows 2000. The Windows 2000 and Windows 2003 Resource Kits include a program called linkd,[2] to create junction points; Mark Russinovich of Winternals released a tool called junction[3] which provided more complete functionality. Windows XP includes "fsutil";[4]Masatoshi Kimura released a filter driver[5] for the soft/symbolic link functionality existing in Windows XP's NTFS version, to be accessible to the end user. Windows Vista, Windows Server 2008, and later operating systems include an command-line utilitymklink for creating junction points.


  • Examples of use 1
    • Program redirection 1.1
    • Saving disk space 1.2
    • Circumventing pre-defined paths 1.3
  • Obtaining a list of junction points 2
  • Creating or deleting a junction point 3
  • Limitations 4
  • See also 5
  • References 6
  • External links 7

Examples of use

Program redirection

By setting a junction point that points to a directory containing a particular version of a piece of software, it may be possible to add another version of the software and redirect the junction point to point to the version desired.

Saving disk space

The contents of a junction use almost no disk space (they simply point to the original files in the original directory). If you need to have multiple points of entry to a large directory, junction points will serve that purpose well. Junction points should not be confused with a copy of something as they simply point to the original. If directories need to be modified separately a junction cannot be used as it does not provide a distinct copy of the directory or files within.

Circumventing pre-defined paths

Since reinstalling Windows (or installing a new version) often requires deleting the contents of the C: drive, it is advantageous to create multiple partitions so only one partition needs to be deleted during the installation. However, some programs don't let the user choose the installation directory, or install some of their files to the C: drive even when they are installed to a different drive. By creating a junction point, the program can be tricked into installing to a different directory.

Obtaining a list of junction points

A list of all the junctions present in the current directory can be obtained from an elevated Command Prompt as Admin by executing dir /aL, and a list of all the junctions present on a disk volume, by executing dir /aL /s C:\, where "C:" is the volume to scan.

Creating or deleting a junction point

A junction point can be created in Vista or later[6]

mklink /J  

To delete it in Vista or later, use: [7]



fsutil reparsepoint delete PATH

A junction point can be created in XP (after installing; Server 2003 Resource Kit) with

LINKD Source Destination

To delete it in XP, use:

LINKD Source /D


Neither the Windows NT startup process nor the Windows Vista startup process support Junction points, so it's impossible to redirect certain system folders:

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

However it is possible to redirect non-critical folders:

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

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

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

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

See also


  1. ^ Sysinternals Junction documentation
  2. ^ Microsoft Knowledge Base, 2007-02-20, How to create and manipulate NTFS junction points,
  3. ^ Mark Russinovich, 2010-09-08, Junction,
  4. ^
  5. ^
  6. ^ "mklink"
  7. ^ "How to Delete a Junction by Using Command Line in Windows 7"
  8. ^
  9. ^

External links

  • Microsoft Knowledge Base Article – 'How to Create and Manipulate NTFS Junction Points'
  • Junction command line utility from Microsoft TechNet
  • Codeproject Article – discussion on the source code of a junction point utility, aimed at programmers
  • PC Mag Article about adding any directory to the start menu (allowing a preview within the startmenu as a submenu).
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 Project Gutenberg 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.