Vagrant Up issue: Access is denied. (5) (ChildProcess::LaunchError)

[Metlhead723]

I've had this same issue with both updated (vagrant_2.4.3_windows_amd64, VirtualBox-7.1.4-165100-Win) AND downgraded versions of Vagrant/Virtualbox together (vagrant_2.4.1_windows_amd64, VirtualBox-7.0.20-163906-Win).

Trying to run "vagrant up" from my Homestead directory for the very first time in my project, which leads me to 2 errors:

Bringing machine 'homestead' up with 'virtualbox' provider...
==> homestead: Box 'laravel/homestead' could not be found. Attempting to find and install...
homestead: Box Provider: virtualbox
homestead: Box Version: >= 14.0.2, < 15.0.0
C:/Program Files/Vagrant/embedded/gems/gems/vagrant-2.4.1/lib/vagrant/util/subprocess.rb:163:in rescue in execute': Access is denied. (5) (Vagrant::Util::Subprocess::LaunchError) C:/Program Files/Vagrant/embedded/gems/gems/childprocess-4.1.0/lib/childprocess/windows/process_builder.rb:89:in create_process': Access is denied. (5) (ChildProcess::LaunchError)

My VPN is disconnected. I'm not sure of any Windows security/firewall that would block this. Has anyone else had any experience in resolving this issue? Please let me know, thanks so much! :)

[jayeshkumarbhoi]

For me it was working fine few week ago but suddenly today it stopped working with error like below

C:/Program Files/Vagrant/embedded/gems/gems/vagrant-2.4.3/lib/vagrant/util/subprocess.rb:163:in `rescue in execute': Access is denied. (5) (Vagrant::Util::Subprocess::LaunchError)
        from C:/Program Files/Vagrant/embedded/gems/gems/vagrant-2.4.3/lib/vagrant/util/subprocess.rb:156:in `execute'
        from C:/Program Files/Vagrant/embedded/gems/gems/vagrant-2.4.3/lib/vagrant/util/subprocess.rb:25:in `execute'
        from C:/Program Files/Vagrant/embedded/gems/gems/vagrant-2.4.3/lib/vagrant/util/downloader.rb:206:in `block in execute_curl'
        from C:/Program Files/Vagrant/embedded/gems/gems/vagrant-2.4.3/lib/vagrant/util/busy.rb:22:in `busy'
        from C:/Program Files/Vagrant/embedded/gems/gems/vagrant-2.4.3/lib/vagrant/util/downloader.rb:205:in `execute_curl'
        from C:/Program Files/Vagrant/embedded/gems/gems/vagrant-2.4.3/lib/vagrant/util/downloader.rb:159:in `head'
        from C:/Program Files/Vagrant/embedded/gems/gems/vagrant-2.4.3/lib/vagrant/action/builtin/box_add.rb:615:in `metadata_url?'
        from C:/Program Files/Vagrant/embedded/gems/gems/vagrant-2.4.3/lib/vagrant/action/builtin/box_add.rb:108:in `block in call'
        from C:/Program Files/Vagrant/embedded/gems/gems/vagrant-2.4.3/lib/vagrant/action/builtin/box_add.rb:106:in `map'
        from C:/Program Files/Vagrant/embedded/gems/gems/vagrant-2.4.3/lib/vagrant/action/builtin/box_add.rb:106:in `call'
        from C:/Program Files/Vagrant/embedded/gems/gems/vagrant-2.4.3/lib/vagrant/action/warden.rb:38:in `call'
        from C:/Program Files/Vagrant/embedded/gems/gems/vagrant-2.4.3/lib/vagrant/action/builder.rb:183:in `call'
        from C:/Program Files/Vagrant/embedded/gems/gems/vagrant-2.4.3/lib/vagrant/action/runner.rb:104:in `block in run'

[sam-vdp]

I had the same issue and it was caused by Windows Defender blocking curl.exe from running.

Try running C:/Program Files/Vagrant/embedded/mingw64/bin/curl.exe (using command line or explorer). If you get an error, that's what you need to fix.

P.S.: My solution was this:
Windows now ships its own version of curl in C:\Windows\system32. As a result, Windows Defender blocked access to the "duplicate" of this system tool:
https://learn.microsoft.com/en-us/defender-endpoint/attack-surface-reduction-rules-reference#block-use-of-copied-or-impersonated-system-tools-preview

I replaced the embedded curl.exe of Vagrant with a symlink:
mklink "C:\Program Files\Vagrant\embedded\mingw64\bin\curl.exe" "C:\Windows\System32\curl.exe"