Home » Php » frameworks – Why "no such file or directory … autoload.php" when accessing Laravel app?

frameworks – Why "no such file or directory … autoload.php" when accessing Laravel app?

Posted by: admin April 23, 2020 Leave a comment


I am a newbie to Laravel, have been trying to install Laravel, wasted three hours unfortunately didn’t work. When I access through public directory, I get these errors:

Warning: require(C:\wamp\www\laravel\bootstrap/../vendor/autoload.php): failed to open stream: No such file or directory in C:\wamp\www\laravel\bootstrap\autoload.php on line 17
Call Stack

And the following:

Fatal error: require(): Failed opening required ‘C:\wamp\www\laravel\bootstrap/../vendor/autoload.php’ (include_path=’.;C:\php\pear’) in C

How to&Answers:

Did you install Laravel’s dependencies? When you unzip the framework in your work environment (i.g. htdocs) you must install the necesary dependencies with the command php composer.phar install (assuming you have installed composer and git). When that is done, you will be able to see the home page of the framework.


I had same problem on Windows(Also works for Mac).


  1. Install composer
  2. Open cmd
  3. Navigate to your laravel application root
  4. Run composer install command in cmd



This message occurs for Laravel’s dependencies.
If never run composer install in your project then run this command on the terminal.
Else run composer update --no-scripts. All Laravel dependencies will download.


To get around this problem, doing a composer self-update would do the trick. Moreover, as long as the composer command itself works in your command-line/bash (which means you have it in your PATH) you don’t necessarily need to go the actual path where composer.phar resides in (i.e. c:/ProgramData/Composer/bin or whatsoever).


Your Laravel installer is giving an error.

Do composer global require "laravel/installer"

Then the new Laravel installer will be installed. Your new Laravel will not return an error then.


if you are migrating the project,try to delete composer.lock and then composer install .this worked for me!


This error indicates it can not find “autoload.php” under the vendor folder.

Make sure the vendor folder is generated by running the “composer install” command and the autoload.php file also created.


In Windows CMD I faced similar issue and fixed with this command below. After clone a laravel project from my git repository, there was no /vendor directory (logically). This below command creates fresh new /vendor directory and appropriate autoload.php file inside it.

composer update --no-scripts


Just make your storage folder writable. This can be found in your app directory

In your terminal use this command

chmod +w <directory> or chmod a+w <directory>

Make sure you navigate to the directory containing the directory you want to make writable or you point to that path.