Another Update Is Currently in Progress: Clear the WordPress Lock

You click Update to version … under Dashboard → Updates and WordPress replies “Another update is currently in progress.” No update seems to be running. WordPress uses a short-lived lock to stop two core updates from running at once, and an update that was interrupted can leave that lock behind. This guide shows how to check whether an update really is running and how to clear a stale lock safely.

How the update lock works

When a core update starts, WordPress’s Core_Upgrader calls WP_Upgrader::create_lock( 'core_updater', 15 * MINUTE_IN_SECONDS ). The lock is a row in the options table named core_updater.lock, holding the time it was created. While that row exists and is less than 15 minutes old, any other core update stops with “Another update is currently in progress.” When the update finishes, WordPress deletes the row. We confirmed these details in WordPress core’s upgrader code.

If the update is interrupted, for example by a timeout, a server restart or a closed connection, the row can stay behind. After 15 minutes WordPress considers it stale, removes it and takes a new lock.

Automatic background updates use a separate lock called auto_updater.lock. A background update that is running can still make a manual update wait.

Step 1: Make sure no update is actually running

1. Check whether someone else is updating the site, or whether your host runs updates for you. Many managed hosts update WordPress automatically.
2. Load the site’s front end. If it shows “Briefly unavailable for scheduled maintenance”, an update is in progress or was interrupted; see our guide to briefly unavailable for scheduled maintenance.
3. Check Dashboard → Updates to see whether WordPress already shows the new version.

If an update is running, let it finish. Interrupting it can leave WordPress half-updated.

Step 2: Wait 15 minutes

The simplest fix is to wait. After 15 minutes WordPress treats the lock as stale and clears it on the next update attempt. Return to Dashboard → Updates and try again.

Step 3: Remove a stale lock manually

Only do this if you are sure no update is running.

With WP-CLI (over SSH, in the WordPress folder):

wp option get core_updater.lock
wp option delete core_updater.lock

The first command shows the lock’s timestamp. The second removes it.

With phpMyAdmin:

1. Back up the database first. Our backup guide explains how.
2. Open the options table (for example wp_options).
3. Search for option_name equal to core_updater.lock.
4. Delete that single row. Do not delete anything else.

Then go back to Dashboard → Updates and run the update again.

If the update fails again

If the update starts but stops part-way again, the lock was a symptom. Look for the real cause:

• Time limits. Updates can exceed PHP’s time limit on slow servers. See maximum execution time exceeded.
• File permissions or disk space. WordPress must be able to write to its own files. See could not create directory.
• Memory. See allowed memory size exhausted.

If you have SSH access, wp core update runs the update from the command line, without browser or web server timeouts, and prints clearer errors.

When to contact your host

Contact your host if your plan includes managed updates, if the lock keeps coming back, or if the update keeps failing. They can tell you whether their own update system is running and check server logs from the time of the failure.

Frequently asked questions

Is it safe to delete core_updater.lock?

Yes, as long as no update is running. It only holds a timestamp, and WordPress removes it itself after a successful update.

Does this lock affect plugin updates?

The core_updater lock is for WordPress core updates. Plugin and theme updates have their own checks, so you can usually still update plugins while it exists.

Will the site be down while I wait?

No. The lock only blocks new core updates. Unless an update was interrupted while the maintenance file was active, the site keeps working.

Summary

“Another update is currently in progress” means WordPress found a core_updater.lock option less than 15 minutes old. Check that no update is really running, wait 15 minutes, or delete the lock with WP-CLI or phpMyAdmin after a backup. If updates keep failing, fix the underlying time, permission or memory problem.