When a WordPress update fails during a core, plugin, or theme change, first identify whether the failure came from files, server limits, or the update package. This guide focuses on recovering from an interrupted update safely.
You may see messages such as “Update failed”, “Installation failed,” “Could not copy file,” “Download failed,” or “An automated WordPress update has failed to complete.”
In many cases, the problem is caused by file permissions, insufficient disk space, PHP limits, a plugin conflict, an interrupted connection, or a hosting configuration that prevents WordPress from writing new files.
Before retrying the same update repeatedly, identify where the update process is failing.
QUICK ANSWER
If a WordPress update fails, create a backup first. Then clear any stuck maintenance state, check available disk space, verify file ownership and permissions, temporarily disable security or caching plugins, check PHP memory and execution limits, retry the update individually, and review your server logs. If WordPress still cannot replace its own files, ask your hosting provider to verify file ownership or perform a careful manual update.
Why Do WordPress Updates Fail?
A WordPress update normally has to:
- connect to the update server,
- download the update package,
- extract the files,
- place the site into maintenance mode when necessary,
- replace or modify files,
- complete any database changes,
- and return the site to normal operation.
A failure at any of those stages can produce a different error message.
Common causes include:
- incorrect file ownership or permissions,
- insufficient disk space,
- PHP memory exhaustion,
- execution timeouts,
- security or firewall restrictions,
- a broken plugin or theme package,
- an interrupted connection,
- a stuck maintenance file,
- or a hosting-level problem.
The exact error message is often the best clue.
1. Back Up WordPress Before Trying Again
Do not repeatedly restart a failed update without first protecting the working parts of your site.
Create a current backup of:
- your WordPress database,
wp-content,- themes,
- plugins,
- uploads,
- and important configuration files.
If your host provides automatic backups or snapshots, verify that a recent restore point actually exists.
This is especially important before:
- manually replacing WordPress core files,
- changing PHP versions,
- editing permissions,
- or updating several major plugins at once.
A backup gives you a safe recovery point if the failed update leaves the site unusable.
2. Check for a Stuck .maintenance File
WordPress temporarily uses maintenance mode while certain updates are running.
Normally that state disappears automatically.
If the update is interrupted, a temporary file named:
.maintenancemay remain in the WordPress root directory.
You may then see:
“Briefly unavailable for scheduled maintenance. Check back in a minute.”
Open your hosting file manager or connect using FTP/SFTP.
Go to the directory containing:
wp-admin,wp-content,wp-includes,- and
wp-config.php.
If the update has clearly stopped but .maintenance remains, remove that temporary file and reload the website.
Then return to:
Dashboard → Updates
and verify which component actually failed.
If the site repeatedly remains in maintenance mode, see our WordPress Stuck in Maintenance Mode? 7 Fixes guide.
3. Check Disk Space and Hosting File Limits
An update requires temporary storage for the downloaded package and extracted files.
If your hosting account is almost full, WordPress may be unable to complete the update.
Open your hosting control panel and check:
- available disk space,
- storage quota,
- inode or file-count limits,
- temporary storage,
- and backup usage.
Common space-consuming items include:
- old backups,
- staging sites,
- large cache directories,
- unused media,
- debug logs,
- and old migration archives.
If storage is full, remove only files you recognize or use your host’s storage-management tools.
Do not randomly delete WordPress core files to free space.
After freeing sufficient space, clear temporary caches and retry only the failed update.
4. Check File Ownership and Permissions
WordPress must be able to write to the files and directories involved in an update.
If it cannot replace a file, you may see messages such as:
“The update cannot be installed because some files could not be copied.”
or:
“Could not copy file.”
On many Linux-based WordPress hosting environments, commonly used permission values are:
- 755 for directories,
- 644 for files.
However, permissions alone are not the whole issue.
The files must also have ownership that works correctly with your web server and hosting configuration.
If WordPress unexpectedly asks for FTP credentials during updates, that can also indicate that WordPress cannot write directly to the required files.
Do not change everything to 777. That creates unnecessary security risk and may not correct an ownership problem.
If you are unsure, ask your hosting provider to verify:
- WordPress file ownership,
- directory permissions,
- the web-server user,
- and whether WordPress has permission to modify its own installation.
5. Temporarily Disable Security, Cache, and Update-Related Plugins
A plugin can interfere with WordPress updates by blocking requests, protecting files, changing filesystem behavior, or consuming excessive resources.
Plugins worth testing include:
- security plugins,
- firewall plugins,
- caching plugins,
- maintenance plugins,
- backup plugins,
- file-protection plugins,
- and plugins that manage automatic updates.
If the problem began immediately after a plugin was installed or updated, deactivate that plugin first.
Then retry one update.
If You Cannot Access wp-admin
Use your hosting file manager or FTP/SFTP and navigate to:
/wp-content/plugins/Temporarily rename the suspected plugin directory.
If you cannot identify a specific plugin, you can temporarily rename the main:
pluginsdirectory to:
plugins-disabledto test whether a plugin conflict is involved.
Restore the original folder name after testing.
Do not leave security or caching plugins disabled permanently unless you have identified a genuine conflict.
6. Check PHP Memory and Execution Limits
Updates use PHP resources to download, extract, copy, and process files.
If PHP runs out of memory or reaches an execution limit, the update may stop before completion.
Go to:
Tools → Site Health → Info → Server
Review values such as:
- PHP memory limit,
- PHP version,
- maximum execution time,
- and server information.
You can also check your hosting PHP configuration.
If your logs contain:
Allowed memory size exhaustedthe update may be failing because PHP does not have enough memory to complete the process.
See our WordPress Memory Exhausted Error? 7 Fixes guide.
If the entire server begins returning temporary availability errors while the update runs, investigate hosting resources as well.
See our WordPress 503 Service Unavailable? 8 Fixes guide.
7. Update One Component at a Time
If several plugins, themes, and WordPress core all require updates, avoid updating everything simultaneously while troubleshooting.
Update one item at a time.
A practical order is:
- create or verify your backup,
- update one plugin,
- test the website,
- update the next plugin,
- test again,
- update themes as needed,
- then perform the WordPress core update when appropriate.
This makes it much easier to identify the component that causes the failure.
If one plugin repeatedly fails while every other update works, focus on that plugin rather than changing your entire server configuration.
You can also try deleting and reinstalling the plugin from a trusted source if its package or existing files are damaged.
Before deleting a plugin, confirm whether it stores important settings or files outside the database and make sure you have a backup.
8. Use a Manual WordPress Update When the One-Click Update Fails
If WordPress core cannot update through the dashboard but the website and hosting environment are otherwise stable, a manual core update may be appropriate.
Back up your website first.
Download a clean copy of WordPress from the official WordPress website.
Using FTP/SFTP or your hosting file manager, replace the appropriate WordPress core files carefully.
Do not overwrite or delete your:
wp-config.phpand do not replace your entire:
wp-contentdirectory with an empty copy.
Your wp-content directory contains your themes, plugins, and uploaded content.
After the new core files are in place, open:
/wp-admin/WordPress may ask you to complete a database upgrade.
Then:
- clear all caches,
- test the homepage,
- test wp-admin,
- check several posts,
- and verify plugins and themes.
A manual update can restore WordPress, but it does not automatically fix incorrect server permissions. If future automatic updates continue failing, investigate file ownership with your host.
Why Does WordPress Say “Could Not Copy File”?
This error usually means WordPress downloaded or began processing the update but could not write one of the required files.
Possible causes include:
- incorrect permissions,
- incorrect file ownership,
- insufficient disk space,
- a locked file,
- security software,
- or a hosting filesystem problem.
The error message may identify the exact file that could not be copied.
That information is useful when contacting hosting support.
Tell them the exact filename rather than only saying that the WordPress update failed.
Why Does WordPress Ask for FTP Credentials During an Update?
WordPress may request FTP or filesystem credentials when it cannot directly modify the files required for the update.
This often relates to the way the hosting server handles file ownership and permissions.
Do not enter unknown FTP credentials or use credentials from an unrelated account.
If WordPress previously updated normally and suddenly begins requesting credentials, ask your host whether:
- file ownership changed,
- the site was migrated,
- permissions were reset,
- or the server’s PHP/web-user configuration changed.
Why Do Plugin Updates Fail but WordPress Core Updates Work?
If WordPress core updates successfully but one plugin does not, the entire WordPress installation is probably not unable to update.
Check the specific plugin for:
- license or subscription requirements,
- download-server problems,
- file permissions in its directory,
- a damaged plugin package,
- insufficient disk space,
- or a plugin-specific compatibility problem.
Premium plugins may obtain updates from their developer’s server rather than WordPress.org.
If that external service is unavailable or your license is invalid, only that plugin’s update may fail.
Why Does an Update End With a 500 Error?
If the update starts normally but ends with an HTTP 500 response, check your PHP and server error logs.
The update may have triggered:
- a PHP fatal error,
- memory exhaustion,
- a plugin conflict,
- or a server configuration error.
See our WordPress 500 Internal Server Error? 8 Fixes guide for that specific error.
Can a Failed WordPress Update Break the Website?
Yes.
If only part of the required files are replaced, WordPress may contain files from different versions.
Symptoms can include:
- a blank page,
- a critical error,
- HTTP 500 errors,
- wp-admin not loading,
- plugin errors,
- or missing functions.
Do not immediately reinstall unrelated plugins.
First determine whether the failed update left WordPress core incomplete.
If you see a critical error after an update, see our WordPress Critical Error? 9 Fixes guide.
How to Reduce Future WordPress Update Problems
Once the site is working again, reduce the chance of another failed update.
- Keep a current backup.
- Maintain adequate free disk space.
- Remove abandoned plugins and themes.
- Use supported PHP versions.
- Keep file ownership consistent.
- Avoid modifying WordPress core files.
- Update important components regularly.
- Test major changes on staging when possible.
- Do not update many critical components at once on an important production site.
Reliable updates depend on both WordPress and the hosting environment being able to safely replace files.
Final Checklist
If a WordPress update fails, check these items in order:
- Create or verify a full backup.
- Remove a stuck maintenance state if necessary.
- Check available disk space and file limits.
- Verify file ownership and permissions.
- Temporarily test security and caching plugins.
- Check PHP memory and execution resources.
- Update one component at a time.
- Use a careful manual WordPress core update when necessary.
If manual updates work but automatic updates consistently fail, do not simply repeat the manual process forever. Ask your hosting provider to verify the filesystem ownership and permissions so WordPress can update safely in the future.