Free tools Windows power users keep installed
One-click scans. No signup required.
If an automatic WordPress update broke your site, first preserve the current files and database, then identify whether core, a plugin, or a theme changed. A known-good backup is the safest rollback. For WordPress core, WP-CLI can reinstall a specific older release with wp core update --version=<known-good-version> --force. Failed plugin and theme installations on WordPress 6.3 and later may still have a temporary copy available. A fatal error may be isolated with Recovery Mode, while a locked-out dashboard can often be recovered by temporarily renaming the plugins directory.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
What “revert an automatic update” actually involves
WordPress can update three different layers: WordPress core, individual plugins, and themes. The recovery method depends on which layer changed and whether the update failed during installation or completed successfully and then exposed an incompatibility.
As an Amazon Associate I earn from qualifying purchases.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →| What changed | Typical symptom | Most dependable reversal |
|---|---|---|
| WordPress core | PHP errors, broken administration screens, white screen, or broad incompatibility after a version change | Restore a complete backup or reinstall a known-good core release with WP-CLI |
| Plugin or theme update failed during installation | Update notice reports failure, or the item is unavailable immediately after the attempt | Use WordPress 6.3+ temporary update backup when present, or restore a backup |
| Plugin or theme update completed but is incompatible | Fatal error, broken layout, missing feature, or errors that began after a successful update | Recovery Mode, then restore or reinstall the previous known-good version |
| Several changes occurred together | Multiple unrelated errors and no clear culprit | Restore a complete files-and-database backup from before the update |
A plugin or theme copy is not the same as a full site restore. The database contains settings, content, orders, form entries, and other data that files alone cannot recover. Conversely, a database dump does not contain your WordPress files. Treat both as required for a dependable rollback.
First response: preserve evidence and stop further changes
Do not delete the current installation or repeatedly run updates while diagnosing the problem. Keep one copy of the broken state in case a host technician or developer needs to inspect it.
#1 Best Overall
- 110 Sheets Log Book: This vehicle maintenance log book includes 110 record sheets to track repairs, services, fuel costs, and other vehicle-related expenses. It also comes with 36 convenient “Service Due” stickers to help remind you of upcoming maintenance schedules. Everything you need to keep your car records organized in one place.
- Detailed Information: Each page is carefully structured with dedicated sections for date, mileage, service description, parts replaced, vehicle information, cost, and additional notes. The clear and organized format allows you to maintain accurate records, monitor repair history, and better manage long-term vehicle performance and expenses.
- Enough Writing Space: The record sheets provide ample space for clear and thorough entries. Whether you’re documenting routine oil changes or major repairs, there’s plenty of room to write detailed information without feeling cramped.
- Easy to Use: The spiral binding allows the notebook to lay flat for comfortable writing, making entries quick and convenient. The included 36 “Service Due” stickers can be placed inside the book or on visible surfaces like your windshield or dashboard, helping you keep important maintenance reminders in sight.
- Proper Size: This compact logbook measures 5.5” x 7.1”, which fits easily in your glove compartment, center console, backpack, or desk drawer. Its portable size ensures you can access and update your vehicle records anytime, whether at home, in the garage, or at the service center.
- Record versions. In the dashboard, note the WordPress version, active theme, and every recently updated plugin. If the dashboard is unavailable, use WP-CLI commands such as
wp core version,wp plugin list, andwp theme listfrom the site directory. - Capture the timing. Write down when the alert arrived and which pages fail: public pages, login, dashboard, checkout, forms, feeds, or scheduled tasks. This helps distinguish a core failure from one extension.
- Create a complete backup before changing anything. Export the database and copy the entire WordPress files directory, including
wp-content,wp-config.php, and server-level configuration that your host exposes. Label it with the date and current versions. - Put the site in a safe state. If visitors are seeing partial transactions or corrupted output, use your host’s maintenance controls while you work. Do not disable security controls permanently just to make troubleshooting easier.
WordPress recommends regular backups before enabling plugin and theme auto-updates. A backup made after the update is useful for investigation, but the rollback point you need is normally the last verified backup from before the update.
Revert a WordPress core update
Option 1: restore a pre-update backup
Restoring the files and database from a known-good snapshot is the safest way to undo a completed core update, especially when the update also changed plugins, themes, or database structures. Use the restore workflow supplied by your host or backup system, and confirm that it restores both components rather than only the database.
After restoration, prevent the same update from running immediately, check the site while it is private or in maintenance mode, and then test the front end and administration area. Keep the broken-state backup until you have confirmed that the restored site is usable.
Option 2: reinstall a specific core version with WP-CLI
When you know exactly which release worked and have shell access, WP-CLI can install that version directly. The documented pattern is:
wp core update --version=<known-good-version> --forceFor example, the WordPress Developer Blog gives:
wp core update --version=6.5.4 --forceThe --version option selects the release, and --force is required when the requested version is older than the installed one. Run the command from the WordPress installation directory as the account that owns the site files, or use the host’s documented WP-CLI invocation.
- Confirm the target version from your version record or pre-update backup; do not guess.
- Make the files-and-database backup described above.
- Run the command with the exact version number.
- Open the site and dashboard, and follow any database-upgrade prompt shown for that release.
- Inspect logs and test critical workflows before removing maintenance mode.
A core downgrade can reveal incompatibilities in plugins or themes that were updated for the newer release. If the site remains broken after core is restored, compare extension versions with the backup and roll back the extension that introduced the conflict.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #2
- All In One Equipment Maintenance Log Book With Detailed Fields：This equipment maintenance log book is designed for complete tracking of machinery and equipment performance Featuring pre-printed sections for Equipment Name Manufacturer Name Model Number Serial Number Purchase Date Item Location and Additional Information this repair log book ensures accurate and consistent service records
- Includes Maintenance Schedule Fields for Time and Task Recording：Each page includes dedicated spaces for Date and Time Maintenance Task or Remarks Performed By and Cost helping you record maintenance frequency track service intervals and monitor expenses Ideal for preventive maintenance logs and repair history documentation
- Large Format Repair Log Book With Continuation Pages：Sized at 8.5 x 11 inches this equipment service record notebook provides generous space for writing and includes 110 Pages with continuation pages to extend entries when needed Ensures that even complex service reports are kept complete and organized
- Durable Spiral Bound Construction for Long Term Use：Built with a 300gsm laminated cover and strong spiral binding this maintenance log notebook lies flat for easy writing and endures frequent handling in demanding environments from factory floors to fieldwork sites
- Ideal for Industrial Commercial and Personal Equipment Tracking：Whether you’re managing heavy machinery in construction agricultural tools in farming or facility systems in schools or warehouses this maintenance record book helps technicians engineers and facility managers maintain consistent and accessible logs
Roll back a plugin or theme update
When the installation failed on WordPress 6.3 or later
WordPress 6.3 introduced a temporary rollback mechanism for failed manual plugin and theme installations. During the update, WordPress moves the previous copy into a temporary path:
wp-content/upgrade-temp-backup/plugins/PLUGINNAMEwp-content/upgrade-temp-backup/themes/THEMENAMEMake WordPress Core documents this as protection when an update fails. The folders are temporary working copies, not a historical archive. The mechanism is intended for a failed installation, not for choosing any old version after a successful update.
- Back up the database and files before touching the temporary directory.
- Check the update notice and server error log to confirm that installation failed rather than completed.
- Look for the affected item under the appropriate
upgrade-temp-backupsubdirectory. - Use the host’s file manager or FTP to restore the prior copy according to its normal plugin or theme directory structure.
- Load the dashboard and public site, then activate the item and test it in isolation.
Do not assume the temporary copy will remain indefinitely. A later successful update can clear it, so copy any needed recovery files to a secure location only after creating a complete backup.
When the update completed but caused an incompatibility
A completed update that breaks the site needs a known-good older package or a backup. If you have a verified pre-update backup, restore the affected plugin or theme files and the database state that belongs with them. If you have the previous release’s official ZIP archive, install that exact release after deactivating the broken one. Verify that the package comes from the project’s legitimate distribution channel and matches your PHP and WordPress requirements.
Recommended Free Tools
Do not overwrite a live extension blindly. Preserve the current version first, because its logs and files may identify the incompatibility. A downgrade can also leave database settings created by the newer release; check the extension’s own rollback guidance and test every feature that writes data.
Use Recovery Mode for a fatal plugin or theme error
Recovery Mode, introduced in WordPress 5.2, is designed to regain access when a fatal error is caused by a plugin or theme. WordPress sends a Recovery Mode link to the site administrator’s email when it detects a qualifying fatal error. WordPress.org describes the feature as a way to access the site without immediately using FTP or editing code.
- Open the Recovery Mode link in the administrator email on the same site.
- Sign in with the affected administrator account.
- WordPress pauses the faulty plugin or theme for that administrator session.
- Deactivate the item, switch to a compatible theme, or apply the vendor’s documented fix.
- Exit Recovery Mode and test the public site and ordinary dashboard sessions, not only the recovery session.
Recovery Mode does not permanently repair the extension or roll back its files. It creates an opportunity to disable the trigger and perform a proper restore or reinstall. If no email arrives, check the administrator address, spam filtering, and server mail logs; then use the file-access procedure below.
Recover when wp-admin is unavailable
Temporarily deactivate all plugins by renaming the directory
WordPress troubleshooting documentation notes that renaming the plugins directory deactivates plugins while preserving their files. Use FTP or your host’s file manager:
- Open the WordPress installation directory.
- Rename
wp-content/pluginsto a temporary name such asplugins.disabled. - Try the login and the public site.
- If access returns, rename the directory back to
plugins. - Reactivate plugins one at a time, testing after each activation to identify the offender.
Renaming the directory is a diagnostic switch, not a permanent fix. Do not delete it. If the site still fails with all plugins unavailable, inspect the active theme, core version, PHP error log, and server configuration. A host can help with permissions, PHP version changes, and restoring a snapshot when file access is insufficient.
When the theme is the trigger
If a theme update caused the fatal error, use Recovery Mode to switch to a default theme, or rename the active theme’s directory through FTP/file manager so WordPress can fall back to an available default theme. Keep the original directory intact for later analysis. Theme changes can affect widgets, menus, templates, and customizer settings, so test the layout and editing screens after access is restored.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Disable the automatic update that caused the problem
Dashboard controls
WordPress introduced per-plugin and per-theme auto-updates in version 5.5. In the dashboard, open Plugins > Installed Plugins or Appearance > Themes, locate the affected item, and use its auto-update toggle or action. Disable only the item you are investigating, unless you have a documented reason for a broader policy.
Enabled plugin and theme auto-updates normally run twice per day. Turning off a toggle prevents the next automated attempt; it does not undo the version already installed.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteWP-CLI controls
With shell access, disable a specific plugin or theme:
wp plugin auto-updates disable <plugin>wp theme auto-updates disable <theme>Use the plugin slug shown by wp plugin list and the theme stylesheet slug shown by wp theme list. Verify the setting afterward with the corresponding list command or dashboard label.
Site-wide and selective policy code
For centrally managed sites, WordPress supports configuration constants and the auto_update_plugin and auto_update_theme filters. Add policy code only after documenting who will review updates and how restores are performed. A site-wide disable can leave security fixes unapplied; WordPress documentation discourages disabling all security updates. A safer policy is to exclude a known-incompatible item while scheduling prompt manual review of every pending update.
Choose the right recovery path
| Situation | Access available | Action | What to verify |
|---|---|---|---|
| Core update broke the site | WP-CLI or host restore | Restore the pre-update backup, or run wp core update --version=KNOWN --force |
Front end, login, database prompt, PHP logs, scheduled jobs |
| Plugin/theme update failed mid-install | File access | Inspect wp-content/upgrade-temp-backup/ and restore the prior copy |
Item activates, files are complete, no fatal error |
| Successful extension update causes fatal error | Recovery email | Enter Recovery Mode, deactivate the item, then restore or reinstall the known-good version | Public and admin sessions outside Recovery Mode |
| Dashboard is completely locked | FTP or file manager | Rename wp-content/plugins; restore the name and reactivate individually |
Whether the failure follows a plugin or remains with core/theme |
| No known-good version or backup | Host/developer assistance | Preserve the current site, obtain the exact previous package if available, and request a host snapshot | Compatibility, file ownership, database integrity, and a new restore point |
Validate the site after a rollback
Do not judge success by whether the home page loads. Test the functions that can lose data or revenue:
- Public pages, navigation, search, feeds, and media.
- Administrator login, editing, publishing, and user management.
- Forms, email delivery, spam protection, and file uploads.
- Commerce checkout, payment callbacks, taxes, coupons, and order status if the site sells anything.
- Scheduled jobs, cron tasks, background queues, imports, backups, and analytics events.
- Permalinks, REST API responses, XML sitemaps, and webhooks used by other systems.
- PHP and web-server logs for new warnings or fatal errors.
Clear caches only after recording the failure and confirming that the rollback is stable. Purge page, object, CDN, and browser caches in a controlled order so a stale copy is not mistaken for a repaired site.
Prevent the next surprise update
Keep a written update policy that states who approves core, plugin, and theme changes; which environment receives a test first; and how long backups are retained. Before enabling an automatic update, confirm that the backup completed and that a restore has been tested at least once. For high-value sites, use staging to test PHP, WordPress, extensions, forms, scheduled jobs, and payment workflows together.
When you disable an auto-update, record the item, reason, current version, and review date. Re-enable updates after the incompatibility is fixed instead of leaving a security-sensitive extension frozen indefinitely. Managed WordPress hosting or a backup service may provide scheduled file-and-database snapshots and assisted restores, but retention, restore process, geography, and support terms differ; verify those details before relying on one.
Quick Recap
Common mistakes to avoid
- Restoring only the database: this leaves the incompatible files in place.
- Copying only plugin files: this cannot recover changed content or settings stored in the database.
- Deleting the current version first: you lose logs and a forensic copy that may be needed.
- Treating the temporary backup as an archive: WordPress may clear it after a successful update.
- Downgrading core without checking extensions: plugins and themes may require the newer release or PHP behavior.
- Testing only while in Recovery Mode: the faulty item is paused for that session, so ordinary visitors may still see the failure.
- Disabling every security update indefinitely: this increases exposure; isolate the exception and schedule manual review.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
