I know that the GUI is probably virtualbox related, but most of us here use virtualbox here so I though why not ask.

and maybe the console problems were irrelevant to the GUI thing. So therefore I asked this question :)

We can't really help since the program itself doesn't open. Fix that first :)

Working fine here

I've tried fixing the virtualbox problem, but ran out of options / things to google. I'm stuck. and like I said a lot of virtualbox users here maybe one encounterd the same problem. or knows how to fix it. Or get it up and running via console only.

And I know virtualbox works, I have an other computer with it running just fine (other OS though) so that's not the problem.

So you checked event viewer and checked for bugged out processes in task manager?

Tested on fresh OS install?

Didn't do really those things, but I was thinking: I'm almost sure that the vm worked on this computer, and by upgrading vagrant, homestead and virtualbox it stopped working. so i'm thinking that the problem can be that VB wants to load a vm that isn't on my pc and that is causing the problems

Make sure to delete and start fresh. Or at least delete the old one that's making it bug out.

Homestead seems to be badly broken in Windows.

1) Most of the paths are in *nix style

2) The command homestead up fails to run, returning the following error

'vagrant' is not recognized as an internal or external command,
operable program or batch file.

If it's any help, I finally got it to work by following the "Manually Via Git (No Local PHP)" part of the installation guide.

I also downgraded vagrant to 1.6.5 and uninstalled the global homestead, not sure if any of these actions had any part in it working though.

@dugjohnson solution worked for me. but homestead ssh gives this error: "'VAGRANT_DOTFILE_PATH' is not recognized as an internal or external command, operable program or batch file."

using git bash ssh worked though

Info on the "vagrant not recognized" and "VAGRANT_DOTFILE_PATH" not recognized can be found in the comments of this commit https://github.com/laravel/homestead/commit/167135bbac3966be7ac05446c7da0d8bee50c34e and as far as I can tell all is fixed with this PR https://github.com/laravel/homestead/pull/134

Maybe some of you guys can join in the comments, try out the changes in the PR and confirm they fix the issue for you and @TaylorOtwell will accept the PR soon? I suppose he needs to test it out on Linux/Mac systems to make sure it doesn't break something there before he pulls in the changes.

PR #134 does indeed fix all the command problems for homestead. Tested on windows 8.1 64bits.

Hopefully the PR will be accepted soon :)

Finaly fixed it:

first I installed VirtualBox V1.3.12, that one was able to launch the GUI Then trying to start the box, I discoverd that I had missing drivers.

So i did:

C:\Program Files\Oracle\VirtualBox\drivers\USB\filter
Select VBoxUSBMon.inf and click the right mouse button. Then pick Install.
Go to
C:\Program Files\Oracle\VirtualBox\drivers\vboxdrv
Select VBoxDrv.inf and click the right mouse button. Then pick install.

from: https://forums.virtualbox.org/viewtopic.php?f=6&t=46845

and it was fixed!

Just wanted to add, if you have installed homestead via composer you can simply clone git@github.com:maddhatter/homestead.git and copy the files (excluding the git repo) to %APPDATA%\Roaming\Composer\vendor\laravel\homestead.

Fixed the issue for me, from my experience Taylor takes a while to merge PRs for homestead so this will work in the interim.

Solution provided by Rich97 worked for me. Thanks!

OK, looks like Taylor has just updated Homestead to 2.0.9.

I've installed it on Win 8.1 and it appears to be working fine now.

Hello everybody!

I was not sure whether to start new thread or post here, so I'll try here.

Homestead suddenly stopped working on my stationary, I suggest after a power failure (didn't use it for a couple of weeks, and now I can't properly vagrant up it).

As I see in VB GUI the box is actually loaded, BUT Ubuntu itself does not launch: it hangs on menu where user has to choose what to boot:

I tried to completely reinstall all software (VB, Vagrant). Also destroyed Homestead and recreated it. Nothing helps :(