WordPress: Another update is currently in progress.
WordPress thinks an update is running because the core_updater.lock option exists — usually left behind by a failed/interrupted update.
Seen on:
WordPress
Meaning
The lock expires after 15 minutes. If an update truly crashed, delete the lock option and run the update again.
Common causes
- Interrupted core update (timeout, closed browser)
- Automatic background update running
- Leftover lock after a crash
⚡ Quick fix
- Wait 15 minutes
- Delete the core_updater.lock option
- Retry the update
Detailed fix by platform
Shell
- php
wp option delete core_updater.lock wp core update
How to diagnose
- Lock — Option present?
- Background — Auto-update running?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- 403 Forbidden wp-admin WordPress: 403 Forbidden on wp-admin, wp-login.php or admin-ajax.php
- 404 except homepage WordPress: 404 Not Found on every page except the homepage (permalinks / .htaccess / Nginx rules)
- An automated WordPress update has failed An automated WordPress update has failed to complete - please attempt the update again now
Most viewed in WordPress
Other ways to find it
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 7 Oct 2026