Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
The safest fix is to confirm that no WordPress core update is running, then remove the stale lock with wp option delete core_updater.lock. Do not delete the lock while another administrator, automated job, or hosting process is still updating the site.
What the message means
WordPress displays “Another update is currently in progress.” when its core updater cannot acquire the core_updater lock. The lock prevents two WordPress core updates from running at the same time.
The error alone does not prove that an update is actively running. The lock may belong to a current update, or it may be left behind after an interrupted process. WordPress core currently uses a 15-minute lock interval, but that is an implementation setting—not a guarantee that every failed update will clear itself exactly 15 minutes later.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsBefore removing the lock
Check whether the site is genuinely being updated. Removing a lock during an active update can interfere with the process and create additional problems.
- Open the WordPress administration area and check the update screen for an active core update or an unfinished status.
- Ask other site administrators whether they started an update.
- Check scheduled deployment, maintenance, security, or hosting jobs that might update WordPress automatically.
- If your host manages WordPress updates, confirm with its control panel or support team that no update is in progress.
Only continue when you have a reasonable basis to conclude that no core update is running.
Remove a stale lock with WP-CLI
WP-CLI is the clearest recovery route for an administrator who has shell access to the site’s WordPress installation. Run the command from that installation:
wp option delete core_updater.lockThe command deletes the option that records the core-updater lock. It should be used only after checking that another update is not actually running.
Recommended Free Tools
Typical command-line sequence
- Open a shell on the server or use your host’s terminal access.
- Change to the directory containing the WordPress installation.
- Verify that WP-CLI is operating on the intended site, especially if the server hosts multiple WordPress installations.
- Run
wp option delete core_updater.lock. - Return to the WordPress dashboard and retry the core update, or run the intended core-update command through WP-CLI.
- After the update, load the front end and administration area and check for errors, missing assets, or maintenance-mode messages.
Retry the update and verify the site
Once the stale option is removed, retry the update through the normal WordPress update interface or your established WP-CLI workflow. A successful update should leave both the dashboard and public site accessible.
Rank #3
- Confirm the WordPress version shown in the dashboard is the expected version.
- Visit representative public pages and log in to the administration area.
- Check that critical plugins, themes, scheduled tasks, and forms still function.
- Review the hosting or PHP error logs if the update reports a failure or the site behaves unexpectedly.
Dashboard versus WP-CLI recovery
| Route | Access needed | Best fit | Important limitation |
|---|---|---|---|
| Wait and retry from the dashboard | WordPress administrator access | When an update may still be finishing or the lock has only just appeared | Waiting does not establish whether the lock is stale, and the 15-minute interval is not a guaranteed clearing time. |
| Delete the option with WP-CLI | Shell access and a correctly targeted WordPress installation | Administrators who have verified that no update is active | Deleting the lock during a real update can disrupt it. |
| Manual core update | File and database administration, plus current WordPress manual-update instructions | A persistent installation-specific failure after safer recovery steps | It is more involved, and a single support-thread report is anecdotal rather than evidence that it fixes every case. |
If the error returns
Do not repeatedly delete core_updater.lock without finding out why it is being recreated. A recurring lock can indicate an update process that is failing, overlapping automation, insufficient permissions, a timeout, or another installation-specific problem.
Investigate the update process
- Identify whether a host, deployment tool, security plugin, or scheduled task is launching updates.
- Review WordPress, PHP, web-server, and hosting logs around the attempted update.
- Check available disk space and the filesystem permissions used by the web server and WP-CLI.
- Make sure the command is being run against the intended site and environment.
- Coordinate updates so that only one process can run at a time.
Consider a manual update only as a fallback
If the lock is gone but the normal updater still cannot complete, consult the current official WordPress manual-update procedure for your installation before replacing files or changing the database. A WordPress.org support-thread user reported that manual updating solved one case, but that report does not establish a universal remedy.
Quick Recap
Safety checklist
- Have you confirmed that no person or automated service is updating WordPress?
- Are you in the correct WordPress installation directory?
- Do you have a recent backup and a way to restore the site if the update fails?
- Will you test both the front end and dashboard after retrying?
- If the lock returns, will you investigate the updater instead of deleting the option repeatedly?
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.
