{"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":64,"created_at":"2015-07-31T01:13:51Z","updated_at":"2015-10-05T19:09:42Z","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/145634612","html_url":"https://github.com/mitchellh/vagrant/issues/6068#issuecomment-145634612","issue_url":"https://api.github.com/repos/mitchellh/vagrant/issues/6068","id":145634612,"user":{"login":"philbates35","id":4882082,"avatar_url":"https://avatars.githubusercontent.com/u/4882082?v=3","gravatar_id":"","url":"https://api.github.com/users/philbates35","html_url":"https://github.com/philbates35","followers_url":"https://api.github.com/users/philbates35/followers","following_url":"https://api.github.com/users/philbates35/following{/other_user}","gists_url":"https://api.github.com/users/philbates35/gists{/gist_id}","starred_url":"https://api.github.com/users/philbates35/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/philbates35/subscriptions","organizations_url":"https://api.github.com/users/philbates35/orgs","repos_url":"https://api.github.com/users/philbates35/repos","events_url":"https://api.github.com/users/philbates35/events{/privacy}","received_events_url":"https://api.github.com/users/philbates35/received_events","type":"User","site_admin":false},"created_at":"2015-10-05T19:09:42Z","updated_at":"2015-10-05T19:09:42Z","body":"VirtualBox 5.0.6 has been released, and there's a few reports on the [forum](https://forums.virtualbox.org/viewtopic.php?f=6&t=68590&sid=00dd9931e1130eecf200e6b9bd21f743&start=420#p340737) that using 5.0.6 has resolved their Windows 10 VirtualBox issues.\r\n\r\nI don't have Windows 10 installed yet so I can't test myself, but it would be good to hear if this resolves anyone else's issues with Vagrant / VirtualBox / Windows 10."}}