Chris Roberts

Hi there, Please install Vagrant using the [official package](https://www.vagrantup.com/downloads). If you still encounter the error after updating your installation, let me know and I will investigate further. Thanks

@jbiason Hi, thanks for the information. The installation of vagrant you are using is not the official build. The official build can be found [here](https://www.vagrantup.com/downloads). Do you still encounter the...

Repository has been updated to account for this and the proper package installs now when following instructions on site so closing this up. Cheers!

Related: #12510

As a work around to prevent the error until a proper solution is in place, you can disable NFS modifications using the `nfs_export` option in your Vagrantfile: https://www.vagrantup.com/docs/synced-folders/nfs#nfs_export

This may be due to powershell compiling assemblies on startup which is causing the delay. Precompiling them can resolve the issue if it is indeed the root cause: https://serverfault.com/questions/761301/calling-powershell-exe-is-extremely-slow/761473#761473

@yasny / @keilma It is not an issue with running Vagrant under powershell or cmd. Vagrant executes powershell commands on Windows to determine things like available providers and user permissions....

Hi there, Would you please provide a gist of the debug output from running a `vagrant up` where you encounter this issue? Also, how are you determining that the folders...

Hi there, Is this issue encountered when connected to the guest after running `vagrant ssh` ?

@ladar Just a note here, for the 64bit rpm builds i was able to revert back to using centos 6 which I believe should resolve these issues.