Black FridayCyber Monday 2026
13Days
14Hrs
16Mins
31Secs
Flat20% OFF

Our biggest sale of the year20% off the first payment on all maintenance plans. Code BF2026

Grab the deal
WordPress

“Another Update Is Currently in Progress” in WordPress: Fix It Safely

WordPress locks core updates so two of them cannot run at once. Learn why the lock gets stuck, how long it lasts and the safe order to clear it.

wpallsolution Updated 7 min read

“Another update is currently in progress” is a message WordPress shows when you try to update the core software and it believes an earlier update has not finished. It looks alarming, but it is a safety lock, not a hack and not data loss. This guide explains what the lock is, how long it normally lasts, and the order in which to check things so you only remove it when it is really stuck.

Quick answer

Before WordPress starts a core update it records a lock in the database, and in the current WordPress source code that lock is respected for 15 minutes. While the lock is fresh, a second core update attempt is refused with this message. In most cases the right move is to stop clicking, wait 15 minutes and try once more. If the message stays and you are sure no update is running, you can clear the stale lock, but only after a backup.

How this guide was prepared: it is research-based. We read the WordPress source code and developer reference listed under Sources, checked on October 23, 2026. We did not reproduce this error on a client site, and the fixes below are the documented, low-risk order of steps, not a guarantee for every host.

What the update lock is

A core update replaces WordPress files and changes the database. Running two of those at the same time could leave the site half updated. To prevent that, WordPress writes a small record into its options table before the update begins. The record is named core_updater.lock and holds the time the lock was created. If another core update starts while that record is newer than the timeout, WordPress stops and shows the message.

In the WordPress core updater, the lock is created with a 15 minute timeout. WordPress documents that an expired lock is released automatically the next time something asks for it, so a lock that is older than 15 minutes should not block a new attempt by itself. The message itself is defined in the core updater class (the same place where the lock is requested).

Why it appears

  • You clicked Update twice. The second click arrives while the first update is still running.
  • Two people updated at once. A second administrator, or a hosting panel, started an update as well.
  • An automatic update was running. WordPress installs minor and security core releases automatically by default, so a background update can overlap with a manual one.
  • An earlier update was interrupted. The browser was closed, PHP timed out or the server restarted, so the lock was written but never released. It then expires by itself after the timeout.

The decision tree: wait, retry or clear?

Flowchart for the WordPress error Another update is currently in progress: five questions covering the 15 minute wait, update state, backup, retry and clearing a stale lock
Five questions tell you whether to wait, retry or clear the lock.
  1. Started less than 15 minutes ago? Wait and do not click Update again (Step 1).
  2. Site shows a maintenance message or looks half updated? Check the update state first (Step 2).
  3. No recent backup? Make one before you retry or edit anything (Step 3).
  4. Still blocked after 15 minutes? Retry from the dashboard or with WP-CLI (Step 4).
  5. Message remains and nothing is running? Clear the stale lock, then verify (Step 5).

Symptoms and likely causes

What you seeLikely causeStart with
Message appears right after you pressed UpdateA double click or a still running updateStep 1
Site shows “Briefly unavailable for scheduled maintenance”An update is running or was interruptedStep 2
Message appears every time for more than 15 minutesA stale lock or a repeated automatic updateSteps 4 and 5
Update fails and the version number did not changeThe earlier update did not finishSteps 2 to 4

5 steps to fix “Another update is currently in progress”

Step 1: Stop and wait 15 minutes

Do not press Update again. Each new attempt only checks the lock and fails. Because the lock is respected for 15 minutes, the simplest fix is time. Close the Updates screen, make a note of the clock time, and come back after 15 minutes.

Step 2: Check whether an update is really running or half finished

Open Dashboard → Updates and look at the WordPress version. Then open the home page in a private window. If you see “Briefly unavailable for scheduled maintenance”, an update started and did not clean up, which our guide on getting WordPress out of maintenance mode explains. If the site loads normally, the lock is most likely only waiting to expire. Also ask whether anyone else, or an automatic update, may have started an update.

Step 3: Take a backup first

Before you retry or edit anything, make a full backup of the files and the database, and check that you can restore it. If you are not sure your backups would work, read is your WordPress backup really safe first.

Step 4: Retry the update

After 15 minutes, open Dashboard → Updates and run the core update once. If you have command line access, WP-CLI offers wp core update, which is the supported way to update core from the terminal. For a safer routine in general, see how to update WordPress safely.

Step 5: Clear a stale lock (last step)

If the message persists, you have waited well past 15 minutes and you are sure nothing is updating, remove the lock record. With WP-CLI you can read it with wp option get core_updater.lock and delete it with wp option delete core_updater.lock. Without WP-CLI, open the options table in your database tool (the table name starts with your prefix, such as wp_options) and delete the row whose option_name is core_updater.lock. The row only stores a time stamp. If you use a persistent object cache, clear it afterwards. Then run Step 4 again. If you are unsure at any point, ask your host or a developer to do this, because a wrong database edit is hard to undo.

Version and hosting differences

  • The 15 minute timeout comes from the current WordPress source. Older versions or custom hosting stacks may behave differently, so check your version if the wait seems longer.
  • Some managed hosts run their own updaters or staging tools. If your host controls updates, contact them before you edit the database.
  • Automatic background updates for minor releases are on by default, so avoid manual core updates at the moment an automatic one may run. See WordPress auto updates.

How to verify the fix

  • Dashboard → Updates shows the expected WordPress version and no pending core update.
  • The home page, a few inner pages and the admin area open normally, and no maintenance message shows.
  • Tools → Site Health shows no new critical issues. See WordPress Site Health.
  • Your forms and, on a store, a test checkout still work.

How to prevent it from happening again

  • Press Update once and keep the tab open until the screen says it has finished.
  • Agree who updates the site, so two people never update at once.
  • Update at a quiet time and have a backup ready.
  • Keep a record of what you changed. A regular maintenance routine removes most of this guesswork.

Frequently asked questions

Is this error a sign my site was hacked?

No. It is a protective lock from the WordPress updater. It can still appear on a hacked site, so check for other warning signs if something else looks wrong.

How long does the lock last?

In the current WordPress core updater it is respected for 15 minutes, and an expired lock is released the next time it is requested.

Is it safe to delete the lock myself?

Only when you are sure no update is running and you have a backup. The row stores a time stamp, but a mistake in the database can cause bigger problems.

Will I lose content?

The lock itself does not delete content. A badly interrupted update can leave files half replaced, which is why a backup matters.

What to do next

Wait, check the update state, back up and retry. If the update keeps failing or the site is stuck in maintenance mode, wpallsolution offers WordPress maintenance packages and an emergency WordPress fix. We cannot promise a result without seeing your hosting setup.

Sources and official documentation

Keep reading

More guides

Need a hand with this?

Tell us what is happening. We reply with honest next steps.

Talk to us