In Windows mapped drives are mapped per logon session and when you have a split token (limited vs admin), each token is in a unique logon session. This means that drives that have been mapped in a limited logon session, like in Windows explorer, will not be seen in the admin session and vice versa.
You can prove this by running ‘net use’ in a normal command prompt versus an elevated command prompt. You have a few options; * set the EnableLinkedConnections registry property https://support.microsoft.com/en-au/help/3035277/mapped-drives-are-not-available-from-an-elevated-prompt-when-uac-is-co which shares the drives between a split token * manually map the drive with net use before running vagrant up * don’t use mapped drives altogether as you will probably come across another issue, especially if you start trying to run this non interactively Thanks Jordan -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/6d0fab41-3710-4030-bf6d-6b9eb039de3d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
