Troubleshooting · Troubleshooting
Fix 'Another Update Is Currently in Progress' in WordPress
Short answer
WordPress shows 'Another update is currently in progress' when a core update lock is still set in the database. The lock, named core_updater.lock, normally clears itself after 15 minutes. If the message stays longer, delete that one option with WP-CLI or phpMyAdmin, then run the update again from Dashboard > Updates.
Key takeaways
- WordPress sets a core_updater.lock option for 15 minutes during a core update, and the message means that lock is still set.
- Waiting 15 minutes clears most stuck locks with no action needed.
- WP-CLI removes the lock with wp option delete core_updater.lock, but only after you confirm no update is running.
- In phpMyAdmin, delete only the core_updater.lock row from the wp_options table.
- A lock that returns after every update points to a PHP timeout, a permission problem, or a full disk.
- The maintenance message comes from a .maintenance file, not the lock, and needs a different fix.
What does “Another update is currently in progress” mean?
It means WordPress has set a core update lock, so it refuses to start a second core update while the first one is still running.
WordPress stores the lock as an option named core_updater.lock in the database. The Core_Upgrader class reference shows the lock is created with a 15-minute timeout, and the mechanism dates back to WordPress 2.8.0.
The message is a safety feature, not a broken site. Two core updates writing files at the same time could leave WordPress half updated, so the lock blocks the second one until the first finishes or the lock expires.
Why does the update lock get stuck?
The lock usually gets stuck because the first update stopped halfway, often when PHP hit a time limit, the browser tab closed, or the server connection dropped.
When an update ends cleanly, WordPress deletes the lock. When the process dies first, nothing removes it, so the lock stays until its 15-minute timeout passes, according to the Make WordPress Hosting handbook.
Common causes, most likely first:
- A PHP time or memory limit kills the update mid-run.
- The browser tab closes during a dashboard update.
- The network connection drops while files are downloading.
- The server runs out of disk space or restarts mid-update.
- A background automatic update is still running.
Kinsta's error guide notes the message often appears during automated core security updates, so the lock may be set even when you did not start an update yourself. See the Kinsta guide to common WordPress errors.
If the message returns after every update, the cause is usually a server limit, not the lock itself. That pattern points to a timeout or a file permission problem that stops updates from finishing.
How long should you wait before doing anything?
Wait 15 minutes from the time the update started, then reload Dashboard > Updates and try again.
The lock expires on its own after 15 minutes, and the next update attempt clears it and takes a fresh lock, according to the Make WordPress Hosting handbook. Waiting costs nothing and is the safest first step.
Do not start a second update from another tab or device while you wait. A second attempt cannot run anyway, and it may set a fresh lock if the first update is still alive.
| Lock or file | Where it lives | What it does |
|---|---|---|
core_updater.lock | wp_options table | Blocks a second core update for 15 minutes |
auto_updater.lock | wp_options table | Blocks a second automatic update in the background |
.maintenance | WordPress root folder | Shows the maintenance message; WordPress ignores it after 10 minutes |
How do you clear the lock with WP-CLI?
If you have SSH access, run wp option delete core_updater.lock from the WordPress root folder to remove the lock at once.
The WP-CLI reference for wp core update says to run this command only after you check that no update is actually running.
- Connect over SSH and change to the folder that holds
wp-config.php. - Run
wp option get core_updater.lockto check whether the lock is still set. - Run
wp option delete core_updater.lock. - Run
wp core updateto retry the update from the command line.
The wp option delete reference shows the success message reads “Success: Deleted 'core_updater.lock' option.”
If the update stalls again, the Make WordPress Hosting handbook recommends forcing a re-run of the same version with wp core update --version=X.X.X --force, replacing X.X.X with your target version.
How do you delete the lock in phpMyAdmin?
Open phpMyAdmin, find the core_updater.lock row in the wp_options table, and delete that one row.
Kinsta's error guide says you can resolve the message in phpMyAdmin by deleting the core_updater.lock row from the wp_options table. See the Kinsta guide to common WordPress errors.
- Back up the database first. If you have not set up backups yet, compare cPanel and plugin backup options before you touch the database.
- Open cPanel, go to the Databases section, then open phpMyAdmin. Namecheap's database guide shows phpMyAdmin under cPanel's Databases section.
- Select the WordPress database, then open the
wp_optionstable. The prefix may differ fromwp_, so check$table_prefixinwp-config.php. - Search
option_nameforcore_updater.lockand delete that row only.
Delete only that one row. Removing other options can break the site, so do not clear rows at random.
How do you fix the lock with a plugin?
If you cannot use WP-CLI or phpMyAdmin, the free Fix Another Update In Progress plugin on WordPress.org deletes the lock with one click.
The plugin page describes it as a one-click fix for the message that appears while updating WordPress core or during automatic updates.
- Go to Plugins > Add New Plugin and search for “Fix Another Update In Progress”.
- Install and activate it.
- Open Settings > Fix Another Update In Progress and run the fix.
- Retry the update from Dashboard > Updates.
Remove the plugin when you are done. A one-job plugin does not need to stay installed, and fewer active plugins means fewer things to update later.
How do you know the fix worked?
Go to Dashboard > Updates and check that the update buttons are back and the message is gone.
WordPress.org's Updating WordPress guide says the Dashboard > Updates screen is where you launch the update, so a working screen with an Update Now button is the clearest sign the lock is gone.
Check these signs:
- The “Another update is currently in progress” message no longer appears.
- The core update runs to completion and the version number changes.
- The site loads normally with no maintenance message.
- Tools > Site Health shows no update errors.
Run the update once after clearing the lock. If it completes, the lock was the only problem. Hosting.com's manual update guide walks through the same Dashboard > Updates steps, including the red update count badge.
What if the message comes back after you clear the lock?
If the message returns, the lock is a symptom, so find why updates keep dying instead of deleting the lock again.
The most likely causes are a PHP time limit, a low memory limit, a full disk, wrong file permissions, or a blocked connection to WordPress.org. Check Tools > Site Health > Info > Server for the PHP version and memory limit, and update the PHP version if your host offers a newer one.
WordPress.org's Updating WordPress guide also advises checking that plugins and themes are compatible with the version you are installing before you update.
A failed update can also leave a .maintenance file behind. The same guide says to delete the .maintenance file from the WordPress directory with FTP after a failed auto-upgrade.
If the update keeps failing at the download step, the server may not reach WordPress.org, and that is a host problem.
How is this different from “Briefly unavailable for scheduled maintenance”?
The maintenance message comes from a .maintenance file in the root folder, while the update message comes from a database lock, and each needs a different fix.
WordPress ignores a .maintenance file once it is 10 minutes old, and the Make WordPress Hosting handbook says you can clear it at once with wp maintenance-mode deactivate or by deleting the file.
| Message | Cause | Fix |
|---|---|---|
| Another update is currently in progress | core_updater.lock row in the database | Wait 15 minutes or delete the option |
| Briefly unavailable for scheduled maintenance | .maintenance file in the root folder | Wait 10 minutes or delete the file |
Deleting the .maintenance file does not clear the update lock. If you see both messages in turn, fix each one separately.
When should you contact your host?
Contact your host when the lock keeps returning, when you have no SSH or database access, or when the update fails with a server error after the lock is gone.
Ask for help when:
- The lock returns after every update attempt.
- The update fails with a timeout, a download error, or a 500 error.
- You cannot open phpMyAdmin or SSH on your plan.
- The site shows a database connection error after the update.
Ask the host to check the PHP error log, the PHP time and memory limits, and free disk space. Those three checks find most repeat causes.
WordPress 7.1.5, released on November 18, 2026, is a security release, and WordPress.org recommends updating sites immediately. WordPress.org also notes that only the most recent version is actively supported, so do not leave a stuck update for weeks.
If the update left the site broken, restore the backup you made before you started.
What mistakes should you avoid?
Avoid touching anything except the single lock row, and never clear a lock while an update may still be running.
- Deleting the whole
wp_optionstable or random rows instead of the single lock row. - Clearing the lock while another update is still running.
- Deleting the
.maintenancefile and expecting the lock message to vanish. - Updating again without a backup after the first failure.
- Leaving a one-job fix plugin installed forever.
- Ignoring the cause when the lock returns after every update.
Frequently asked questions
Will waiting really fix it, or do I have to delete something?
Waiting usually fixes it. WordPress sets the core update lock for 15 minutes, and the next update attempt clears it once that time has passed. Delete the lock yourself only if the message is still there after 15 minutes, or if you cannot wait. Always check first that no update is actually running before you delete anything.
Is it safe to delete core_updater.lock from the database?
Yes, when you delete only that one row. The option holds a timestamp that marks when the update started, not content, settings, or posts. Deleting it only tells WordPress that no core update is running. Back up the database first, and do not delete any other option rows.
Can I update plugins while the core update lock is set?
No. The lock blocks updates while a core update is in progress, and the message can appear when you try to update a plugin or theme at the same time. Wait for the core update to finish or for the 15-minute lock to expire, then run the plugin or theme update.
Why does the message appear even though I did not start an update?
WordPress runs minor and security updates in the background, a feature that has existed since WordPress 3.7. If one of those automatic updates stalls, the lock stays set and the message appears the next time you open the Updates screen. Wait 15 minutes or clear the lock, then check that the update finished.
Do I also need to delete the .maintenance file?
Only if you see the maintenance message. The .maintenance file causes the Briefly unavailable for scheduled maintenance screen, which is a different problem from the update lock. WordPress ignores that file after 10 minutes, or you can delete it from the root folder with FTP.
What if wp option delete says the option does not exist?
Then there is no lock set, and the message may come from a cached page or an update running on another tab or device. Reload Dashboard > Updates, clear your browser cache, and check whether someone else is updating the site. If the message stays, contact your host.
Sources
- Upgrading WordPress Make WordPress Hosting
- wp core update WordPress Developer Resources
- Core_Upgrader WordPress Developer Resources
- Updating WordPress WordPress.org Documentation
- WordPress 7.1.5 WordPress.org Documentation
- 70+ Most Common WordPress Errors and How to Fix Them Kinsta
- How to manage databases with phpMyAdmin Namecheap
- Updating WordPress manually Hosting.com
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
