Using npm on windows host will cause symlink errors #611
Please note that the Homestead issue tracker is reserved for bug reports and enhancements. We are not always able to debug Vagrant, Provider or Operating System issues but will do our best to help. Thank you!
Host operating system
This is the operating system that you run locally.
Windows 10 64 bit.
--- name: homestead7 ip: "192.168.10.10" memory: 2048 cpus: 1 provider: virtualbox authorize: /Users/Jonathan/Dropbox/Documents/SSH-Keys/Homestead/homestead.pub keys: - /Users/Jonathan/<snip>/private.key folders: - map: /Code to: /home/vagrant/Code sites: - map: new.app to: /home/vagrant/Code/new.app/public databases: - homestead ports: - send: 80 to: 80 - send: 443 to: 443
Before you begin
Make sure you have started vagrant on windows using a normal user. ie, you have NOT selected to
Thanks for taking the time to write this up. As I expected this is caused by not running the console application as administrator (therefore running vagrant as Administrator). There isn't anything we can do to fix this for windows users (and not make a change that would affect all platforms as the previous PR showed).
Sounds like the best advice is to run Vagrant as an administrator on Windows, or use the Linux subsystem to create your projects instead of doing it in Homestead.