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 reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWhen /wp-admin stops working, do not start by deleting files or repeatedly retrying the login. Record the exact symptom first—login loop, blank screen, 404, 500, critical-error notice, broken Save/Publish controls, or a maintenance message—and note whether the public site still loads. That combination points to the safest next test.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
Start with WordPress Recovery Mode if an email link is available. If it is not, temporarily disable all plugins, test a default theme, check .htaccess, and then enable temporary logging. These changes are reversible when performed carefully. Database edits, configuration changes, and server-level work should be handled by someone comfortable with hosting tools or by your host’s support team.
As an Amazon Associate I earn from qualifying purchases.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
First, identify exactly what is failing
“The admin panel is not working” can describe several different failures. Before changing anything, write down the URL you opened, the message or HTTP status you saw, and whether the public site is normal. Take a screenshot if the message may disappear.
| Observed symptom | What to record | Why it matters |
|---|---|---|
| Login loop | Whether the password is accepted, whether the browser returns to the login page, and whether the front end loads | Shows that authentication or a component loaded during login may be failing, rather than the entire server being unavailable |
| Blank or white screen | Whether the blank page affects only /wp-admin or the public site too |
Often indicates a fatal PHP error whose details are hidden from visitors |
| HTTP 404 | The exact URL and whether ordinary site pages also return 404 | Helps distinguish an admin path problem from rewrite or access-rule trouble |
| HTTP 500 | The time of the error and whether it began after an update or configuration change | Server and PHP logs can match the request to the underlying failure |
| “There has been a critical error on this website” | Any recovery email and the component named in it | WordPress may have identified a fatal plugin or theme error and offered Recovery Mode |
| Save or Publish does not work | Whether the editor loads, whether the button spins, and whether the public site remains available | A plugin, theme, or custom code conflict can affect dashboard actions without taking down every page |
| Maintenance message | Whether it remains after a normal page refresh and whether the front end is also affected | Confirms that the site is presenting a maintenance state rather than a normal login failure |
Do not make several changes at once. If you rename a directory and edit configuration in the same attempt, you lose the ability to tell which test changed the result.
Use WordPress Recovery Mode before touching files
Recovery Mode is the least invasive path when WordPress offers it. WordPress introduced the feature in version 5.2. According to WordPress documentation, it can help regain access after a fatal error without FTP access or direct code editing.
WordPress automatically activates Recovery Mode when it detects a fatal PHP error during a regular page load. It does not trigger for CRON or other background tasks. When activation succeeds, WordPress sends the site administrator a special login link. The recovery session pauses the suspected plugin or theme and displays notices identifying the component that failed.
Recovery Mode procedure
- Check the administrator mailbox associated with the site for the Recovery Mode message. Use the link from that message rather than repeatedly loading the normal login page.
- Sign in through the special link. The dashboard should show a notice naming the paused plugin or theme, if WordPress could identify one.
- Review the notice and deactivate, repair, or update the named component as appropriate. Do not immediately reactivate it just to see whether the error returns.
- Exit Recovery Mode, then open the public site and the normal
/wp-adminlogin in a new session. Confirm that both behave normally. - If the same fatal error returns after the component is restored, leave it inactive and continue with the plugin, theme, or logging tests below.
Recovery Mode is session-scoped: a component paused for your recovery session is not proof that the component has been permanently fixed. The normal site still needs a clean test after you leave the session.
If you cannot log in, deactivate every plugin
A plugin can break the login page, dashboard, editor, or front end. WordPress documents two ways to deactivate all plugins without opening the dashboard. The filesystem method is usually easier to reverse; the database method is useful when you have no usable file access.
Method 1: rename the plugins directory
- Use FTP, SFTP, or your hosting file manager to open the WordPress installation.
- Locate
wp-content/plugins. - Rename the directory to a temporary name such as
plugins.hold. Renaming does not erase plugin files; it prevents WordPress from finding the active plugins in their expected location. - Try the normal login and load the dashboard. If access returns, the failure is likely in a plugin or in an interaction between plugins.
- Rename
plugins.holdback toplugins. Do this before attempting to manage individual plugins. - Reactivate plugins one at a time, testing the login, dashboard, and any previously broken action after each activation. The plugin that brings the symptom back is the leading suspect.
This test requires filesystem access but is reversible. The public site may change while all plugins are unavailable, so check a representative public page as well as the dashboard.
Method 2: set the active plugin list to empty in phpMyAdmin
- Open phpMyAdmin through your hosting account and select the database used by the WordPress site. If you are unsure which database is correct, ask the host rather than editing a random database.
- Open the site’s options table. Its prefix may not be the default, so identify the table by the prefix shown in
wp-config.php. - Find the
active_pluginsvalue and set it toa:0:{}, the serialized value representing no active plugins. - Save the change, then try the login again.
- If access is restored, reactivate plugins individually from the dashboard and test after each change.
Serialized database values must be entered exactly. A typo can create a separate database problem, which is why WordPress’s documentation treats this route as a task for someone familiar with phpMyAdmin or for the hosting provider.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Test the active theme after plugins are ruled out
If all plugins are disabled and /wp-admin is still unavailable, test the active theme. Theme files can contain PHP or custom code that runs on both the front end and dashboard.
- Through FTP, SFTP, or the hosting file manager, open
wp-content/themes. - Identify the directory for the active theme and rename that directory temporarily.
- Retry the login and load a public page. WordPress should fall back to an available default theme.
- If the dashboard works with the default theme, the original theme or its custom code is implicated.
- Restore the original directory name after the test. Keep the default theme active while you inspect or repair the original theme, then test again.
A recovery after the theme rename isolates the theme path; it does not identify which template or customization is defective. Keep a copy of any custom changes before replacing or editing theme files.
Rank #3
Check .htaccess for 404 and 500 responses
On installations that use Apache rewrite rules, a damaged or incompatible .htaccess file can interfere with routing. It is especially relevant when the symptom is a 404 or 500 response and the site changed after a migration, update, or configuration edit.
- Make a backup copy of
.htaccessbefore changing it. The file is often hidden, so enable “show hidden files” in the FTP client or hosting file manager. - Rename the file temporarily, for example by appending a temporary suffix. Do not delete the only copy.
- Try the admin URL and a public page. If access returns, the rewrite rules in the original file are a strong suspect.
- Once the dashboard works, open Settings > Permalinks and save the settings once. This lets WordPress regenerate its expected rewrite rules.
- Retest the admin and public URLs. Keep the backed-up original file until you have confirmed that routing is stable.
Renaming .htaccess is a diagnostic change, not a permanent instruction to run without rewrite rules. If it makes no difference, restore the original name before moving to the next test.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Turn on temporary logging when the cause is still unclear
When a blank page, critical error, or HTTP 500 continues, logs provide evidence instead of guesswork. WordPress support guidance recommends both the WordPress debug log and the server or PHP error log.
Enable the WordPress debug log
- Make a backup copy of
wp-config.phpbefore editing it. - Open the file and add these definitions before the line that says WordPress’s editing should stop:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );- Save the file and reproduce the failure once. Use the same URL and action that originally failed so the log entry is meaningful.
- Inspect
wp-content/debug.logfor the timestamp of that request. Look for a plugin, theme, file path, or PHP message named near the failure. - Check the hosting control panel’s server and PHP error log for the same time. Server-level messages can reveal resource, permission, or PHP configuration problems that the WordPress log cannot.
- After diagnosis, set debugging back to its previous state. Do not leave raw errors displayed on a public site.
Debug logging is temporary evidence collection. It does not repair the failing component, and the log may contain paths or other details that should not be exposed to visitors.
Choose the next move by risk and access
The following comparison helps you choose a path without treating every failure as a file-editing problem.
| Path | Dashboard access required? | Risk to public site | Reversibility | Technical skill | Diagnostic value |
|---|---|---|---|---|---|
| Recovery Mode | No normal dashboard access; uses the emailed recovery link | Low; the suspected component is paused for the recovery session | High; exit the session and restore the component only after testing | Low | High when a fatal plugin or theme is identified |
Rename wp-content/plugins |
No | Moderate; all plugin-dependent features may change temporarily | High if the directory is renamed back | Moderate filesystem access | High for plugin conflicts |
Set active_plugins to a:0:{} |
No | Moderate; all plugins are deactivated at the database level | Depends on restoring the prior value | Higher; requires phpMyAdmin and serialized-value care | High for plugin conflicts when file access is unavailable |
| Rename the active theme directory | No | Moderate; WordPress falls back to a default theme | High if the directory name is restored | Moderate filesystem access | High for theme or custom-code failures |
Rename .htaccess |
No | Moderate; rewrite-based URLs may change temporarily | High with a backup | Moderate filesystem access | High for rewrite and access-rule symptoms |
| Enable debug and server logging | No, but file or host access is needed | Low when public display remains disabled | High; remove or disable the temporary settings | Moderate to high | Strongest evidence when application-level tests are inconclusive |
| Host or WordPress professional | No | Depends on the intervention agreed with the provider | Depends on backups and change control | Lowest for the site owner | Highest when server, database, permissions, or damaged core files are involved |
Use the public site as a discriminator
If visitors can still browse the public site while the dashboard fails, prioritize Recovery Mode, plugin isolation, theme isolation, and logging. A dashboard-only failure can still be serious, but it gives you a working front end from which to confirm each test.
If both the public site and /wp-admin fail, record whether the response is a 404, 500, blank page, critical-error notice, or maintenance message. A 404 or 500 makes the .htaccess test and server/PHP logs particularly useful. A critical-error notice makes Recovery Mode the first choice when the email arrives.
If only Save or Publish actions fail while pages and login work, do not immediately alter the database. Disable plugins through the dashboard one at a time if possible; if the dashboard becomes unusable during that process, use the filesystem or phpMyAdmin method instead. A plugin or theme that affects the editor can be isolated by the same reversible tests used for a complete dashboard outage.
When to stop troubleshooting yourself
Escalate to the host when the next action requires phpMyAdmin, filesystem permissions, PHP configuration, server logs, resource-limit changes, or access you do not have. Ask for the error timestamp, the exact URL, the HTTP status, and the steps already tested. That information lets support correlate your request with the server and PHP logs.
Host or professional help is also appropriate when core files may be damaged or an upgrade failed. Avoid replacing core files or changing database values at random: without a backup and a known-good target, those actions can turn a recoverable component conflict into a broader outage.
Recommended Free Tools
A controlled recovery checklist
- Write down the exact symptom, URL, time, and whether the public site works.
- Look for the WordPress Recovery Mode email and use its special login link.
- If Recovery Mode is unavailable, rename
wp-content/pluginsand test. - Restore the directory name, then reactivate plugins individually to identify a conflict.
- If plugins are not responsible, rename the active theme directory and test the default theme fallback.
- For 404 or 500 symptoms, back up and temporarily rename
.htaccess; restore permalinks from Settings > Permalinks after access returns. - Enable
WP_DEBUGandWP_DEBUG_LOGtemporarily, reproduce the failure, and inspect both WordPress and server/PHP logs. - Turn debugging off after diagnosis and restore every temporary filename change that is no longer needed.
- Contact the host when the evidence points to permissions, PHP settings, resource limits, damaged files, a failed upgrade, or unavailable database and filesystem access.
What a successful fix looks like
Do not stop at the first successful login. After each change, verify the normal login, one dashboard screen, the previously broken Save or Publish action if applicable, and a representative public page. Then undo temporary diagnostic changes, confirm that the public site still renders correctly, and document which component or rule caused the failure. That record makes the next incident faster to diagnose without repeating risky changes.
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.
