Symbolic links on the other hand refer directly to the file which refers to the inode, a. With this utility you can use the symlink application Microsoft Windows has well hidden inside the cmd.exe app. Rather unfortunate if I need to create further symlinks at a later stage, but it does work, it is just very inconvenient. A hard link is essentially a synced carbon copy of a file that refers directly to the inode of a file. My solution became to disable User Account Control, reboot, then create the symlinks as my own user, then re-enabling UAC and rebooting again. Note: Make sure the directory you're trying to link to exists or hasn't been moved or deleted, prior to linking. Now you should be able to run mklink commands like this with no problems: mklink /d %userprofile%\music \\server\music
Substitute Link in the command above with the full path of a folder (directory) you want created as a soft symbolic link at. (see screenshot below) mklink /d ' Link ' ' Source Target '. When you log back in, run cmd with admin privileges. 2 Type the command below into the elevated command prompt, and press Enter. Add your username to the list, click OK.Navigate to: Local Policies > User Rights Assignment.Go to the Run dialog and type: secpol.msc Your user account has some security policies on them by default which can be disabled, through secpol.msc. This is a old thread, but still want to clarify that you can create symbolic links like this: The following command worked for me as administrator: mklink /D C:\temp11111 \\server\share\foldername\Īnd also check whether your command contains appropriate quotes ( "). Run cmd as administrator and use UNC path.