What another update is currently in progress means
This message is a protection mechanism rather than evidence that WordPress is damaged. When a WordPress core update begins, WordPress creates an update lock so a second core update cannot start at the same time and overwrite files while the first process is still working.
Current WordPress core uses a core_updater.lock option for this purpose. The core updater treats that lock as valid for 15 minutes. Once it has expired, a later update attempt can replace the stale lock.
If you see the message immediately after starting an update, waiting is normally the correct first action. Forcing another update while files are still being changed creates unnecessary risk.
Why a WordPress update lock can remain
The most ordinary cause is simply that another core update really is running. This is particularly likely if an update was started in another browser tab, by another administrator or by an automated process.
A lock can also be left behind temporarily when an update request times out, the PHP process stops, the browser connection closes or the server encounters a problem during the update.
Do not confuse this lock with WordPress maintenance mode or a failed plugin update. The core_updater.lock specifically protects WordPress core updating. If the website is also displaying a maintenance message, missing files or a critical error, investigate that condition separately rather than assuming that deleting the lock will repair it.
How to clear another update in progress safely
- Wait before changing anything. If an update may still be running, leave it alone. WordPress core uses a 15-minute validity period for the core updater lock.
- Refresh the Updates screen after the wait. In many cases the next attempt will proceed once the previous lock has expired.
- Check that no update is active. Confirm that another administrator, deployment process or hosting tool is not currently updating WordPress.
- Take a full backup. Back up both files and the database before manually changing an update lock or retrying a failed core update.
- Use WP-CLI if the lock is genuinely stale. WordPress's official WP-CLI documentation recommends deleting the lock only after verifying that another update is not actually running.
wp option delete core_updater.lockRun that command only if you have appropriate SSH and WP-CLI access and understand which WordPress installation you are operating on. Do not remove unrelated database options and do not edit or delete WordPress core files to clear this message.
When an update lock needs investigation
Get help if the message persists after the lock should have expired, repeatedly returns, or follows a failed core update that has left the site unavailable or behaving unexpectedly. The underlying problem may be file permissions, storage, server processes or an incomplete update rather than the lock itself.
If you are unsure whether a live update is still running, do not clear the lock experimentally. Our Emergency Fix costs £249 per incident with a response within 2 working hours. Care plans start at £59 a month for ongoing WordPress maintenance.