Windows issues on Vbox 6.1.18/Vagrant 2.2.14

[ghost]

This came up for me and some others recently when trying to get the VM up on Win10 20H2 (which may or may not be relevant). After the 1st Vagrant up, it works fine but once the machine is halted and restarted it will no longer connect to the /vagrant folder and goes into a timeout loop. The work around is to "do-release-upgrade" on the first successful login which updates to Ubuntu 16.04.7 LTS, there is probably a much less time consuming fix but thats a bit above my pay grade.

[ultrapalace]

I'm having the same issue, this didn't happen before but something has changed. I'm on vbox 5.2.44. My fix was to just destroy it.

[MichiganSynthWorks]

Issues seem to be resolved with recent updates to vagrantbox on 6.2.2 and Vagrant 2.2.15. Please close