Windows 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 reinstallOutdated 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 matchIf an automatic WordPress update broke your site, first identify whether WordPress core, a plugin, or a theme changed, then preserve the current files and database. Restore a verified backup whenever possible. For a core rollback without a backup, WP-CLI can install a specific older release with wp core update --version=<known-good-version> --force. A failed plugin or theme installation may have a temporary copy available on WordPress 6.3 and newer, while a completed incompatible update normally requires a backup restore or a deliberate reinstall of a known version.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
Do not delete the current site before you have a restorable copy. The recovery method depends on what changed, whether the previous version is known, and whether you can reach the dashboard, Recovery Mode, WP-CLI, or your host’s file and database tools.
As an Amazon Associate I earn from qualifying purchases.
Recommended Free Tools
Choose the rollback path before changing anything
An automatic update can affect three different layers. Core is the WordPress application itself. Plugins and themes are separate packages that can become incompatible with the current PHP version, core release, or with one another. A failed installation and a successfully installed update that later causes errors are also different situations.
| What changed | What you see | Most dependable recovery |
|---|---|---|
| WordPress core | Dashboard reports a newer WordPress version, or the site fails immediately after a core update | Restore a known-good full backup, or use WP-CLI with a specific version and --force |
| Plugin or theme installation failed | Update process reports an error or leaves the package unusable during installation | On WordPress 6.3+, check the temporary upgrade backup directory and restore the prior copy |
| Plugin or theme update completed, then caused a fatal error | White screen, HTTP 500, or a fatal-error notice after the update | Use the Recovery Mode email link, deactivate the faulty package, and repair or restore it |
| Dashboard unavailable | You cannot reach wp-admin to deactivate or roll back anything | Use Recovery Mode, WP-CLI, hosting tools, or temporarily rename the plugins directory |
Write down the exact versions before proceeding. The dashboard’s Updates, Plugins, and Themes screens show installed versions; WP-CLI can record them from the site directory:
#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.
wp core version
wp plugin list --fields=name,status,version,update
wp theme list --fields=name,status,version,updateSave this information, the time of the failure, and any fatal-error text. A version number in a log or email is often the difference between a controlled rollback and guesswork.
Make a restorable backup of the current state
Before replacing files or changing the database, make a complete copy of both. WordPress guidance recommends regular backups before enabling plugin and theme auto-updates because a backup is the dependable fallback when a completed update must be reversed.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errors- Back up the database. Export the database with your host’s backup tool or a trusted command-line process. Keep the export outside the live web root.
- Back up the files. Include
wp-content,wp-config.php, the web-server rules file, and the WordPress core files. Store the archive separately from the site. - Label the copy. Record the domain, UTC time, core version, plugin and theme versions, PHP version if your host displays it, and whether the site was working before the update.
- Protect the evidence. Keep the current broken files until the rollback is verified. Do not overwrite your only copy with an older archive.
If your host offers scheduled file-and-database backups with assisted restores, check its retention period, restore scope, storage geography, and whether a restore can be tested on a staging copy. Those details vary by provider; do not assume that a daily backup includes both the database and uploads.
Revert a WordPress core update
Restore a known-good backup first
A full backup made before the automatic update is the lowest-risk core rollback. Restore the matching files and database together when both changed. Restoring only files can leave database migrations from the newer core in place, while restoring only the database can remove content created after the backup. If you need posts, orders, form entries, or other data created since the backup, ask your host whether it can restore files separately or clone the backup to staging for selective recovery.
Use WP-CLI when the previous core version is known
WP-CLI documents the --version option for a specific release and --force when the requested release is older than the installed one. From the WordPress directory, run:
wp core update --version=<known-good-version> --forceThe WordPress Developer Blog gives this concrete example:
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →wp core update --version=6.5.4 --force- Confirm that the target release is the version that last worked, not merely an older number.
- Put the site in a maintenance window if visitors could submit content or payments while files are being replaced.
- Run the command as the account that owns the WordPress files, or use the host’s approved WP-CLI method.
- Check the command output for download, permission, or checksum errors. Do not delete files manually if the command fails.
- Run
wp core version, open the dashboard, and test the front end after the command completes.
A core downgrade can expose a different incompatibility: a plugin or theme may require the newer core, or the older core may not support a newer PHP environment. Treat the rollback as a diagnostic step, not proof that the older release is a permanent solution.
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 installation failed on WordPress 6.3 or newer
WordPress 6.3 introduced rollback handling for failed manual plugin and theme installations. During an update, WordPress moves the old package to a temporary location:
wp-content/upgrade-temp-backup/plugins/PLUGINNAME
wp-content/upgrade-temp-backup/themes/THEMENAMEMake WordPress Core describes these directories as temporary backups used when an update fails. If the update process reports failure, inspect the relevant directory with your host’s file manager, SFTP, or shell access. Preserve the temporary copy before attempting another update, then restore the prior package using your host’s documented procedure or ask support to do it safely.
This mechanism is not a historical version archive. It is intended for a failed installation, and the temporary copy can be cleared after a successful update. If the update completed successfully and the site broke later, do not assume that this directory still contains the version you need.
When the update completed but the package is incompatible
For a completed update, use a backup made before the change whenever possible. If no backup exists, obtain the exact older package from the developer or your organization’s release archive and verify that it matches the site’s PHP and WordPress requirements. A package that merely has a lower version number is not automatically safe.
With WP-CLI, a known plugin version can be requested explicitly:
wp plugin update PLUGIN_SLUG --version=KNOWN_GOOD_VERSION --forceFor a theme, the equivalent form is:
wp theme update THEME_SLUG --version=KNOWN_GOOD_VERSION --forceUse these commands only when the slug and package version are known and available from a trusted source. Record the current package first, test the result on a staging copy when possible, and avoid overwriting the only copy of the newer package. If the package has changed its database schema, rolling back files alone may not undo those schema changes; a database restore or the developer’s documented migration path may be required.
Use Recovery Mode for a fatal plugin or theme error
Recovery Mode was introduced in WordPress 5.2. When WordPress detects certain fatal errors, it sends an administrator an email containing a special link. Recovery Mode pauses the faulty plugin or theme for that administrator session, which can restore access without FTP or direct code edits.
- Open the Recovery Mode link from the administrator email in the same browser where you will repair the site.
- Read the error details and identify the plugin or theme named in the notice.
- Deactivate the faulty package, or update it to a compatible release if the error page provides that option.
- Exit Recovery Mode, then test the public site, login, dashboard screens, scheduled jobs, forms, publishing tools, and payment workflows.
- Only reactivate the package after confirming that its version supports the current core and PHP environment.
Recovery Mode pauses the problem for the session; it does not create a permanent rollback or repair corrupted files. If the email never arrives, check the administrator address, spam filtering, and your host’s mail logs. Continue with the dashboard, WP-CLI, or file-manager procedure below.
Recover when wp-admin is unavailable
Temporarily deactivate all plugins with file access
WordPress troubleshooting documentation describes a reversible file-based method: use FTP or your host’s file manager to rename wp-content/plugins, for example to plugins.disabled. WordPress then treats the plugins as unavailable while preserving their files.
- Back up the directory before renaming it.
- Rename
wp-content/pluginsto a temporary name. - Try to log in to wp-admin and confirm whether the fatal error is gone.
- Rename the directory back to
plugins. - Reactivate plugins individually, testing the site after each activation so the offending package is isolated.
This method does not roll back files; it only disables plugins. If the active theme is responsible, ask the host for help or use a staging copy and a known-good theme while preserving the original theme directory. Avoid deleting a theme or plugin to make the error disappear, because deletion can remove settings, translations, or custom files you still need for recovery.
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
Per-plugin and per-theme auto-updates were introduced in WordPress 5.5. In wp-admin, open Plugins > Installed Plugins, find the affected plugin, and use its Automatic Updates control to turn updates off. For themes, open Appearance > Themes, select the theme, and use its automatic-update control. The exact control is shown only when the package and site configuration support it.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Disabling the toggle prevents an immediate repeat but does not fix the incompatibility. Keep a manual review date and update the package after checking its changelog, WordPress compatibility, PHP requirements, and a tested backup.
Disable one item with WP-CLI
WP-CLI provides separate commands for plugins and themes:
wp plugin auto-updates disable PLUGIN_SLUG
wp theme auto-updates disable THEME_SLUGRun the corresponding enable command only after testing the replacement version:
wp plugin auto-updates enable PLUGIN_SLUG
wp theme auto-updates enable THEME_SLUGWordPress normally runs enabled plugin and theme auto-updates twice per day. A disabled item therefore needs an owner and a scheduled manual check; otherwise security and compatibility fixes can be missed indefinitely.
Free tools Windows power users keep installed
One-click scans. No signup required.
Apply a site-wide or selective policy in code
For centrally managed sites, WordPress supports configuration constants and the auto_update_plugin and auto_update_theme filters. A constant in wp-config.php can disable automatic updating broadly, while filters allow a developer to return true or false for selected plugins or themes.
Use the narrowest policy that meets the operational need. A blanket block can also stop security updates, which WordPress documentation discourages. If you must hold updates, document the exception, monitor security advisories, and schedule a manual update window with a tested backup. Keep code changes in version control and make them on staging first; a syntax error in wp-config.php can lock the whole site out of the dashboard.
Verify the site after a rollback
Do not judge success solely by whether the home page loads. Run a short acceptance checklist while the rollback state is still easy to reproduce:
- Confirm the core, plugin, and theme versions shown in wp-admin or by WP-CLI.
- Open the home page, representative game or article pages, search, menus, and media.
- Log in and out with an administrator and a normal user account.
- Submit a form and verify the notification or stored entry.
- Check publishing, scheduled posts, background tasks, and cron-triggered jobs.
- For stores, memberships, or donations, test cart, checkout, account, confirmation, and webhook flows in a safe environment.
- Inspect the PHP error log and WordPress debug log for new notices or fatal errors.
- Clear page, object, and CDN caches only after confirming that the files and database are consistent.
If the site works only with all plugins disabled, reactivate them one at a time. If the front end works but wp-admin does not, test the affected administrator account, permissions, and the plugin’s admin-only code before changing core again.
Diagnose the common rollback failures
| Symptom | Likely cause | Next action |
|---|---|---|
| WP-CLI refuses an older core version | The requested release is older than the installed one and force was omitted | Confirm the target, then use wp core update --version=TARGET --force |
| The temporary plugin/theme backup is absent | The update succeeded, the temporary directory was cleared, or the site is older than WordPress 6.3 | Restore a pre-update backup or obtain the exact known-good package |
| Recovery Mode link works but the public site still fails | A second plugin, theme, core file, or server-level error is involved | Keep the named package inactive, inspect logs, and test other components individually |
| Renaming plugins fixes the site, but reactivation breaks it | One plugin is incompatible or its files are damaged | Restore the directory name and reactivate packages one at a time; roll back the identified package |
| Rollback restores files but content is missing | The database was not restored, or the backup predates recent content | Stop further changes and ask the host about a database-only restore or staging clone |
| The site loops back into updates | Auto-update remains enabled or a management system is reapplying the update | Disable the item in the dashboard or with WP-CLI, then check host-level update policies |
Which method should you use?
Use this decision order to avoid destructive trial and error:
- Known-good full backup available: restore it, preferably to staging first, and decide how to preserve content created afterward.
- Core changed and the working version is known: use the WP-CLI version command with
--force, then run the full verification checklist. - Plugin or theme installation failed on WordPress 6.3+: inspect the temporary upgrade backup before trying another update.
- Completed update caused a fatal error: use Recovery Mode, deactivate the named package, and repair or restore it.
- No dashboard access: use WP-CLI or temporarily rename the plugins directory; involve the host before editing core or database files manually.
- No known version and no backup: do not guess repeatedly on production. Preserve the current site, obtain the package history from the developer or host, and work on a clone.
The practical rule is simple: reverse the smallest component that explains the failure, keep both files and database recoverable, and disable only the automatic update that is causing the immediate repeat. A core downgrade, plugin rollback, or theme replacement is complete only after the site’s visitor-facing and administrative workflows pass testing.
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.
