An update download failure can occur before any files are replaced, but inspect the reported state before assuming the installation is unchanged. Check the package source, network access, storage and licence requirements for the specific component.
IN THIS ARTICLE
01 Record the exact update
Note whether the failure concerns WordPress core, a directory plugin, a commercial extension or a theme. Record the current and intended versions and the full error message. A commercial package can require a valid licence or account connection that is unrelated to general WordPress.org access.
Keep a current backup before retrying an update that may write files or migrate data.
02 Check the likely cause
- Review Site Health for outbound-connection or certificate errors.
- Check available disk space and whether the temporary download or upgrade location is writable with appropriate ownership.
- Verify the official package source and any required licence status.
- Review server logs for DNS, TLS, timeout or HTTP response errors at the attempted update time.
- Check the vendor's official service status or release information when its package endpoint appears unavailable.
03 Retry in a controlled way
After correcting a specific issue or confirming a temporary outage has ended, retry once and watch the completion result. Avoid starting several update processes in parallel or repeatedly downloading the same large package on a constrained account.
If a manual ZIP replacement is appropriate, obtain it from the original developer and follow the supported replacement workflow. Do not download a repackaged commercial extension from an unknown source merely because its update server is unavailable.
Should I disable certificate checks to download an update?
Do not disable certificate verification to bypass a TLS error. Correct the server trust, clock, hostname or vendor-side issue instead. A successful insecure download is not a reliable update process.
Check compatibility before replacing code with a different release, especially when the component has database migrations. A file-only downgrade may not restore a coherent application state.
04 Verify the final installation
Confirm the reported version, activation state and key functionality after the update. Review fresh logs and remove a stale maintenance state only after confirming the update is no longer running.
If the failure persists, provide the component, versions, error, time and package source to support without sharing licence secrets. This distinguishes a network or hosting problem from a vendor entitlement issue and avoids unnecessary changes to the rest of the website.