C:/HashiCorp/Vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/util/subprocess.rb:158:in `rescue in execute': Access is denied. (5) (Vagrant::Util::Subprocess::LaunchError)....i'm getting this error so far..what do i do? can u plz give suggestions for how to resolve this?

[devendra1321]

Please note that the Vagrant issue tracker is in priority reserved for bug reports and enhancements. For general usage questions, please use the Vagrant mailing list:
https://groups.google.com/forum/#!forum/vagrant-up. Thank you!

Tip: Before submitting your issue, don't hesitate to remove the above introductory text, possible empty sections (e.g. References), and this tip.

Vagrant version

Run vagrant -v to show the version. If you are not running the latest version
of Vagrant, please upgrade before submitting an issue.

Host operating system

This is the operating system that you run locally.

Guest operating system

This is the operating system you run in the virtual machine.

Vagrantfile

# Copy-paste your Vagrantfile here (but don't include sensitive information such as passwords, authentication tokens, or email addresses)

Please note, if you are using Homestead or a different Vagrantfile format, we
may be unable to assist with your issue. Try to reproduce the issue using a
vanilla Vagrantfile first.

Debug output

Provide a link to a GitHub Gist containing the complete debug output:
https://www.vagrantup.com/docs/other/debugging.html. The debug output should
be very long. Do NOT paste the debug output in the issue, just paste the
link to the Gist.

Expected behavior

What should have happened?

Actual behavior

What actually happened?

Steps to reproduce

References

Are there any other GitHub issues (open or closed) that should be linked here?
For example:

• NAT DNS Proxy Option? #1234
• ...

[briancain]

Hi there,

Thank you for opening an issue. However, there is not enough information here to reproduce or provide a recommendation. When you first open an issue, a template is pre-filled in the box. That template provides instructions for getting your host and guest information, the version of Vagrant, and the debug output. Without that information, it is very challenging for us to assist you.

Please supply that information either by updating this ticket or by closing this ticket and opening a new one. Thank you!

[briancain]

Hey there,

I am going to close this due to lack of response. If this is still occurring, please open a new issue and follow the provided issue template that appears when you click the "New Issue" button. This will help us in getting a reproduction and fix. Thanks!

[nazy]

I just faced the same issue.
In my case, it caused by a security software in my PC.

To identify the cause of issue I modified subprocess.rb and run vagrant --debug then
I found the security program blocks at least the following patterns.

• ruby.exe in embedded directory spawns ...
  • powershell.exe with -Command or -EncodedCommand option
  • cmd.exe with /K or /C option

Actually security program reported it.
It might be caused by false positive rules of the security program.

When someone face the same problem, you can check with irb.

> system('powershell -Help')
SNIP
=> true
> system('powershell -Command Write-Output test')
=> nil

If -Help worked (true) and -Command failed (nil) means someone prevented to run powershell.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.