Severity: Minor · Fix time: Under 5 min · Skill level: Beginner

“Another update is currently in progress” is a WordPress error message that appears in the Updates section of the dashboard when WordPress believes an update is already running — and therefore won’t allow a new one to start. In reality, no update is running; a previous update attempt left a lock record in the database that was never cleaned up. Deleting that single database row resolves the error immediately.

This is one of WordPress’s most benign-looking errors: no content is broken, no pages are down, and no visitors are affected. The only impact is that you temporarily can’t run updates from wp-admin until the lock is cleared.

Need a quick map of every WordPress error? See our 70+ WordPress Errors Guide → for a categorized reference of every common WordPress issue.

How “Another Update Is Currently in Progress” Works

When WordPress starts an update, it writes a record to the wp_options database table with the option_name of core_updater.lock. This lock prevents two simultaneous updates from running and corrupting each other. When the update finishes normally, WordPress deletes this record automatically.

If the update is interrupted — by a timeout, a server crash, a closed browser tab, or a PHP memory limit — WordPress never reaches the cleanup step. The core_updater.lock record remains in the database indefinitely. The next time you visit the Updates page, WordPress finds the lock, assumes an update is still running, and blocks new updates with the error message.

The fix: delete the core_updater.lock row from the wp_options table. There are three ways to do this — via phpMyAdmin, via WP-CLI, or via a WordPress plugin — and all three take under two minutes.

Check This First — 2-Minute Diagnostic

  1. Verify no update is actually running — If you initiated an update in the last few minutes and the page is still showing “in progress,” wait a few minutes before acting. A large update can take time.
  2. Check if this persists after a page reload — Reload the Updates page. If the error is still there after a minute or two, the lock is stuck.
  3. Confirm in phpMyAdmin — Go to your hosting’s phpMyAdmin, open the wp_options table, and search for core_updater.lock. If it exists, the lock is stuck. If it doesn’t exist, the issue is something else.

Purpose & Benefits

1. Database Locks Protect Against Concurrent Updates

The core_updater.lock mechanism exists for a legitimate reason: running two update processes simultaneously on WordPress core or plugins can corrupt files and database tables. The lock is a protection mechanism, not a bug. Understanding this means you know not to try to force an update while one is genuinely in progress — but also that a stuck lock is safe to delete.

2. Keeping Updates Current Is a Security Priority

WordPress core updates frequently contain security patches. Plugin updates fix vulnerabilities discovered after release. If “another update in progress” prevents you from running updates, those security fixes remain uninstalled. Clearing the lock promptly ensures your site stays current. Our WordPress maintenance services include managed updates that monitor for and resolve lock issues before they delay security patches.

3. Understanding wp_options Demystifies WordPress

The wp_options table in the WordPress database stores everything from site settings and widget configurations to transient cache data and update locks. Knowing this table exists and that you can read it via phpMyAdmin gives you a window into how WordPress tracks its internal state — useful knowledge for diagnosing a range of other WordPress issues.

Examples

1. Deleting the Lock via phpMyAdmin

This is the most common method for users without command-line access:

  1. Log into your hosting control panel (usually cPanel) and open phpMyAdmin.
  2. Select your WordPress database from the left sidebar.
  3. Click on the wp_options table (your prefix may differ — it could be wpsomething_options).
  4. Use the Search tab to search for core_updater.lock in the option_name column.
  5. Find the row and click Delete.
  6. Return to your WordPress dashboard and reload the Updates page.
-- Alternative: delete directly via SQL in phpMyAdmin
DELETE FROM wp_options WHERE option_name = 'core_updater.lock';

2. Deleting the Lock via WP-CLI

For site owners with SSH access, WP-CLI handles this in a single command:

# Delete the stuck update lock via WP-CLI
wp option delete core_updater.lock

If successful, WP-CLI returns: Success: Deleted 'core_updater.lock' option.

After running this command, reload the WordPress Updates page — updates should be available again immediately.

3. Using a One-Click Plugin

If you have no experience with phpMyAdmin or command line, install the free “Fix Another Update In Progress” plugin from the WordPress plugin directory:

  1. Go to Plugins → Add New and search for “Fix Another Update In Progress.”
  2. Install and activate the plugin.
  3. Go to Settings → Fix Another Update In Progress.
  4. Click the “Fix WordPress Update Lock” button.

