Troubleshooting
Why Won't WordPress Show Plugin Updates? Causes and Fixes

Short answer
WordPress usually hides plugin updates because its last update check is stale, WP-Cron is not running, the server cannot reach api.wordpress.org, updates are disabled in wp-config.php or by a plugin, or a premium plugin's license is inactive. Click Check again under Dashboard > Updates first, then work through the causes below.
Key takeaways
- Click Check again under Dashboard > Updates to force a fresh update check.
- Blocked outgoing connections stop WordPress from seeing any updates.
- DISALLOW_FILE_MODS and update manager plugins can hide updates entirely.
- Premium plugins only show updates with an active license.
- On multisite, plugin updates appear in the Network Admin only.
Why is WordPress not showing plugin updates?
WordPress shows updates only after a successful check, so missing updates usually mean the check is stale, blocked or disabled, or the plugin gets updates from somewhere other than WordPress.org.
WordPress checks for plugin updates in the background roughly twice a day. It saves the result and shows it until the next check.
When something breaks that process, the Plugins screen can look up to date for weeks while new versions sit waiting.
| Symptom | Likely cause | First fix |
|---|---|---|
| No updates for any plugin | Stale check or blocked connection | Check again, then test connections |
| No update menu at all | Updates disabled or wrong role | Check wp-config.php and your role |
| One premium plugin never updates | Inactive license | Activate the license |
| One free plugin never updates | Plugin closed or abandoned | Check its WordPress.org page |
| Updates missing on subsites | Multisite | Use Network Admin |
How do you force WordPress to check for updates?
Go to Dashboard > Updates and click Check again; WordPress then contacts the update servers immediately and refreshes the list of available plugin, theme and core updates.
If updates appear after this, the background schedule was the problem. Look at WP-Cron next so the issue does not come back.
You can also check from the command line. The WP-CLI plugin commands show an update column for every installed plugin.
wp plugin list --update=available
Is WP-Cron running?
WordPress schedules its update checks with WP-Cron, so if scheduled tasks never run, the saved update information goes stale and new versions stop appearing.
WP-Cron runs when people visit the site. Low-traffic sites, disabled cron and failed loopback requests can all stop it.
If wp-config.php contains DISABLE_WP_CRON set to true, a real server cron job must call wp-cron.php instead.
Our guide on fixing WP-Cron not running covers loopback errors and server cron setups.
Can your server reach the update servers?
WordPress must make outgoing HTTPS requests to api.wordpress.org, and firewalls, blocked external requests, DNS problems or outdated SSL libraries on the server will make every update check fail.
Open Tools > Site Health. It reports failed connections to WordPress.org and failed loopback requests.
Our guide on using Site Health in WordPress explains how to read those tests.
Check wp-config.php for WP_HTTP_BLOCK_EXTERNAL. If it is true, add api.wordpress.org and downloads.wordpress.org to WP_ACCESSIBLE_HOSTS or remove the block.
Timeout messages often point to network issues. The libcurl error list helps you decode cURL numbers in error logs.
Are updates disabled in wp-config.php?
If DISALLOW_FILE_MODS is set to true, WordPress blocks plugin and theme installs, updates and edits from the dashboard, and the update notices disappear.
Some managed hosts and agencies set this on purpose. They deploy updates through Git or their own tools instead.
The WordPress handbook page on editing wp-config.php explains this constant and the related DISALLOW_FILE_EDIT.
Ask before removing it. If a host or developer manages updates for you, changing it can clash with their deployment process.
Is a plugin hiding updates?
Update manager plugins, security plugins and some custom code can hide update notices or block updates for selected plugins, so check their settings before assuming nothing is available.
Look for plugins with names like update manager, disable updates or maintenance tools.
Custom code can filter the saved update data. Search your theme and must-use plugins for update-related filters if you inherited the site from another developer.
If you want controlled updates instead of hidden ones, our guide on enabling automatic updates for plugins shows the built-in options.
Why don't premium plugins show updates?
Premium plugins get updates from their vendor, not WordPress.org, and most only show them when a valid license key is entered and active for that site's domain.
Open the plugin's license screen and confirm the status. Expired or moved licenses are the usual cause.
After migrating to a new domain, deactivate the license on the old site and activate it again on the new one.
Some vendors need a separate helper or updater plugin. Check the vendor's documentation if updates never appear.
Our comparison of free vs premium WordPress plugins explains how updates and support differ between the two.
Has the plugin been closed or abandoned?
A plugin closed on WordPress.org or no longer maintained will never show updates, so check its plugin page for a closure notice or a last updated date long in the past.
Closed plugins can be removed for security issues or guideline violations. Replace them rather than waiting for an update.
The plugin directory guidelines explain why plugins are closed and what that means.
If the plugin is still listed but untouched for years, plan a replacement. Old plugins often break with newer PHP versions.
Why do missing updates matter for security?
Plugin updates often fix security holes, so a site that silently stops seeing updates can keep running known vulnerable code for months without anyone noticing.
The OWASP Top 10 lists vulnerable and outdated components as a major web risk. WordPress plugins are a common example.
Set a monthly reminder to compare your installed versions with each plugin's latest release. That catches a broken update check early.
Could the plugin get updates from the wrong place?
Custom or renamed plugins can share a folder name with a WordPress.org plugin, so WordPress may offer the wrong update or none at all; the Update URI header prevents this.
WordPress 5.8 added the Update URI plugin header. It tells WordPress where a plugin's updates should come from.
The core team's note introducing the Update URI header shows how developers use it.
If you edited a plugin's files directly, an update would overwrite your changes. Move custom code into a separate plugin instead.
Why are updates missing on multisite?
On a multisite network, plugin updates are managed only by network administrators, so site admins on individual subsites never see update notices or the Updates screen.
Go to My Sites > Network Admin > Updates to see and run plugin updates for the whole network.
If you are a site admin but not a super admin, ask the network administrator to run updates.
Does your user role allow updates?
Only users with the update_plugins capability, usually administrators, see plugin update notices and the Updates screen; editors and lower roles see nothing.
Role editor plugins can remove this capability by mistake. Check your role's capabilities if an admin account cannot see updates.
Access control plugins may also hide the Updates menu for some admins.
To test, log in with the original administrator account created when the site was installed, or ask another admin to check their dashboard.
What should you do once updates appear?
Back up first, update on a staging copy if possible, update one plugin at a time on important sites, and know how to roll back if something breaks.
Read the changelog for big version jumps. Major updates sometimes change settings or need database upgrades.
If an update causes problems, our guide on how to roll back a plugin update shows safe ways to return to the previous version.
An update stuck halfway can leave a maintenance lock behind. Our guide on fixing the another update is in progress message covers that case.
Frequently asked questions
How do I force WordPress to check for plugin updates?
Go to Dashboard, then Updates, and click Check again. WordPress contacts the update servers straight away and refreshes the list of available updates.
Why is the Updates menu missing in WordPress?
Updates may be disabled with DISALLOW_FILE_MODS, hidden by a plugin, limited to Network Admin on multisite, or your user role may lack permission to update plugins.
Why does my premium plugin not show updates?
Most premium plugins need an active license key for the current domain. Check the license status in the plugin's settings and reactivate it after a migration.
How often does WordPress check for plugin updates?
WordPress checks in the background about twice a day using its scheduled task system. If scheduled tasks do not run, the update information goes stale.
Can a firewall stop WordPress from finding updates?
Yes. If the server cannot make outgoing connections to the WordPress update servers, every update check fails. Site Health reports these connection errors.
Sources
- wp plugin list WP-CLI Command Reference
- Editing wp-config.php WordPress Developer Resources
- Detailed Plugin Guidelines WordPress Plugin Handbook
- Introducing Update URI plugin header in WordPress 5.8 Make WordPress Core
- libcurl error codes curl
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


