Record the update that was started, when it began and any completion or failure message. Check the hosting or management tool's task status and avoid launching another update in parallel.

A maintenance plugin or hosting-level maintenance feature can produce a similar public message without using WordPress core's update marker. Identify which mechanism is active before changing files.

1. Check whether the administration dashboard or management interface reports the task as complete.
2. Review relevant logs for a timeout, download failure, storage problem or permissions error.
3. Confirm that no update process is still writing files.
4. Use the supported maintenance control, or have an authorised administrator remove a stale .maintenance marker from the correct WordPress root only after the stopped state is verified.
5. Open the public site and inspect the update result immediately.

Check the reported WordPress, plugin or theme version that was being updated. Test the affected component and look for missing-file or fatal errors. If the package is incomplete, repair it through the supported update or trusted replacement workflow rather than declaring success because the maintenance message disappeared.

Keep a backup and account for any database migrations. Replacing older code after a completed database update may not be a safe rollback.

Review disk space, PHP limits, package download access and file permissions. If the same update repeatedly fails at the same point, collect the error and stop rerunning it without a changed condition.

If the public page still shows maintenance after the application is healthy, inspect page caches and any separate maintenance plugin. Do not delete arbitrary hidden files from the site root in an attempt to remove the message.

Test login, navigation and critical forms or checkout. Confirm temporary maintenance controls are off only where intended and that scheduled jobs continue normally.

When asking for assistance, provide the site, exact update attempted, approximate start time and error details. A clear timeline helps distinguish a stale marker from an active update or a separate maintenance feature. Removing the marker is a final state correction, not a substitute for checking that the application files and database are coherent.

• Updating WordPress safely from the administration dashboard
• Troubleshooting a WordPress update download failure
• Checking WordPress core file integrity with WP-CLI
• Resolving the editor's invalid JSON response error

• WordPress documentation
• WordPress developer documentation
• WP-CLI maintenance mode