January 18th, 2017 
etdot 
If you have used vagrant on a Windows host, you’ve undoubtedly been bit once or twice when trying to create a symlink inside your vagrant guest inside shared folder on the host, especially if your vagrant guest is linux. The reason is that under windows, creating a symlink (using mklink.exe) requires Administrative privileges. If your ‘vagrant up’ command was not executed from an Administrative Command Prompt, your VM will not be able to create these symlinks on the host filesystem.
The solution to the symlink problem is easy, make sure you run your vagrant commands from an Administrative Command Prompt. But, should you forget, a lot of time can be wasted powering off your vm and restarting under new security context.
Wouldn’t it be nice if that initial ‘vagrant up’ command alerted you that you did not have the proper privileges? Here is how you can make that happen: