0

I want to create a symbolic link betwee a folder on a network and a folder on the local drive using the following command;

mklink /d "\<networkName>\<folderA>\<folderB>" "C:\<folderA>\<folderB>\<folderC>"

I get the error; The file or directory is not a reparse point.

I did some searching online and didn't find much information on this error besides the tool, Junction which allows you to view reparse points. I prefer to do this within Windows ?

Edited by Siberian

2
Contributors
4
Replies
26
Views
5 Months
Discussion Span
Last Post by Siberian
1

Arghh, I was doing it in reverse, from a stackoverflow link I refreshed upon. Thanks :)

Votes + Comments
Thanks for the report. Nice to know it heped.
0

Just to share a little more. From an article on Windows 10 Developer Mode, I think you may find this of interest.

In Windows 10’s Creators Update, putting your device into developer mode relaxes restrictions on creating symbolic links. Previously, it was only possible for Administrator users to create symlinks. This is still the case on Windows 10—unless you put it into Developer Mode.

In Developer Mode, a user account with any level of privileges can create symbolic links. In other words, you can open a normal Command Prompt window and use the mklink command. Outside of Developer Mode, you’d need to open a Command Prompt window as Administrator before using the mklink command.
From https://www.howtogeek.com/292914/what-is-developer-mode-in-windows-10/

0

Thanks for the info.

I have to re-surface this issue; sorry if I forgot something. When using mklink and placing the network path after and the local path first, the symbolic link gets created but one of the links is a short-cut ?

mklink /d "C:\<folderA>\<folderB>\<folderC>" "\<networkName>/<folderA>"

The source gets created as a shortcut ?

This question has already been answered. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.