"Another Update Is Currently in Progress" in WordPress: Fix the Lock (2026)
Disclosure: some links on this page are affiliate links. We may earn a commission at no extra cost to you. How we test and rate hosts.
"Another update is currently in progress" is a stuck lock, not a stuck update. WordPress sets a core_updater.lock option in the database when a core update starts - it's meant to auto-clear when the update finishes. When an update dies mid-way, the lock stays. The fix: delete the lock row.
Step 1: Wait 15-20 Minutes First
Before touching the database: WordPress auto-clears the lock ~15 minutes after the update process dies. If you're within that window, get a coffee and check again. If the message persists past 20 minutes, the lock is stale and needs manual removal.
Step 2: Delete the Lock via phpMyAdmin
The reliable fix:
- 1.cPanel > phpMyAdmin > select your WordPress database
- 2.Open the
wp_optionstable (prefix may differ - check wp-config.php$table_prefix) - 3.Search
option_nameforcore_updater.lock - 4.Delete that row. If
auto_updater.lockexists too, delete it as well.
SQL equivalent if you prefer the query tab:
DELETE FROM wp_options WHERE option_name = 'core_updater.lock';
DELETE FROM wp_options WHERE option_name = 'auto_updater.lock';
Step 3: WP-CLI Method
If you have SSH access, this is cleaner:
wp option delete core_updater.lock
wp option delete auto_updater.lock
Step 4: The Plugin Method
Not comfortable in the database? Install Fix Another Update In Progress - one button that deletes the lock safely. Fine for a one-time fix; uninstall it after, since the lock should never recur if updates run cleanly.
Why the Lock Got Stuck
The lock exists to prevent two updates running simultaneously and corrupting core files. It gets stuck when the first update dies: browser closed during update, PHP timeout mid-process, connection drop, or a server issue. If this recurs on every update, the underlying problem is usually a too-tight max_execution_time - raise it (see our execution time fix) so updates finish before PHP kills them.
After the Fix: Verify the Update Completes
With the lock cleared, retry the update from Dashboard > Updates. If it fails again - or worse, the site white-screens - the original update probably did corrupt files and needs a manual re-install. Download the matching WordPress version, upload wp-admin and wp-includes via FTP (not wp-content), then retry.
Updates That Finish
Stuck locks usually trace to PHP timeouts killing updates mid-way. Bluehost's defaults give updates room to complete - and 24/7 support can clear stuck locks if you'd rather not touch the database. From $3.99/mo.
Get Reliable HostingRelated: stuck in maintenance mode - max execution time fix - white screen of death - 500 internal server error.
What are you building?
Tell us about your project so we can match the perfect hosting plan.
Hosting Cost Calculator
See exactly how much you'll spend on hosting over time. Compare Bluehost vs popular alternatives and discover your potential savings.
Used to calculate transaction fees (Shopify charges 2% on sales)
Frequently Asked Questions
What causes 'Another update is currently in progress'?
WordPress sets a lock (core_updater.lock in wp_options) when a core update starts, to prevent simultaneous updates. Normally it auto-clears when the update finishes or after ~15 minutes. If the update crashed mid-way, the lock stays and blocks all further updates.
What's the fastest fix?
Wait 15-20 minutes first - the lock often auto-clears. If it persists, delete the core_updater.lock row from the wp_options table via phpMyAdmin, or install the Fix Another Update In Progress plugin which does it with one button.
How do I remove the lock via phpMyAdmin?
cPanel > phpMyAdmin > select your database > wp_options table > search option_name for 'core_updater.lock' > delete that row. If you also see 'auto_updater.lock', delete that too. Then retry the update.
Can I fix it with WP-CLI?
Yes - run: wp option delete core_updater.lock (and wp option delete auto_updater.lock if present). This is the cleanest method if you have SSH/WP-CLI access.
Why did the update lock get stuck?
The previous update was interrupted - browser closed, connection dropped, PHP timeout, or a server issue during a core update. The lock exists to prevent exactly that scenario from corrupting core files, so it errs on the side of staying set.
Is it safe to delete the lock manually?
Yes, if no update is actually running. Check Dashboard > Updates first - if nothing is visibly running and it's been 15+ minutes, the lock is stale and deleting it is safe. The worst case is another update starts, which the lock would have prevented anyway.
Ready to launch?
Get Bluehost from $3.99/month with a free domain, free SSL, and 30-day money-back guarantee.
Related Articles
Bluehost vs Competitors: The Technical Deep Dive
We ran 47 benchmarks over 90 days. Here's the raw data on why Bluehost dominates.
Fix ERR_TOO_MANY_REDIRECTS in WordPress (2026): The 6 Real Causes
ERR_TOO_MANY_REDIRECTS means an infinite redirect loop. Match your Site URLs, fix Cloudflare SSL mode, reset .htaccess, kill plugin conflicts - step-by-step with code.
WordPress 403 Forbidden Error: 7 Fixes That Actually Work (2026)
403 means the server understood you but refuses to serve the page. Fix file permissions (755/644), regenerate .htaccess, kill security plugin blocks - in the right order.
Fix 502 Bad Gateway in WordPress (2026): Diagnose First, Then Fix
502 means the gateway got a bad response from your server - usually PHP timeouts, CDN issues, or overload. A 9-step diagnostic workflow from browser checks to server logs.
Fatal Error: Maximum Execution Time Exceeded - 6 Fixes (2026)
max_execution_time kills slow updates at 30-60s. Fix the culprit plugin/theme first, then raise the limit via wp-config, .htaccess or php.ini - with exact code.
HTTP Error Uploading Images in WordPress: 9 Fixes Ranked (2026)
The vague 'HTTP error' on image upload usually means memory limits or Imagick. Fix order: rename the file, bump memory, force GD library, check permissions - with code.