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.
After Recovery
Once Admin is available again, confirm the affected page or feature works and review the error that caused the interruption. Use Verify Installed Packages when Micro CMS reports an integrity problem or when filesystem integrity is part of what failed; it is not a required ritual after every successful recovery.