A failed WordPress update is usually recoverable. First make a restorable backup of the database and all site files. If visitors see the scheduled-maintenance message, remove the stale .maintenance file from the WordPress root. If the dashboard update still fails, use the official manual update sequence, complete the database upgrade when prompted, and use Recovery Mode for a fatal error or white screen. Permission, PHP, memory, execution-time, and server-connection problems may require your host or a developer; restore a known-good backup rather than repeatedly retrying a broken installation.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
Start with a symptom and access check
Do not keep clicking “Update” until you know what failed. The visible symptom tells you which part of WordPress is reachable and which recovery method is safest.
As an Amazon Associate I earn from qualifying purchases.
| What you see | Likely first action | Access needed | What the action changes | When to escalate |
|---|---|---|---|---|
| “Briefly unavailable for scheduled maintenance” or a failed-update notice after the update stopped | Delete the stale .maintenance file, then retry once |
FTP, host file manager, or shell | Clears a maintenance marker only; it does not repair the update | If the file is absent, returns immediately, or other errors appear |
| Dashboard cannot download or install the update | Check outbound connectivity, write access, ownership, and permissions | Dashboard first; FTP/file manager or host support for server checks | May change server permissions or ownership | When you cannot safely change permissions or the host blocks connections |
| One-click update repeatedly fails but the site still loads | Perform the official manual update | FTP/file manager or shell plus administrator dashboard | Replaces WordPress core files and may update the database | Before replacing files if no verified backup exists |
| White screen, fatal PHP error, or inaccessible dashboard after updating | Open the Recovery Mode link from the administrator email and isolate the named plugin or theme | Administrator email and dashboard; FTP if no email arrives | Pauses the suspected component for your administrator session | For persistent errors, missing access, or server-level PHP failures |
| Site remains broken after file and plugin checks | Restore matching files and database from a known-good backup | Host backup tools or technical administrator | Reverts content and code to the backup point | Ask the host or a qualified developer if you cannot verify the restore |
A backup is not “ready” merely because a plugin reported success. Confirm that both the database and files are included and that the backup can actually be restored before you alter the installation.
1. Make a restorable backup before retrying
WordPress’s update guidance recommends backing up the website before an update, and its plugin and theme auto-update guidance recommends regular automatic backups so a rollback is possible. For this recovery, preserve two separate parts:
- Database: posts, pages, settings, users, orders, and other content stored in MySQL or MariaDB.
- Files: WordPress core,
wp-content(including plugins, themes, and uploads), and configuration files such aswp-config.php.
Download or snapshot both parts to storage independent of the web server. Record the backup time and the WordPress, PHP, plugin, and theme versions it contains. Test restoration on a staging site or another safe location when possible. A database-only export cannot restore missing uploads or a damaged theme, while files without the matching database may produce an inconsistent site.
If the site is already serving errors, take the backup before deactivating plugins or replacing files, provided the host can create it without making the outage worse. If your host supplies a point-in-time snapshot, ask whether it includes the database, files, and the PHP version that ran the site.
Recommended Free Tools
2. Remove a stale maintenance file
During an update, WordPress creates a hidden file named .maintenance in the installation’s root directory. A process that stops before cleanup can leave that marker behind, causing visitors to see “Briefly unavailable for scheduled maintenance. Please check back in a minute.”
Find the correct WordPress root
Use the directory that contains wp-admin, wp-includes, and wp-content. On some hosts it is public_html; on others it is a subdirectory or a document-root folder. Do not delete a similarly named file from an unrelated site in the same account.
Delete the marker with your available access
- Open an FTP client or your host’s file manager, enable viewing of hidden files, and navigate to the WordPress root.
- Locate
.maintenanceand delete only that file. With shell access, change to the verified root and runrm .maintenance; do not run a recursive delete command. - Load the public site and
/wp-adminin a private browser window. If they open, inspect the dashboard for an incomplete update notice. - Take or verify the backup, then retry the update once.
Deleting .maintenance only removes the stale maintenance state. It does not fix a failed download, unwritable directory, incompatible PHP version, exhausted memory, or a broken plugin. If the message returns immediately, stop repeating the deletion and investigate the underlying failure.
3. Diagnose a dashboard update that will not download or install
Check outbound connectivity
A download can fail because the server cannot reach the WordPress update service, DNS is failing, a firewall is blocking outbound HTTPS, or the connection times out. Retry after a transient network interruption, but treat repeated failures as a host-level connectivity issue. Ask the host whether outbound connections from the web-server process are allowed and whether any firewall, proxy, or DNS change is affecting them.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Check write access and ownership
If WordPress repeatedly asks for FTP or connection credentials, the web-server process may not be able to write the WordPress directory. Ownership and permissions are separate: a directory can have permissive mode bits yet belong to the wrong system user, or be owned correctly but deny writes.
Compare the owner and group of the WordPress files with the account used by the web server. Correct them through the host’s documented control panel or with a qualified administrator; do not apply a broad, permissive setting to the entire server. Make sure the temporary directory and the destination directories are writable for the duration of the update, then return to the host’s least-privilege policy.
Rank #3
Separate a download problem from a file-replacement problem
A message about downloading, unpacking, or connecting points to a different remedy than an error that appears while replacing files. Note the exact dashboard text and the point at which it stops. Preserve that message for the host or developer instead of reporting only that “the update failed.”
4. Use the official manual update path
Manual updating is the recovery route when one-click updating cannot complete. Use the WordPress release that matches the version you intend to run, and keep the backup available until the public site and dashboard have been checked.
Prepare the files
- Download the matching WordPress release from the official WordPress distribution source using a trusted computer.
- Confirm that the archive is complete before uploading it. Keep your existing
wp-contentdirectory,wp-config.php, and any server-specific files outside the distributed core set. - Temporarily deactivate all plugins from the dashboard. If the dashboard is unavailable, rename plugin folders only as a temporary troubleshooting measure and record each change so it can be reversed.
Replace core files, not site content
- Remove the old
wp-admindirectory and replace it with the new one. - Remove the old
wp-includesdirectory and replace it with the new one. - Replace the distributed WordPress files in the installation root, while retaining
wp-config.php,wp-content, and other files that belong to your site rather than WordPress core. - If this follows a failed automatic upgrade, remove the stale
.maintenancefile from the root. - Visit
/wp-admin. If WordPress displays a database-upgrade prompt that usesupgrade.php, complete it immediately and wait for confirmation. - Sign in, check the dashboard and public pages, and reactivate plugins one at a time. Test the site after each activation so a new failure can be attributed to a specific component.
The manual procedure replaces distributed core files. Any edits made directly to those files will be overwritten. Keep custom code in a plugin or child theme and retain the backup for rollback. Never copy an old, modified core file over the new release simply to preserve an unsupported edit.
5. Recover from a fatal error or white screen
WordPress Recovery Mode, introduced in WordPress 5.2, can help regain access when a fatal PHP error occurs during a normal page load. WordPress sends the administrator an email containing a Recovery Mode link when it detects a qualifying fatal error.
Use the Recovery Mode session
- Open the link in the administrator email on the same site.
- Sign in when prompted. Recovery Mode pauses the suspected plugin or theme for your administrator session, allowing the dashboard to load while ordinary visitors may still see the failure.
- Read the dashboard notice identifying the component and the PHP error. Update, configure, replace, or deactivate that component as appropriate.
- Exit Recovery Mode and test both the public site and the dashboard in a fresh browser session.
Pausing a component is not the same as repairing it. Check whether the plugin or theme version supports your current WordPress and PHP versions, and restore its previous version or a backup if the newer release is the trigger.
If no Recovery Mode email arrives
Check the administrator mailbox, spam filtering, and the address stored in WordPress. If you still cannot enter the dashboard, use the documented FTP or file-manager method to identify a faulty plugin folder, and enable WordPress debugging only under controlled conditions so error details are not exposed to visitors. Contact the host if PHP errors occur before WordPress can load or if you cannot safely access the files.
6. Handle PHP, memory, execution-time, and server limits
Some failed updates are not fixable from the dashboard. WordPress troubleshooting guidance identifies connection glitches, incorrect permissions, memory limits, maximum execution time, and PHP compatibility as separate causes.
- PHP compatibility: A core, plugin, or theme update may require a PHP version different from the one currently enabled. Ask the host which PHP versions are supported by the target WordPress and extensions before switching.
- Memory limit: A large site or complex plugin can exhaust PHP memory while unpacking or activating files. The host may need to raise the limit or identify a component consuming excessive memory.
- Maximum execution time: A slow or resource-heavy update can time out before cleanup. The host can inspect server logs and adjust the limit where appropriate.
- Filesystem restrictions: Containers, security modules, read-only mounts, or incorrect ownership can prevent replacement even when dashboard credentials are correct.
- Connection failures: Firewall, DNS, TLS, proxy, or temporary network problems can stop downloads before any files are changed.
Do not change PHP versions or server limits on a live site without a backup and a rollback plan. A PHP change can affect whether a backup will run; when restoring, the host may need to return the previous PHP version before the site works as it did at the backup point.
7. Restore a known-good backup when repair is riskier than rollback
Restore when core files are inconsistent, the database upgrade failed, repeated attempts have made the symptoms less clear, or the site is losing business while diagnosis continues. Restore the files and database from the same known-good point whenever possible. Restoring only one side can leave mismatched code and data.
- Put the site behind a maintenance page or otherwise prevent writes while restoring.
- Record the current state, including the failed version, PHP version, error messages, and any new orders or comments that must be preserved separately.
- Restore the backup’s files and database using the host’s verified procedure.
- Confirm the PHP version and required extensions match the restored site.
- Test the public site, login, media, forms, scheduled tasks, and key transactions before reopening it.
- Plan the update again on staging or during a maintenance window, one component at a time.
If you cannot verify that the backup is complete or restorable, ask the hosting provider for a snapshot and restoration test. A qualified WordPress developer is appropriate when you lack safe file access, cannot change ownership or PHP settings, or need to reconcile database changes made after the backup.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match8. Prevent the next failed update
- Keep scheduled WordPress backups that include both database and files, and periodically perform a test restore.
- Update core, plugins, and themes in a controlled order rather than changing everything simultaneously.
- Use staging for major version changes and verify the PHP version before updating.
- Keep direct core-file customizations out of the update path; use plugins or a child theme.
- Record the last known-good versions and maintain host access details before enabling automatic plugin or theme updates.
- Monitor administrator email so Recovery Mode messages and update failures are seen promptly.
WordPress’s update documentation states that you should always update WordPress to the latest version, but “latest” is safest when the site has a tested backup, compatible PHP, writable files, and a rollback plan.
Frequently Asked Questions
Will deleting .maintenance fix every failed WordPress update?
No. It only clears a stale maintenance marker left in the WordPress root. Download, permission, PHP, memory, execution-time, and plugin errors need their own remedies.
What if the site breaks again immediately after a manual update?
Use Recovery Mode if WordPress sends the administrator link, isolate the named plugin or theme, and restore the matching files and database from a known-good backup if the fault persists.
Should I change PHP versions to make an update work?
Only with a verified backup and a rollback plan. Confirm compatibility with your host first; a PHP change can require the host to restore the previous version during rollback.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
