Permission denied - C:/Windows/system32/drivers/etc/hosts (Errno::EACCES) #89
Comments
|
Nevermind, I think I found why. I'm using git bash through conemu and I have to start gitbash as administrator. |
|
One thing I have noticed though, by running as the administrator, the VM does not appear in VirtualBox anymore (because it's seen as a different user, explained by this: hashicorp/vagrant#4286) Also, I noticed that running it as administrator brings other constraints. |
|
I found a workaround in another issue ticket. Open %SystemRoot%\system32\drivers\etc in Windows Explorer, locate the hosts file, right-click it and set the usage rights to the current user (the one you run vagrant under) to allow file modification. If that is required, maybe this could be added to the documentation. |
|
Having the same issue. Here's the .cmd contents:
|
|
I'd just like to add that I experienced this issue and was able to narrow it down to Kaspersky Anti-Virus. Disabling the service completely and restarting restored correct functionality. I'll update this post when I find out which specific service it was that was causing issues. |
|
I just ran into this issue today on an Windows 10 installation I've had running for a couple months without any issues. Perhaps my issue was caused by not properly using 'vagrant halt' before shutdown? I can't be sure. In any event I suspect something hosed the VirtualBox VM, and here is how I resolved the following error. The output that followed the below error is almost exactly the same as @YAmikep output.
|
|
Have the same issue after updating Vagrant to 1.9 this morning. Tried @ronezone suggestion but didn't work for me. Vagrant 1.9 |
|
I've just encountered this issue while trying to setup a new VM with vagrant. Deleting the file at /users//.vagrant.d/tmp/hosts.temp (something like that, not the default hosts but the temporary copy of your hosts) seems to be doing the trick. |
|
Tried deleting temp files as suggested by @brettmaxwellmorgan ('c:\users%username%.vagrant.d\tmp') directory but no luck for me |
|
copy this to windows/system32/drivers/etc/hosts file and will work 100% |
|
Should be fixed with the UAC escalation. Let me know if there are issues. |
|
Ran cmder as administrator. Issue fixed. |
|
Hi. This issue happened to me many times in Windows 10, by some reason the plugin vagrant-hostupdater begins to not ask for the UAC (the window that asks you for permissions). I don't know surely what things changed recently. I tunned the Windows disabling some services, I've VirtualBox at 5.2, don't changed due to a bug with 6.0 setup. I installed some Windows updates too. How can I debug this to fix it? Following the behavior at runtime by setting some debug code lines at mentioned ruby files in the callstack debugging code? Someone familiarized with this can help? Is very nice for me to have the dialog that advices me that the hosts file is going to be changed instead of opening the Notepad as administrator etc. If the bug persists and I don't found the cause probably I will reinstall the OS. Probably as well, I could do a test in each change I do in my OS when it is fixed to reproduce it again. C:/Users//.vagrant.d/gems/2.4.4/gems/vagrant-hostsupdater-1.1.1.160/lib/vagrant-hostsupdater/HostsUpdater.rb:98:in `open'` |
|
+1 to above, it's no longer prompting UAC and is now just failing on write attempt. |
|
I restored my Windows using a restore point and it works again. Something changed in the OS caused this problem. If I have the issue again I will investigate more. |
|
Changing the share type of the vagrant shared folder to NFS solved it for me. |
|
I don't know if is the same issue but now, again, when I'm doing a vagrant reload or a vagrant halt I'm having the same error again. The only thing I see for the moment is that it fails at: C:/Users//.vagrant.d/gems/2.4.4/gems/vagrant-hostsupdater-1.1.1.160/lib/vagrant-hostsupdater/HostsUpdater.rb This is theoretically that the app is quering the OS for opening that file with write permissions and the OS is saying that is not permitted. Not knowing what thing do. I suppose that I will reinstall Windows and do an image, and restore it every day, Maybe it is possible to debug more with that programs that do a registry of all services and settings, and says you what changed or what program did you install when it starts failing. I will revise also antivirus settings, firewall, windows services. |
|
I have same problem with the host file...
Please! Help.. Emergency..... |
|
@ashokbaruaakas You should open an issue with Laragon. You are in the wrong GitHub issue. |
This worked for me too--went to the hosts file, right-clicked, "edit" button and chose the "Users" profile to add all permission checks to. Was warned by windows popup. |
I highly discourage everyone from doing this. In fact: the result allows every application running under the current user to modify the hosts file without further questions or possibilities of intervention. This is an enormous security issue. |
and others
I get this error on the first
vagrant up:Permission denied - C:/Windows/system32/drivers/etc/hosts (Errno::EACCES)Windows 10
Virtualbox 5.0.10
vagrant 1.7.4
The text was updated successfully, but these errors were encountered: