Plan a Manual WordPress Core Update with Verified Recovery

A manual WordPress core update replaces executable files and can require database changes. Do not begin by deleting live directories before a recoverable backup, complete trusted package and maintenance/recovery plan are ready. Prefer the supported built-in update path when appropriate.

Prepare a complete before-state

Verify private backups of both database and files, including uploads, themes/plugins, wp-config.php and custom server rules. Confirm the exact installation path, supported runtime and plugin/theme compatibility. Rehearse a large version jump using the official extended guidance; a file-only rollback may not match an upgraded database.

Download the intended official WordPress release and extract it completely before touching production. Plan controlled maintenance and the plugin deactivation/reactivation sequence. Core modifications can be overwritten; identify them rather than assuming there are none.

Replace only the intended core

1. Connect using approved encrypted file access, verifying service identity and the precise WordPress root.
2. Follow the official procedure for replacing wp-admin and wp-includes with the complete matching release. Avoid leaving a partial mixture of versions accessible during interrupted transfers.
3. Preserve the existing wp-content tree, uploads, custom themes/plugins and wp-config.php. Review release-supplied content files individually; do not replace or delete the entire content directory.
4. Replace the appropriate root core files while preserving unrelated site/configuration files and custom rules. Inspect failed transfers and exact destinations.
5. Complete the authorized WordPress database-upgrade prompt when required, then review version and update state.

Validate before ending maintenance

Review controlled plugin reactivation, login, representative pages, media, forms, scheduled/integration behavior and errors. Clear relevant application/CDN caches deliberately. Remove a stale .maintenance file only after establishing that no update is still running; deleting it is not a repair for incomplete core files.

Do not claim success solely because uploads finished or the dashboard opens. If recovery is required, restore a compatible verified database/files state through the planned procedure. Keep backups outside public directories and never disable encryption or grant broad filesystem access to complete an update.

References: WordPress manual update and content-preservation rules and extended/version-jump guidance.

Reviewed October 16, 2026. No WordPress files, database, maintenance state or production update/recovery was executed.