Virtual server: Vagrant misinterprets tilde under Windows command line

[ghost]

I found out that the guide lacks some steps necessary on Windows systems to successfully configure Vagrant to find the directories. First of all, the way environmental variables are set does not seem to work on our systems. Also, despite setting the HOMEDRIVE and HOMEPATH vars to the correct ones, Vagrant tries to access ~/ktp-jako which does not exist. ~ is not supported in the Windows cmd.

I found Powershell to be a better console to run the commands. I was successfull configuring the server by setting vars in Powershell and running Vagrant inside of it. (Powershell does support path shortcut ~.)

Here is a script that automates the process: https://github.com/Aanekoskenlukio/virtual-abitti-script-ps

[mplattu]

We have and are aware that there are several Vagrant installations where ~ is correctly expanded to %HOMEDRIVE%%HOMEPATH%. According to the Vagrant issue tracker there has been issues with expanding tilde.

What Vagrant and Windows versions are you running?

[ghost]

Our systems are running Windows 10 version 10.0.16299 and the Vagrant version installed is 2.0.3. The temporary Powershell solution will suffice for now but we hope to find a way to initiate Vagrant from cmd.exe.

Thank you for including the link. We need to seek the solution from their side from now on.