iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
If an automatic WordPress update broke your site, first identify whether WordPress core, a plugin, or a theme changed. Preserve the current files and database, then restore a known-good backup or roll back with the method that matches the failure: WP-CLI for core, WordPress’s temporary rollback for a failed plugin or theme installation, Recovery Mode for a fatal error, and a backup or manual reinstall for a completed but incompatible update.
Do not delete the current site before you have a restorable copy. A rollback can expose other compatibility problems, so test the public site, administration screens, scheduled tasks, forms, payments, and publishing workflows afterward.
Identify exactly what changed
“Automatic update” can mean a WordPress core release, a plugin, a theme, or several items updated during the same maintenance window. The rollback procedure depends on which one changed and whether its installation actually completed.
- Check the WordPress dashboard. Look at Dashboard > Updates, the Plugins screen, and Appearance > Themes. Record the current WordPress version and every plugin and theme version shown there.
- Check update and error notifications. The administrator email may identify the component that failed and may contain a Recovery Mode link.
- If you have shell access, record versions with WP-CLI.
wp core versionshows the core version;wp plugin listandwp theme listshow installed versions and status. - Note the first symptom and its time. A white screen, a PHP fatal-error message, a missing layout, a failed form, or an inaccessible dashboard points to different recovery steps.
Keep a copy of these notes. They let you verify that the rollback restored the intended release rather than merely making the site load again.
#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.
Choose the rollback method
| What happened | Best first method | What must be true | Important limitation |
|---|---|---|---|
| WordPress core changed and the previous release is known | Restore a backup or run WP-CLI with a specific version and --force |
You know the target version and have hosting or command-line access for WP-CLI | A downgrade can reveal incompatibilities in plugins, themes, or custom code |
| A plugin or theme update failed during installation | Use WordPress 6.3 or newer’s temporary update backup | The failure occurred while WordPress was installing the update and the temporary copy still exists | This is not a permanent version archive and does not provide an arbitrary historical version after a successful update |
| A plugin or theme update completed, then caused a fatal error | Open the Recovery Mode link and deactivate or repair the component | The administrator can access the email account that receives the Recovery Mode message | Recovery Mode pauses the faulty component for that administrator session; it does not restore every file or database change |
| The dashboard is unavailable | Use Recovery Mode, the host’s tools, or temporarily rename the plugins directory | You have administrator-email, hosting, FTP, or file-manager access | Renaming the directory deactivates plugins but leaves their files in place; it is a diagnostic step, not a version rollback |
| The update completed but is incompatible and no temporary copy remains | Restore a verified files-and-database backup or manually install a known-good release | A backup or an exact older package is available | Installing an older package without a database and file backup may leave data or configuration changes from the newer release |
Make a complete backup before changing anything
A rollback is safest when you can return to the current state. Save both parts of the site:
- Database: Export the WordPress database, including posts, pages, users, settings, orders, form entries, and plugin tables.
- Files: Copy
wp-content, uploaded media, themes, plugins, and the WordPress configuration file. A full document-root backup is preferable when your host supports it. - Environment notes: Record the PHP version, active theme, server, and any special cron or caching configuration if those details are available.
Do not overwrite your only backup with the rollback attempt. Store the copy outside the live document root or use a host snapshot that can be restored independently. WordPress recommends regular backups before enabling plugin and theme auto-updates because a backup is the dependable fallback when a completed update must be reversed.
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 →Repair Windows errors before they cause bigger problemsFix Now →Revert a WordPress core update
Option 1: Restore a known-good backup
If the site worked before the core update and you have a backup from that point, restoring the matching files and database is usually the most complete reversal. Restore the core files and the wp-content state together, then restore the database from the same backup set. Mixing a database from one point in time with files from another can produce confusing settings, missing tables, or incompatible plugin data.
Use your host’s documented restore process or ask support to perform it if you cannot verify that the backup is complete. After the restore, clear any server or page cache only if your hosting instructions require it, and log in to confirm the restored version.
Option 2: Use WP-CLI to install the specific older release
WP-CLI’s core update command accepts a target release. When the target is older than the installed version, include --force:
wp core update --version=<known-good-version> --forceFor example, the WordPress Developer Blog gives this concrete command:
Recommended Free Tools
wp core update --version=6.5.4 --force- Put the site in a maintenance window and confirm that the database and files are backed up.
- From the WordPress installation directory, run the command with the exact release you intend to restore.
- Run
wp core versionand confirm that it reports the target version. - Open the front end and
/wp-admin/. Check for PHP errors, missing assets, and database-update prompts. - Exercise the site’s important workflows before re-enabling automatic updates.
WP-CLI can replace core files, but it cannot undo changes that a newer core release or a plugin made in the database. If the site remains broken, restore the verified backup rather than repeatedly changing versions.
Handle a plugin or theme update that failed during installation
WordPress 6.3 introduced a rollback mechanism for failed manual plugin and theme installations. During an update, WordPress moves the old copy into a temporary location:
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
wp-content/upgrade-temp-backup/plugins/PLUGINNAMEwp-content/upgrade-temp-backup/themes/THEMENAMEWhen the new package cannot be installed successfully, WordPress can use that temporary copy to restore the previous version. The exact folder name contains the affected plugin or theme, so do not remove the directory while diagnosing the failure.
What this mechanism can and cannot do
- It is intended for an update that failed during installation, such as an interrupted or unsuccessful replacement.
- It is not a “choose any old version” control after an update completed normally.
- The temporary backup is cleared after a successful update, so it should not be treated as a historical version archive.
- It protects the old files, not necessarily database changes made before the failure. Keep a database backup as well.
If WordPress reports that the update failed, follow the recovery notice and then inspect the plugin or theme’s status. If the site still fails, use Recovery Mode or restore the backup made before the update.
Recover from a fatal error with Recovery Mode
Recovery Mode was introduced in WordPress 5.2. When WordPress detects a fatal plugin or theme error, it can send the administrator an email containing a special link. Recovery Mode pauses the faulty plugin or theme for that administrator session so the dashboard can load without immediately executing the failing component.
- Open the Recovery Mode message sent to the site administrator email address.
- Follow the link and sign in when prompted.
- Read the error details and identify the plugin or theme named in the notice.
- Deactivate the component, install a compatible release, or contact its developer with the exact PHP error.
- Exit Recovery Mode, then test the public site and normal administrator screens in a separate browser session.
Recovery Mode is an access and diagnosis tool, not a complete rollback. It does not automatically restore a prior plugin package, reverse database migrations, or repair unrelated components. If the error returns after you leave Recovery Mode, restore the known-good backup or install the exact older package you have verified.
Regain dashboard access when the site is locked out
Temporarily deactivate all plugins through the file system
When /wp-admin/ and Recovery Mode are unavailable, use your host’s file manager, FTP, or another documented file-access method. In the WordPress installation, rename:
wp-content/pluginsFor example, change it to plugins-disabled. WordPress treats the original directory as unavailable and deactivates the plugins while preserving their files. Try the front end and dashboard again.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Once access returns, rename the directory back to plugins. Reactivate plugins one at a time and test after each activation. The plugin whose activation brings back the failure is the likely cause. Leave it deactivated until you have a compatible release or a restore point.
If renaming the directory does not help, ask the host to inspect PHP error logs and restore a snapshot if one exists. Avoid deleting plugin or theme folders: deletion removes the only copy you may need for diagnosis.
Reverse a completed plugin or theme update that is incompatible
A successful installation followed by a broken layout, missing feature, or fatal error is different from a failed installation. WordPress’s temporary update backup is not a permanent rollback archive, so the dependable choices are a backup restore or a manual installation of a known-good package.
Restore the complete pre-update state
If you have a backup made before the update, restore the files and database as a coordinated set. This is the best choice when the update changed database tables, options, custom post data, or serialized settings in addition to replacing files.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesManually install a specific older package
If you have an exact older plugin or theme package and the problem is limited to its files, replace the current package through the dashboard, FTP, file manager, or your host’s deployment tool. Deactivate the component first when possible, install the known-good version, and then verify the site. Keep the current package and your backup until testing is complete in case you need to return to it.
Do not assume that an older package can safely read data written by the newer one. Check the component’s release notes and test forms, editor screens, scheduled jobs, and any commerce or publishing workflow that depends on it.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Stop the same automatic update from running again
Disable one plugin or theme in the dashboard
WordPress introduced per-plugin and per-theme automatic updates in version 5.5. In the dashboard, open Plugins > Installed Plugins and use the affected plugin’s automatic-update control. For a theme, open Appearance > Themes, select the theme, and use its automatic-update control when the option is available. Disable only the item you are investigating, then keep a manual review schedule.
Automatic plugin and theme updates normally run twice per day. Turning off one item prevents the next scheduled attempt but does not undo the version already installed.
Disable one item with WP-CLI
With command-line access, use the item’s slug:
wp plugin auto-updates disable <plugin>wp theme auto-updates disable <theme>Confirm the setting with the corresponding list command or in the dashboard. The slug is usually the directory name for a plugin or the theme directory identifier, not necessarily the display name.
Apply a site-wide or selective policy in configuration
For centrally managed sites, WordPress supports configuration constants and the auto_update_plugin and auto_update_theme filters. A site-wide constant can stop automatic updates, while filters let developers allow or deny updates selectively. Put policy code in the appropriate configuration or must-use plugin location, test it on a staging copy, and document who will review updates manually.
Disabling every automatic update, including security updates, is discouraged by WordPress documentation. If you create an exception, assign an owner and a recurring review date so security fixes are not forgotten. A safer policy is often to hold only the incompatible component while allowing appropriate security maintenance elsewhere.
Verify the site after a rollback
Loading the home page is not enough. Use a checklist that reflects how the site is used:
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall- Open several public pages, category or archive pages, search, and the 404 page.
- Sign in and sign out with an administrator account and, if relevant, a normal user account.
- Create and edit a test post or page, preview it, upload media, and confirm the editor works.
- Submit every important form and verify that notifications and stored entries arrive.
- Check scheduled posts, cron-driven imports, backups, feeds, and external integrations.
- For a store or membership site, test login, checkout or payment flows, account pages, and confirmation emails with a safe test transaction.
- Inspect PHP and web-server logs for new errors after the rollback.
- Clear caches only after confirming that the underlying site works; otherwise a cache can hide a remaining failure.
Record the final core, plugin, and theme versions. Keep the pre-rollback backup and the restored copy until the site has passed a normal operating cycle.
Common mistakes and how to avoid them
Deleting the current files before making a backup
Deletion removes evidence and may make it impossible to determine which component failed. Rename or copy files first, and retain the database export.
Using wp core update without the target version
A normal core update command asks for the latest available release. A downgrade requires the known-good version and, when it is older than the installed release, --force.
Expecting Recovery Mode to fix every kind of breakage
Recovery Mode isolates a fatal plugin or theme for one administrator session. It will not repair a syntax error in custom code, a damaged database, a missing file, or a front-end incompatibility that is not fatal.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Treating the temporary update directory as a version library
The upgrade-temp-backup copy exists to recover from a failed installation and can be cleared after a successful update. Maintain real backups when you need historical versions.
Re-enabling updates immediately after recovery
Leave the affected item disabled while you test and identify a compatible release. Re-enable it only after documenting the version and confirming that a current backup exists.
Plan a more controllable update process
Managed WordPress hosting or a backup service can provide scheduled database-and-file backups and assisted restores. Before relying on one, verify its retention period, restore workflow, storage geography, and whether it can restore individual files as well as the complete site. A backup that cannot be retrieved or is missing the database does not provide a dependable rollback.
For self-managed sites, combine regular off-site backups with a written update procedure: record versions, update one component at a time when possible, monitor the site after the maintenance window, and keep a tested restore path. WordPress’s dashboard controls, WP-CLI, and Recovery Mode are free tools, but they work best when a verified backup remains available.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
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.
