Are you running the command prompt as administrator and using the mklink command? If so post your syntax of the command.
Yes you really do however you can also set admin as the default cmd and assume that only you will use it...
I believe this is a security policy that you need to modify, makes sense that they disallowed them as most people never use symbolic links on NTFS.
Fire up Group Policy editor (gpedit.msc) and browse to the following location:
Computer Configuration -> Security Settings -> Local Policies -> User Rights Assignment -> Create symbolic links
Also see the fsutil command:
fsutil behavior query symlinkevaluation
fsutil behaviour set symlinkevaluation
If all else fails maybe toggling UAC off would allow creation?
Because the 'mklink' command would then need to be MUCH larger and have a way to go searching for this extra data… perhaps over the network in the case of a domain, it would also need permission to enter a user's profile and look at their settings.
A human operator can simply say "run as admin" to make the extra code redundant & that seems to work well enough to keep most people happy.
Yes, A skilled coder could make it browse our emails, do your internet banking & in the near future perhaps even have sex with your wife… what investors and consumers will think of this new Windows feature is debatable.
For what its worth I am c+ and v-basic certified but "run as admin" has been around a long time so as a requirement is nothing new… i.e. something all windows programmers need to know.
The problem with just throwing away old security protocols and functionality is that Windows needs to remain backwards compatible… as any software developer knows, making something that only works on one version of Windows with one set of hardware is simple, cheap and only needs a light footprint… that’s why Microsoft is so strongly behind the development of apps as the future for student programmers.
p.s. I admit my Powershell scripting needs a refresher but each too their own and I hope you have a good day.