@Shwheelz No problem, just wanna help. :) Because that was exactly my thought when I was encounter this problem until I saw someone mention about this setting once again that made me realized.

Linux do care about upper and lowercase in file names or folders.

In your Homestead.yaml file: /home/vagrant/code is not the same path as /home/vagrant/Code

After you fix that then use 'vagrant provision' or another command that suits you best to restart vagrant and apply those changes.

Some VM machines will run even without vt-x. but homestead relies on it, I don't know which part. but my guess is the part where it needs to virtualize the network adapter. so yeah, check if you got vt-x enabled.

Alright, so some progress I think. Thanks @ratiw and @zzzcollapsar; it appears BIOS was not configured properly, and it is now. However, I am still unable to access localhost:8000. When I run vagrant up I get the following output. I'm not really sure what to make of it:

C:\laravel_code\Homestead>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'laravel/homestead' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    default: Adapter 2: hostonly
==> default: Forwarding ports...
    default: 80 => 8000 (adapter 1)
    default: 3306 => 33060 (adapter 1)
    default: 5432 => 54320 (adapter 1)
    default: 22 => 2222 (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Connection timeout. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Setting hostname...
==> default: Configuring and enabling network interfaces...
==> default: Mounting shared folders...
    default: /vagrant => C:/laravel_code/Homestead
    default: /home/vagrant/Code => C:/laravel_code
==> default: Machine already provisioned. Run `vagrant provision` or use the `--
provision`
==> default: to force provisioning. Provisioners marked to run always will still
 run.

Then I run vagrant provision, as suggested by cmd

C:\laravel_code\Homestead>vagrant provision
==> default: Running provisioner: shell...
    default: Running: inline script
==> default: stdin: is not a tty
==> default: ssh-rsa [redacted]
==> default: Running provisioner: shell...
    default: Running: inline script
==> default: Running provisioner: shell...
    default: Running: inline script
==> default: stdin: is not a tty
==> default: Running provisioner: shell...
    default: Running: inline script
==> default: stdin: is not a tty
==> default: * Restarting nginx nginx
==> default: ...done.
==> default: php5-fpm stop/waiting
==> default: php5-fpm start/running, process 2267
==> default: Running provisioner: shell...
    default: Running: inline script
==> default: stdin: is not a tty
==> default: php5-fpm stop/waiting
==> default: php5-fpm start/running, process 2300

When I navigate to http://localhost:8000, I get a plain HTML page that displays "No input file specified." I'm not quite sure how to go about troubleshooting this yet.

Additionally, I'd like to mention that the narrator of the Laracasts tutorial mentioned in the original post creates a laravel app in episode 2 (regular installation guide) and then just moves it to the right directory in episode 3 (vagrant/vbox installation guide). I don't have any way to create this app without laravel installed on my computer, so that's another problem in itself.

ok now install laravel. vagrant ssh into the code/project folder.Then composer create-project laravel/laravel

I can't install Composer on my computer due to issues with PHP. At this point, I'm ready to scrap it. I successfully installed WAMP on another computer (Windows 8.1) and just finished installing Composer there, too. I appreciate all of your help, and I'm willing to follow up on this if you guys want to try to solve this problem for future readers. There just seems to be a lot of poorly configured files on my computer from past attempts at installing WAMP and XAMPP and I don't know that it's worth taking up more of your time if I have what I need running on another machine.

Glad that work out.

Anyway, you don't need to run vagrant provision again as it has already been provisioned. You need to run vagrant ssh to get into the vm and install laravel as @fraserk mentioned.

Once you installed Laravel, you will then see the "You've arrived" page.

Oh, by the way, I used to run WAMP and XAMPP as well. But once I get to know Homestead, I never go back to them anymore. Don't give up just yet, believe me. It really worth it and you'll learn a lot once you've overcome this. :)

Git is installed, but vagrant ssh doesn't seem to be working.

C:\laravel_code\Homestead>vagrant ssh
`ssh` executable not found in any directories in the %PATH% variable. Is an
SSH client installed? Try installing Cygwin, MinGW or Git, all of which
contain an SSH client. Or use your favorite SSH client with the following
authentication information shown below:

Host: 127.0.0.1
Port: 2222
Username: vagrant
Private key: C:/Users/Shane/.vagrant.d/insecure_private_key

You're not in your Git shell. There's a special link to launch it!

As @keevitaja mentioned, you will need to run vagrant ssh in Git Shell or Git Bash, NOT from Windows Command prompt (e.g. cmd.exe).

I use windows, this is what I do. It works perfectly without any issue

• Download http://bliker.github.io/cmder/ ( Best terminal for windows )
• Create a folder with name www in your c: or d: drive
• Clone laravel/homestead in www folder
• Clone laravel in lv folder ( that is c:\www\lv ) in cmder use this command composer create-project laravel/laravel --prefer-dist lv
• Generate rsa keys using putty !! IMPORTANT
• Open Homestead.yaml
• Edit the file as given below

---
ip: "192.168.10.10"
memory: 2048
cpus: 1

authorize: C:/Users/YOUR-USER/.ssh/id_rsa.pub

keys:
    - C:/Users/YOUR-USER/.ssh/id_rsa

folders:
    - map: C:/www/lv
      to: /home/vagrant/lv

sites:
    - map: app.dev
      to: /home/vagrant/lv/public

variables:
    - key: APP_ENV
      value: local

• Edit host file C:\Windows\System32\drivers\etc\hosts and add 127.0.0.1 app.dev there
• Open cmder and visit c:\www run vagrant up command
• Visit http://app.dev:8000 in your browser

That's all and well if your network or BIOS is setup properly.

I successfully created the app with the git shell, but localhost:8000 is still displaying "No input file specified" even after vagrant up

Have you tried http://learn.app:8000

Thank you @abhimanyusharma003! I've just successfully installed Homestead on my home Windows 8.1 computer by following your checklist.

Some notes: I already had a ssh key for SourceTree however that didn't work as PuttyGen didn't generate the id_rsa file for me. But by using the full Cmder (with Git) I had the option to just run ssh-keygen -t rsa -C "your@email.com" and that generated the proper keys.

This is my homestead.yaml now:

---
ip: "192.168.10.10"
memory: 2048
cpus: 1

authorize: C:/Users/[...]/.ssh/id_rsa.pub

keys:
    - C:/Users/[...]/.ssh/id_rsa

folders:
    - map: C:/www/
      to: /home/vagrant/www

sites:
    - map: test.dev
      to: /home/vagrant/www/test 
    - map: sandbox.dev
      to: /home/vagrant/www/sandbox/public

variables:
    - key: APP_ENV
      value: local

And in my hosts file I've added:

192.168.10.10 sandbox.dev

So, that way I can just visit http://sandbox.dev/ instead of http://sandbox.dev:8000/. Or does that cause unforeseeable trouble down the line?

I was surprised it went without a hitch! :-) But then again, I only am showing the homepage as of now.

I was having the same issue as Shwheelz, but my issue had 2 parts:

1. Forgetting to put a laravel project in the code directory for learn.app to go to.

2. Forgetting Linux cares about capitalization in folders (my path was code\Laravel\public instead of code\laravel\public).

Once I fixed that it worked great. Just thought I'd through that out there for any newcomers who run into the same issue.

@FrankPeters good to know that you installed homesetad successfully.

I will give try to 192.168.10.10 sandbox.dev in host file, personally I have no issue using port 8000 in browser urls.

I'm having the exact same issue as @Shwheelz, still no solution.

I'm new to Laravel. Search Laravel + Windows drive me to this and no solution. Try Laragon to solve your issue in Windows. or Phansible or Vagrobash if you want to tame PHP stack.

@reinvent "no solution".

There are actually several solutions in this thread, each of them specific to different users who posted and all of them from user error.

For example, virtualization support not enabled in bios, forgot to install Laravel to code folder, folder naming case sensitivity issues and so on.

But thanks for necroing a 4 month old thread :)