Update problems
Recover safely from a failed or interrupted update without mixing Core versions or duplicating the operation.
Treat an update failure as one operation. Do not repeatedly replace files or start the same update while its current state is unresolved.
Read the current state
Record the version, visible status and error. A queued operation may be waiting for background processing; an interrupted Core change may direct you to Recovery.
If Updates offers Retry
Correct the reported cause first, then use the offered Retry action. If a failed combined Bridge update is blocking progress, the supported Core Only path can update public Core independently.
If normal Admin will not load
Open /recovery.php and sign in. Use Core & Updates for Core repair or temporary rollback, and Bridge Recovery when an existing Bridge installation needs separate recovery.
Check Site Health after recovery
After Admin is available, review Site Health → Errors, run Verify Installed Packages and load a representative public page before starting another update.