@antonybudianto VirtualBox just released a temp fix - https://www.virtualbox.org/ticket/14040

@BEIDevs , how to apply the patch?

Thanks @BEIDevs it works! @antonybudianto you have to download VBox-Win 10-fix-14040.exe and running it in background during your VM setup.

@luismec90 , The exe didn't work on my machine, maybe the exe is 64-bit (my Windows 10 is 32-bit)

finally get it worked, my state:

• Windows 10 x86
• Vagrant 1.7.4
• VirtualBox 4.3.12, not 5.0.0
• the port-forwarding hack works too. really need the update on the virtualbox.

The solution in the accepted answer worked for me too!

I have a question for the port 8000 required in the address bar:

According to the lesson on Homestead 2.0, Jeffrey uses the IP address from the Homestead.yaml file in his etc/hosts file, and when he goes to the address (example: homestead.app), he doesn't have to attach the port (8000).

When I try to add the IP address from the Homestead.yaml file in my etc/hosts file on Windows, I don't get to my app, I get connection refused error or something similar. The fix is to change the IP address to 127.0.0.1 instead of 192.168.10.10 in the etc/hosts file!

When I have the localhost IP address in the etc/hosts file, it's mandatory that I have to attach the port (homestead.app:8000) in my address bar.

What's the difference between Windows And MacOS in this part? I am guessing it should be the same but it's not for some reason.

I can live with the port attached in my address bar but I am just curious about the differences and if there's something that I can do for it to work!

i solved my problem to that answer, but when I access homestead url from browser, web page not available. must append port 8000 to access "http://site.com:8000". how can I access my url without append port 8000?

forward your host port from 8000 to 80 (change it from virtualbox network setting, portforwarding button), and it works

The problem I have is that I don't have any Host-only Network in VirtualBox and it doesn't let me create one (it throws me the E_FAIL (0x80004005) error. I'm pretty much screwed now. Maybe I'll get fired, who knows...

Been stuck with this for the last 3 days. Downloading VirtualBox 5 now

With the temporary fix @BEIDevs mentioned, I was able to add a Host-only network in VirtualBox, but it disappears as soon as I click OK or close the window.

@pdcmoreira its a temp fix so consider using the marked answer works best

@Mwaa As I said, the marked answer didn't work for me because step 6. assumes that you already have a Host-only network there. I didn't so I had to create one, which didn't work. But I think it is going to work with another method, I'll report back in just a sec.

I found a VERY SIMPLE way to make it work without touching any file in the accepted answer!

1. Install and run this file: https://www.virtualbox.org/attachment/ticket/14040/VBox-Win10-fix-14040.exe (leave it running in the background)
2. Go to the C:\Program Files\Oracle\VirtualBox folder, right click on VirtualBox.exe, go to compatibility, check the "Run in compatibility mode" checkbox and choose Windows 7. Click OK to close the window.
3. Repeat step 2. for VBoxManage.exe and VBoxHeadless.exe
4. Run cmd and do homestead up.

There you go! It should work!

After all is done and working, close the program opened in step 1.

[UPDATED]

You don't need to run cmd as Administrator in step 4.

@pdcmoreira Did also the same thing as your steps above and it worked well. Hope a complete fix is released soon cause its a hustle to keep opening 2 setups to get it working

Link for RC1 http://dlc-cdn.sun.com/virtualbox/5.0.0_RC1/

It would be cool if @Eldair could add my steps as a second method to the accepted answer, otherwise they will get lost through the pages.

Hi I've just updated to windows 10 and have this same problem. I've tried the recommended fix, updated the scripts but I'm still unable to get homestead box to work.

I've tried the work around by @pdcmoreira and I've been able to get homestead up and can ssh into the the machine. However my site is not working - I simply get a white screen. I've check the logs but nothing happening there.

I'm losing days on this problem and want to avoid using wamp but possibly my only solution?

Any one know how long before a stable fix is released or other work arounds?

Ta

@longestdrive Did you combine the fixes of @Eldair and @pdcmoreira ? If yes, maybe try to reverse the first one.

I only used pdcmoreira's fix and everything works like before.

I've also applied my "fix" in my home PC after upgrading to Windows 10 and it works! I didn't even update VirtualBox nor homestead/vagrant, so it seems that it also works on previous versions. If you did the steps by @Eldair , undo them before applying mine.

Still not a perfect solution, just do a vagrant halt, and can not up the vagrant anymore, I need to uncomment the 3rd step line, and it works again

Just installed the latest test build from https://www.virtualbox.org/wiki/Testbuilds

Everything is working without changing any files or using the fix.

My VirtualBox version: 5.0.1 r101939

Hi @bluesheep , looks like it's still not working on my machine, though the error is different now:

The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'poweroff' state. Please verify everything is configured
properly and try again.

I've been able to get Homestead up and running after a day of troubleshooting with the following steps:

Installed the VirtualBox 5.0.1 test build https://www.virtualbox.org/download/testcase/VirtualBox-5.0.1-101902-Win.exe Information at: https://www.virtualbox.org/ticket/14040

I also reinstalled Vagrant 1.7.4

This solved the initial issue with VirtualBox, but presented another issue. When I attempted to "vagrant up" I would get a pop-up error message from VirtualBox about not being able to rename the connection, the VM wouldn't boot, and I would get the error message that @antonybudianto posted in terminal.

I applied a suggestion made by Venimus in this thread: https://github.com/mitchellh/vagrant/issues/6059

I edited line 17 in /Homestead/scripts/homestead.rb as follows:

config.vm.network "private_network", ip: "192.168.10.10", name: "VirtualBox Host-Only Ethernet Adapter #3"

Apparently the trick is to include the name of the host-only adapter that you've already set up in VirtualBox. By doing this, you prevent Vagrant from attempting to rename the connection. You just need to make sure that the name matches the name of your adapter in Windows. Also, go into the VirtualBox GUI and make sure that the host-only adapter is on the same network, but not the same ip. My homestead is 192.168.10.10, my VirtualBox host-only adapter is set to 192.168.10.9.

This seems to be working well for me, and has the advantage of not changing your Vagrant install at all. It's a Homestead-only modification.

Still not working, now trying to reinstall my vagrant, thanks anyway @zackward

@antonybudianto Have you tried starting the box from the VirtualBox GUI? It might give you a better idea of the reason for the box entering an invalid state.

I did that steps, it works fine:

https://github.com/mitchellh/vagrant/issues/6068#issuecomment-127233545

Hello, @pdcmoreira I can include your steps into accepted post or set it as accepted, even though I haven't tried it, it is easier solution (: Is virtualbox 5.0.1 now working correctly? I don't wish to update/loose my currently working setup if it's not completely ready :/

@Eldair it worked fine! Thanks :) But now i'm with problems on the NFS, any idea?

@Eldair just include it as an alternative method, people may still prefer yours. Or even for future reference. I haven't tried VirtualBox 5.0.1 yet, but I hope it's fixed.