How to Fix a Windows PC That Keeps Restarting Automatically

Introduction

A Windows PC that keeps restarting automatically is one of the most disruptive problems a user or administrator can face. The machine may reboot during startup, in the middle of a document, or shortly after you log in, and each unexpected restart risks data loss, hardware stress, and lost productivity. The good news is that automatic restarts are usually caused by a small set of well-understood triggers: Windows Update behavior, a faulty driver, a failing power supply, overheating, a corrupted system file, or a misconfigured recovery setting.

This guide covers How to Fix a Windows PC That Keeps Restarting Automatically in practical, step-by-step detail. It is written for both beginners who need plain instructions and IT administrators who need a repeatable process they can apply across a fleet of machines. You will learn how to identify the cause, disable unwanted automatic restarts, repair system components safely, and confirm that the fix holds under load.

Automatic restarts fall into two broad categories. The first is software-driven: Windows Update installs a patch and reboots, a buggy graphics driver crashes the display subsystem, or a stop error (blue screen) triggers a restart before you can read the error code. The second is hardware-driven: an unstable power supply, bad RAM, dust-clogged fans, or an aging motherboard causes a hard reset. Effective troubleshooting separates these two categories early, because the repair path is completely different.

Before making changes, remember that keeping your operating system updated before installation prevents dependency conflicts. Many restart loops are actually triggered by a partially installed update, so verifying update state is part of the diagnosis, not an afterthought. Similarly, if you plan to reinstall or repair Windows from external media, always verify software compatibility with your hardware architecture (ARM64 vs x86) so you download the correct image and drivers.

By the end of this article you will have a clear, ordered procedure: prepare your data and tools, apply targeted fixes, run the main repair or reinstall procedure, verify stability, and configure post-install settings so the problem does not return. Administrators can follow the same steps and then roll the fix out through their management tools.

Prerequisites

Gather the following before you begin. Skipping these items is the most common reason a beginner gets stuck halfway through.

• A Windows PC that currently boots, or a second working computer if the affected PC will not stay on long enough to operate.
• Administrator rights on the affected machine. Standard users cannot change startup and recovery settings.
• A Windows installation USB or recovery drive that matches your architecture. Check whether the system is x86 (32-bit), x64, or ARM64 before downloading anything.
• A reliable external drive or cloud backup of important files. Repair steps can fail and you do not want to gamble with irreplaceable data.
• Knowledge of how to enter your system firmware (BIOS/UEFI) and, if needed, the Safe Mode menu.
• For administrators: access to your deployment or remote management console, plus hardware inventory records so you can map the fix to the correct model and architecture.
• The PC’s model number, serial number, and current Windows build, so you can look up vendor-specific firmware and chipset drivers.

Prior Linux experience is not required. Although some advanced diagnostic tools run from Linux, everything in this guide can be completed from Windows, Safe Mode, or the Windows Recovery Environment. If you choose to run a live Linux USB for hardware testing, treat it as optional.

Preparation

Preparation protects your data and makes the repair faster. Work through these items in order.

• Back up personal data. Copy documents, photos, browser profiles, and license keys to an external drive or cloud service. If the PC restarts constantly, use Safe Mode or pull the drive and attach it to another machine.
• Note the restart pattern. Does it restart before login, after login, only under load, or at a fixed interval? Write it down. This single observation narrows the cause dramatically.
• Capture error information. Disable automatic restart temporarily so blue-screen errors stay on screen. In Windows, go to System Properties, Advanced, Startup and Recovery, and clear the Automatically restart checkbox. You can also read the most recent entries in Event Viewer under Windows Logs, System.
• Check the update state. Run Windows Update and install any pending updates, then restart deliberately and see whether the problem changes. Again, keeping your operating system updated before installation prevents dependency conflicts when you later install drivers or repair tools.
• Verify architecture and compatibility. Open Settings, System, About and read the System type line. Always verify software compatibility with your hardware architecture (ARM64 vs x86) before downloading drivers, recovery images, or diagnostic utilities. Installing an x64 driver on an ARM64 device can itself cause crashes.
• Prepare the recovery environment. Create a Windows recovery USB or confirm that the built-in recovery partition works. Test that it boots before you need it.
• Document the hardware. For administrators, record RAM configuration, storage model, and firmware version. This makes it possible to correlate failures across identical machines and spot a bad batch.

