A plugin update can fail for reasons that have nothing to do with the plugin itself — a file permission WordPress can’t write to, a connection to the update server that times out, a disk quota reached mid-download — and the error message WordPress shows rarely says which of those actually happened.
Before you buy, one quick look
Read-only if you just look at the Updates screen. If you try updating again to read the error text, one attempt is enough — repeated failed attempts can leave partial files behind that complicate the eventual fix.
“Could not create directory” points somewhere different from “Download failed” or “Destination folder already exists” — three different causes with the same generic symptom of a failed update, and the exact wording narrows which one applies before we even start.
If the error text scrolled past or wasn’t fully visible, trying the update once more just to read it in full is worth the minute it takes, since a partial description sends us down the wrong path from the very first step.
It’s also worth checking whether the failure happens the same way every time or varies slightly — a consistently identical error points at a fixed cause like permissions, while a message that changes between attempts often points at something less stable, like an intermittent connection issue.
Plugin update failure resolution
A specific plugin keeps failing to update, with a generic error that doesn't say why. We find the actual cause — permissions, disk space, connection — and complete the update.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
This or something else?
| A specific plugin update repeatedly failing with an error message | This fix covers it |
| The site broke after an update completed, rather than the update failing | Fatal PHP error after update |
| Multiple plugins failing to update at once | This fix covers it, likely a shared cause |
| You want to revert to the version before a problematic update | Plugin rollback to previous version |
| No error shown, update just seems to do nothing | This fix covers it, worth investigating regardless |
What you are seeing
- A specific plugin repeatedly failing to update, with the same or a similar error each time
- An error message referencing file permissions, disk space, or a connection timeout
- The update button appearing to do nothing, with no confirmation either way
- Other plugins updating normally while one specific plugin consistently fails
- The failure happening the same way whether attempted from wp-admin or elsewhere
Common causes
- File or directory permissions preventing WordPress from writing the new plugin files
- A disk space or hosting quota limit reached during the download or extraction
- A firewall or security plugin blocking the connection to the plugin’s update server
- A corrupted partial download from a previous failed attempt left in place
- A server timeout during a large plugin’s download or extraction process
What we do
- Read the exact error and attempt the update directly to observe the failure firsthand
- Check file and directory permissions relevant to the plugin’s installation path
- Check for disk space, quota, or connection issues specific to your hosting environment
- Clear any corrupted partial files left from previous failed attempts
- Complete the update successfully once the underlying cause is resolved
- Confirm the plugin functions correctly on the newly updated version
What is included
- The specific cause of the update failure identified and resolved
- The update completed successfully to the current version
- A note on what was actually causing it, for future reference
- The pre-update backup, kept for 30 days
Not included
- Fixing bugs introduced by the plugin’s new version itself, which is the plugin author’s responsibility
- A hosting upgrade, if that’s genuinely what the limit requires
- Ongoing update monitoring for other plugins
- Reverting to an older version, which is a separate, related fix
Questions about this fix
Is it safe to keep trying the update myself while I wait?
A few attempts won't cause harm, but repeated failed attempts can sometimes leave partial files behind that complicate the eventual fix, so it's worth stopping and ordering once you've confirmed it's not a one-off.
Could this be affecting other plugins too, even if they're updating fine right now?
Possibly, if the cause is a shared hosting limit like disk space — we check whether it's isolated to this one plugin or a sign of something that will affect others soon.
Will fixing this also fix the plugin's own bugs?
No — this resolves the update process itself. If the plugin has bugs in its new version once successfully updated, that's a separate issue for the plugin's own support.
Why does the error message never say what's actually wrong?
WordPress's update mechanism reports fairly generic failure states rather than detailed diagnostics, which is exactly why the underlying cause usually needs checking directly rather than trusting the message alone.
Can this happen with theme updates too?
Yes, the same underlying causes — permissions, disk space, connection issues — apply to theme updates as well, and the diagnosis approach is the same.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.