Vagrant 2.2.9 on Windows 10 performance

Hi there,

i’m new to vagrant so i do not have any experience and therefore asking if what i am seeing on my box is normal behaviour or if i have some issue with my setup i can work on.
I am using the latest vagrant release on a Windows 10 (2004) box with VirtualBox.
If i type in any vagrant command, it takes almost 3 minutes until anything happens.

May it be a vagrant init, up, or even just “vagrant” without any parameters, it takes 3 minutes to get any output.

I am not sure if this is normal behaviour, as it doesn’t seem so to me at first sight and i just need to be patient, or if this is an issue and if so, if there are any steps i can take to find out what is happening and preventing vagrant from performing faster.
The host box itself has quite some CPU cores as well as 32 gig of memory, all being idle and waiting for action so that should definitely not being an issue with hardware performance.


i found about the vagrant log levels and i see that various powershell commands are being run that take a lot of time, like finding out if the user is in the administrators role and getting the users groups.
I don’t know why they take so long, but it is definitely not normal. Being started in. privileged powershell vagrant up takes only a few seconds to respond.

What powershell comands take so long?
I have had such an issue but not 3 minutes. I have had a scenario which at my LAN it takes a really short time while on a workplace it took at-least 5+ seconds to start showing that something is moving.

I located and found this bug report:

And my current idea for a solution would be to change the dns client at:

to a an async one using this:
$x = (Get-VMHost).Name; if($x -eq [System.Net.Dns]::GetHostEntryAsync($x).Result.HostName){ Write-Output 'true'}

To debug it I have used the next powershell commands since the example in the mentioned bug report is not for powershell cli:

vagrant status
Remove-Item Env:\VAGRANT_LOG