windows 10 - [vagrant-hostsupdater] This operation requires administrative access.

[adamplabarge]

Fixed here agiledivider/vagrant-hostsupdater#89

    default: Guest Additions Version: 4.3.36
    default: VirtualBox Version: 5.1
==> default: [vagrant-hostsupdater] Checking for host entries
==> default: [vagrant-hostsupdater] Writing the following entries to (C:/WINDOWS/system32/drivers/etc/hosts)
==> default: [vagrant-hostsupdater]   192.168.50.4  vvv  # VAGRANT: 685ad3a645e6d56f30d959fd922ef00b (default) / 0295f741-a12a-42b4-bb1b-a835bde69fed
==> default: [vagrant-hostsupdater]   192.168.50.4  vvv.dev  # VAGRANT: 685ad3a645e6d56f30d959fd922ef00b (default) / 0295f741-a12a-42b4-bb1b-a835bde69fed
==> default: [vagrant-hostsupdater]   192.168.50.4  local.wordpress.dev  # VAGRANT: 685ad3a645e6d56f30d959fd922ef00b (default) / 0295f741-a12a-42b4-bb1b-a835bde69fed
==> default: [vagrant-hostsupdater]   192.168.50.4  src.wordpress-develop.dev  # VAGRANT: 685ad3a645e6d56f30d959fd922ef00b (default) / 0295f741-a12a-42b4-bb1b-a835bde69fed
==> default: [vagrant-hostsupdater]   192.168.50.4  build.wordpress-develop.dev  # VAGRANT: 685ad3a645e6d56f30d959fd922ef00b (default) / 0295f741-a12a-42b4-bb1b-a835bde69fed
==> default: [vagrant-hostsupdater] This operation requires administrative access. You may skip it by manually adding equivalent entries to the hosts file.
==> default: Forcing shutdown of VM...
==> default: Destroying VM and associated drives...
C:/Users/adaml/.vagrant.d/gems/2.2.5/gems/vagrant-hostsupdater-1.0.2/lib/vagrant-hostsupdater/HostsUpdater.rb:98:in `initialize': Permission denied @ rb_sysopen - C:/WINDOWS/system32/drivers/etc/hosts (Errno::EACCES)

Seems this needs to be able to write to the host file?

[iliyaskhan]

Hey, did you solved the issue?

[rmurillo21]

The issue was fixed here agiledivider/vagrant-hostsupdater#89

Run as administrator or give the current user rw permission on the hosts file.

[musamamasood]

You can give the rw permission to the hosts file.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.