{"action":"created","issue":{"url":"https://api.github.com/repos/mitchellh/vagrant/issues/6068","labels_url":"https://api.github.com/repos/mitchellh/vagrant/issues/6068/labels{/name}","comments_url":"https://api.github.com/repos/mitchellh/vagrant/issues/6068/comments","events_url":"https://api.github.com/repos/mitchellh/vagrant/issues/6068/events","html_url":"https://github.com/mitchellh/vagrant/issues/6068","id":98296045,"number":6068,"title":"Vagrant not starting after upgrade to Windows 10","user":{"login":"thewibblywobbly","id":5221910,"avatar_url":"https://avatars.githubusercontent.com/u/5221910?v=3","gravatar_id":"","url":"https://api.github.com/users/thewibblywobbly","html_url":"https://github.com/thewibblywobbly","followers_url":"https://api.github.com/users/thewibblywobbly/followers","following_url":"https://api.github.com/users/thewibblywobbly/following{/other_user}","gists_url":"https://api.github.com/users/thewibblywobbly/gists{/gist_id}","starred_url":"https://api.github.com/users/thewibblywobbly/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/thewibblywobbly/subscriptions","organizations_url":"https://api.github.com/users/thewibblywobbly/orgs","repos_url":"https://api.github.com/users/thewibblywobbly/repos","events_url":"https://api.github.com/users/thewibblywobbly/events{/privacy}","received_events_url":"https://api.github.com/users/thewibblywobbly/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/mitchellh/vagrant/labels/bug","name":"bug","color":"e11d21"},{"url":"https://api.github.com/repos/mitchellh/vagrant/labels/host/windows","name":"host/windows","color":"d4c5f9"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":59,"created_at":"2015-07-31T01:13:51Z","updated_at":"2015-09-10T16:40:28Z","closed_at":null,"body":"I am having this issue after upgrading to Windows 10 yesterday, did not have this issue with windows 7 two days ago.\r\n\r\n```\r\n$ vagrant up\r\nBringing machine 'default' up with 'virtualbox' provider...\r\n==> default: Importing base box 'puphpet/ubuntu1404-x64'...\r\n==> default: Matching MAC address for NAT networking...\r\n==> default: Checking if box 'puphpet/ubuntu1404-x64' is up to date...\r\n==> default: Setting the name of the VM: vagrant5_default_1438281430392_96097\r\n==> default: Clearing any previously set network interfaces...\r\nThere was an error while executing `VBoxManage`, a CLI used by Vagrant\r\nfor controlling VirtualBox. The command and stderr is shown below.\r\n\r\nCommand: [\"hostonlyif\", \"create\"]\r\n\r\nStderr: 0%...\r\nProgress state: E_FAIL\r\nVBoxManage.exe: error: Failed to create the host-only adapter\r\nVBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)\r\nVBoxManage.exe: error: Context: \"enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)\" at line 70 of file VBoxManageHostonly.cpp\r\n``` \r\n\r\n I'm also unable to create Host Only Interfaces in the VirtualBox GUI now. I was able to fix it, but it is definitely not permanent and does not feel like an appropriate fix. If anybody can suggest a more definitive fix or route of investigation for this issue, that would be greatly appreciated. The fix I found is from the following location (Steps 2 and 3 appear to be the most important as the error seems to caused by VirtualBox's inability to clear host only interfaces): https://laracasts.com/discuss/channels/general-discussion/windows-10-vagrant-virtualbox-homestead/?page=1\r\n\r\n1. Install Virtualbox 5 and Vagrant 1.7.4\r\n2. Comment line 17: config.vm.network :private_network, ip: settings[\"ip\"] ||= \"192.168.10.10\" in homestead.rb\r\n3.Comment line 64: b.use ClearNetworkInterfaces in action.rb (path ~\\HashiCorp\\Vagrant\\embedded\\gems\\gems\\vagrant-1.7.4\\plugins\\providers\\virtualbox\\action.rb)\r\n4. Homestead init and/or up\r\n5. Homestead halt\r\n6. In Virtualbox preferences -> network -> host-only networks edit existing Host-Only adapter and add 192.168.10.10 as IP address\r\n7. Select homestead box in Virtualbox and go to settings -> network -> adapter 2 and select Host-only network (the one edited in step above)\r\n8. Homestead up, provision"},"comment":{"url":"https://api.github.com/repos/mitchellh/vagrant/issues/comments/139305566","html_url":"https://github.com/mitchellh/vagrant/issues/6068#issuecomment-139305566","issue_url":"https://api.github.com/repos/mitchellh/vagrant/issues/6068","id":139305566,"user":{"login":"ericfrancis","id":1517115,"avatar_url":"https://avatars.githubusercontent.com/u/1517115?v=3","gravatar_id":"","url":"https://api.github.com/users/ericfrancis","html_url":"https://github.com/ericfrancis","followers_url":"https://api.github.com/users/ericfrancis/followers","following_url":"https://api.github.com/users/ericfrancis/following{/other_user}","gists_url":"https://api.github.com/users/ericfrancis/gists{/gist_id}","starred_url":"https://api.github.com/users/ericfrancis/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ericfrancis/subscriptions","organizations_url":"https://api.github.com/users/ericfrancis/orgs","repos_url":"https://api.github.com/users/ericfrancis/repos","events_url":"https://api.github.com/users/ericfrancis/events{/privacy}","received_events_url":"https://api.github.com/users/ericfrancis/received_events","type":"User","site_admin":false},"created_at":"2015-09-10T16:40:28Z","updated_at":"2015-09-10T16:40:28Z","body":"@philbates35 I am having issues.\r\n\r\nWindows 10\r\nVagrant 1.7.4\r\nVirtualbox 5.0.4.102546\r\n\r\n```\r\nPS> vagrant up\r\nBringing machine 'default' up with 'virtualbox' provider...\r\n==> default: Importing base box 'ubuntu/trusty64'...\r\n==> default: Matching MAC address for NAT networking...\r\n==> default: Checking if box 'ubuntu/trusty64' is up to date...\r\n==> default: Setting the name of the VM: eric-vagrant-vm\r\n==> default: Clearing any previously set forwarded ports...\r\n==> default: Clearing any previously set network interfaces...\r\n==> default: Preparing network interfaces based on configuration...\r\n    default: Adapter 1: nat\r\n==> default: Forwarding ports...\r\n    default: 8180 => 8180 (adapter 1)\r\n    default: 22 => 2222 (adapter 1)\r\n==> default: Running 'pre-boot' VM customizations...\r\n==> default: Booting VM...\r\n==> default: Waiting for machine to boot. This may take a few minutes...\r\nThe guest machine entered an invalid state while waiting for it\r\nto boot. Valid states are 'starting, running'. The machine is in the\r\n'poweroff' state. Please verify everything is configured\r\nproperly and try again.\r\n\r\nIf the provider you're using has a GUI that comes with it,\r\nit is often helpful to open that and watch the machine, since the\r\nGUI often has more helpful error messages than Vagrant can retrieve.\r\nFor example, if you're using VirtualBox, run `vagrant up` while the\r\nVirtualBox GUI is open.\r\n\r\nThe primary issue for this error is that the provider you're using\r\nis not properly configured. This is very rarely a Vagrant issue.\r\n```\r\n\r\nOpened up virtualbox and tried to manually start the created vm and got this error:\r\n```\r\nRTR3InitEx failed with rc=-1912 (rc=-1912)\r\nwhere: supR3HardenedMainInitRuntime\r\nwhat:  4\r\nVERR_VM_DRIVER_VERSION_MISMATCH (-1912) - The installed support driver doesn't match the version of the user.\r\n```"}}