How to Fix “Installation Failed: Could Not Create Directory” in WordPress

WordPress needs to create folders when it installs or updates plugins, themes, and core files. If the web-server process cannot write to the required location, the process stops with “Could not create directory.” Low disk space can produce the same symptom.

Do not solve this by setting every folder to 777. That creates a security problem and often hides incorrect ownership.

Check Storage First

Open your hosting dashboard and review disk space and inode usage. A plan can have free megabytes but no available inodes—the entries needed to create more files. Remove obsolete backups or cache files only after confirming they are safe to delete.

Use Site Health

Go to Tools → Site Health → Info → Filesystem Permissions. WordPress should be able to write to the main directory and the relevant wp-content, plugins, themes, and uploads folders.

The failing path in the error message is valuable. If only wp-content/upgrade is affected, focus there instead of changing the entire installation.

Repair Ownership and Permissions

On many Linux hosts, directories use 755 and files use 644, but ownership is just as important. Files copied by a root account or restored under another hosting user may not be writable by PHP.

Ask the host to set the WordPress files to the correct account and web-server group for its platform. Avoid copying a generic chown command from the internet; usernames and server models differ.

Check the Temporary Directory

Uploads and updates may be unpacked in a PHP temporary folder before WordPress moves them. Ask the host to confirm that upload_tmp_dir exists, is writable, and has space. Also check whether a partial folder from a failed installation already occupies the destination.

Retry Carefully

After correcting the cause, clear any safe temporary update files and install one item at a time. If the dashboard installer still fails, download the package from its trusted source and follow WordPress's documented manual installation process.

Finish by checking Tools → Site Health again. Correct ownership should let WordPress update normally without making sensitive files broadly writable.