The plugin deletes the core_updater.lock row and confirms when it’s done. Deactivate and delete the plugin after using it — it serves no ongoing purpose.

Common Mistakes to Avoid

  • Waiting for the “update” to finish on its own — A stuck lock won’t clear itself. No update is running; WordPress is just reading a stale database record. The lock must be deleted manually.
  • Trying to run updates from the command line while the lock is active — WP-CLI respects the core_updater.lock the same way wp-admin does. Delete the lock first, then run updates.
  • Editing the wrong database table — Make sure you’re modifying the correct WordPress database and the correct wp_options table. If you have multiple WordPress installs or databases, work in the right one. The table prefix in the database must match the $table_prefix value in wp-config.php.
  • Leaving the “Fix Another Update In Progress” plugin active — This plugin has no ongoing utility once the lock is cleared. Deactivate and delete it to keep your plugins list clean.

Best Practices

1. Delete the Lock Record via phpMyAdmin

The most reliable fix without command-line access is to delete the core_updater.lock record directly from phpMyAdmin. Access phpMyAdmin through your hosting dashboard, navigate to your WordPress database’s wp_options table, search for core_updater.lock, and delete the row. This takes under two minutes and requires no coding knowledge. Always confirm you’re in the correct database before making changes.

2. Use WP-CLI for Speed and Precision

If you have SSH or WP-CLI access, wp option delete core_updater.lock is the fastest path. WP-CLI’s targeted delete operation is less error-prone than navigating phpMyAdmin tables manually, and it provides immediate confirmation that the option was deleted. WP-CLI is the preferred method for developers managing multiple WordPress sites.

3. Address the Root Cause of the Failed Update

After clearing the lock, retry the update. If it fails again and leaves another stuck lock, the underlying issue — a PHP memory limit, execution time limit, or a specific plugin conflict — needs to be resolved. Check your WordPress error logs and server error logs for clues about what caused the first update to fail. Recurring stuck locks typically indicate a hosting environment that needs PHP configuration adjustments.

Frequently Asked Questions

What causes “another update is currently in progress” most often?

A previous update was interrupted before it could clean up after itself. Common interruptions include closing the browser tab mid-update, a PHP execution time limit being hit, a server timeout, or a PHP memory limit being exceeded. The update left the core_updater.lock record in wp_options and never removed it.

How do I fix “another update in progress” when locked out of wp-admin?

This error typically doesn’t lock you out of wp-admin — you can still access your dashboard, you just can’t run updates. If you’re also locked out of wp-admin, you’re dealing with a separate issue. To clear the update lock without wp-admin, use phpMyAdmin through your hosting control panel (no WordPress login required) to delete the core_updater.lock row, or use WP-CLI via SSH.

Can this error hurt my SEO?

No, this error has no direct impact on your site’s front-end or search visibility. Visitors see your site normally. The only effect is blocking updates from wp-admin — which indirectly matters for SEO if the updates include security patches or performance improvements that would benefit your site.

Is it safe to delete the core_updater.lock row?

Yes, completely safe. The core_updater.lock is a temporary flag that should have been automatically deleted when the update finished. Deleting it manually when it’s stuck is the intended recovery action. Deleting it does not affect any site settings, content, or code.

What if the lock reappears after every update?

If core_updater.lock keeps getting stuck after every update attempt, your updates are consistently failing at the same point. Enable WP_DEBUG temporarily and check wp-content/debug.log for error messages during the update. Most recurring cases point to a PHP memory limit or execution time limit that’s too low for the update process to complete.

Related Glossary Terms

How CyberOptik Can Help

Still broken? Our team fixes WordPress errors like this in under 30 minutes for maintenance clients. While “another update in progress” is one of the simpler WordPress errors, recurring update failures often signal a hosting environment that needs attention — and uninstalled updates create security gaps. Our WordPress maintenance services manage updates proactively, monitor for failure conditions, and ensure your site stays current without requiring your manual attention. Contact us to discuss your site or explore our WordPress support options.