Installation Steps

The following procedure walks you through the actual repair. It is written so that a beginner can follow it sequentially, while an administrator can adapt each step for scripted or remote execution. Do not skip steps: each one either fixes a known cause or eliminates one so later steps are easier to interpret.

Step 1: Review prerequisites and compatibility

Confirm that you have administrator access, a current backup, and the model and architecture details of the PC. Check that any recovery media or driver packages you downloaded match the machine’s architecture. Always verify software compatibility with your hardware architecture (ARM64 vs x86) at this stage, because a mismatched recovery image will fail to apply and can waste an hour of troubleshooting. Also confirm that Windows Update has run recently, since keeping your operating system updated before installation prevents dependency conflicts with repair tools and drivers.

Step 2: Prepare the environment

Boot the PC in a controlled state. Disconnect unnecessary peripherals such as printers, external docks, and USB hubs, because a failing device can trigger restarts. If the machine restarts before you can log in, boot into Safe Mode or the Windows Recovery Environment. In Safe Mode, only core drivers load, which immediately tells you whether a third-party driver is responsible. For administrators, snapshot the machine’s current state or note its configuration in your management console so you can compare before and after.

Step 3: Configure core settings

Change the settings that make diagnosis and repair possible.

• Disable automatic restart on system failure via Startup and Recovery, so blue screens remain visible long enough to photograph or transcribe the stop code.
• Set Windows Update active hours and defer feature updates temporarily, so an update does not reboot the machine while you are mid-repair.
• In the firmware, disable any aggressive auto-reboot or watchdog options and check that the boot order points to the correct drive.
• Turn off fast startup, which can mask shutdown problems and interfere with driver installation.
• Review power settings to ensure the machine is not set to sleep or hibernate in ways that mimic a restart.

These changes are reversible and do not affect your data.

Step 4: Run the main installation procedure

This is the core repair. Choose the path that matches what you observed in preparation, then work through the remaining items if the restart persists.

• System File Checker and DISM. Open an elevated Command Prompt. Run sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth. These tools replace corrupted system files that can cause reboots.
• Driver rollback or reinstall. In Device Manager, look for warning icons. Roll back recently updated graphics, chipset, network, and storage drivers. If no rollback is available, download the correct vendor driver for your architecture and install it cleanly.
• Memory and storage checks. Run Windows Memory Diagnostic and check the drive’s health with the manufacturer’s tool. Failing RAM or a degrading SSD produces exactly the symptom you are fixing.
• Thermal and power inspection. Clean dust from fans and vents, confirm the CPU cooler is seated, and if possible test with a known-good power supply. Overheating and unstable power are hardware causes that no software fix will cure.
• Windows repair install. If software repairs fail, run an in-place upgrade using installation media that matches your architecture. This reinstalls Windows while keeping files and most applications, and it resolves deeply corrupted system components.
• Clean install as a last resort. If the machine still restarts after a repair install and hardware checks pass, back up and perform a clean installation. Always verify software compatibility with your hardware architecture (ARM64 vs x86) before you begin, and keep your operating system updated before installation of drivers and applications to prevent dependency conflicts.

After each item, restart the PC deliberately and observe. Recording which step changed the behavior is as valuable as the fix itself, especially when you are managing many machines.

Step 5: Verify the installation

Do not declare success after a single quiet reboot. Verification should stress the system enough to expose an intermittent fault.

• Run the PC for at least 30 to 60 minutes of normal work with several applications open.
• Check Event Viewer for new critical errors, unexpected shutdown events, or bugcheck entries.
• Confirm that all drivers show healthy status in Device Manager with no warning icons.
• Run Windows Update once more to ensure the system is current and no pending update is waiting to reboot the machine.
• For administrators, monitor the machine through your management console for 24 to 48 hours before returning it to production.

Step 6: Configure post-install options

With stability confirmed, restore the settings you changed and lock in good habits.

• Re-enable automatic restart only if your organization’s policy requires it; otherwise leave it disabled so future errors stay visible.
• Set Windows Update active hours to match real working hours so updates do not interrupt users.

You now have a complete workflow for How to Fix a Windows PC That Keeps Restarting Automatically. Keep your system updated, monitor resource usage, and revisit this guide when software versions change.

Next steps: harden your server firewall, set up automated backups, and explore related tutorials linked above.