« NStatic Status | Main | Symbolic Links Redux »

October 03, 2006


TrackBack URL for this entry:

Listed below are links to weblogs that reference Symbolic Links in Vista:

» re: Windows Vista 体験記 - mklink from 囚人のジレンマな日々
re: Windows Vista 体験記 - mklink [Read More]


Paul Betts

The way I understand it is, junctions are a trick to get part of the directory to reread itself, ie say there's a pointer in each directory that points to its children, with junction points, you set the pointer to some existing tree. They're somewhat akin to *nix's mount -o bind

Symbolic links are based purely on names, they have nothing to do with contents. When the fs looks up a name, if it encounters a symlink it starts over again with what the symlink points to (so you have to check for loops and what)

Symlinks in *nix can have permissions, but almost never do because it makes no sense.

Wesner Moise

Paul's comments sounds plausible.

So, symbolic links may not actually be reparse points, a mechanism that is probably limited to directories.

As a result, API functions need to be changed to specifically handle symbolic links which are just regular files.

Wesner Moise

One point I used linkd.exe from the Windows Resource Kit not junction.exe, so junction.exe may have limitations on the drive support.

Blind Wanderer

I mostly use junctions to chain link drives together in creative ways. Say an application wants to put it's cache in one place and no option to move it...

Junctions can only be 16 deep. More then 16 junctions and an error is returned.

A good tool for creating junctions & hardlinks is "NTFS Link" (it's open source so it shouldn't be a problem to add Symbolic Link support). It encorporates nicely into Explorer.


I moved the directory "C:\Users\MyName\Documents" to "D:\MyName". After doing so, the symlink "C:\Users\MyName\My documents" is broken and points to a non-existing directory. (Everybody, who moves his user files to a separate data partition, will probably face this problem)

Did you ever try to rebuild the symlink "My documents" as Scott Hanselman wrote in his blog http://www.hanselman.com/blog/MoreOnVistaReparsePoints.aspx ?
I did, but my self-made link behaves differently than the original one, even after adapting the access control settings (see below). Clicking on my self-made link leads me through two UAC dialogs, whereas clicking on the original link blocks any access. What is the difference?

Here is, what I did:

- C:\Users\MyName> mklink "My documents" D:\MyName
- New security setting (DACL):
--- Add user "Everyone" with the following permissions: List Folders/Read Data: Deny
--- Change the owner of the link to SYSTEM

Thank you for any idea.
Best regards


Oh sorry, there is a typing error in my post: It should be: mklink /d "My documents" D:\MyName


this is good site for cheap software


The comments to this entry are closed.

My name is Wesner Moise. I am a software entrepreneur developing revolutionary AI desktop applications. I worked as a software engineer in Microsoft Excel group for six years during the 1990s. I worked on PivotTables and wrote the most lines of code in Excel 97-- about 10 times the median developer. I have a Harvard BA in applied math/computer science and a UCLA MBA in technology entrepreneurship. I am a member of the Triple Nine Society, a 99.9 percentile high-IQ society.

December 2013

Sun Mon Tue Wed Thu Fri Sat
1 2 3 4 5 6 7
8 9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24 25 26 27 28
29 30 31