How to Disable Automatic Restart After a Blue Screen on Windows 11
There is a special kind of frustration that comes with a Windows blue screen that flashes past in half a second. You see a sad face, a percentage counter, and then your laptop is already rebooting. The one piece of information you actually need — the stop code — is gone before you can read it.
The good news is that this instant reboot is just a setting, and you can turn it off in under a minute. Once disabled, your laptop will hold the blue screen until you restart it yourself, giving you time to photograph the error code and work out what is actually wrong. If the blue screen keeps coming back after you read the code, follow our broader guide on how to fix the blue screen of death on Windows 11 .
Why this happens
- AutoReboot is enabled by default. Windows sets the
AutoRebootvalue to 1 after every clean install, so a crash triggers an instant reboot with no confirmation. - Windows treats a crash as unrecoverable. A bugcheck (the technical name for a blue screen) means the kernel hit something it could not safely continue from, so the default response is to collect a dump and restart.
- The dump is written silently. Windows saves a minidump to
C:\Windows\Minidumpand an event to Event Viewer, assuming you will look there later instead of reading the screen. - Fast Startup hides the crash. With Fast Startup enabled, a “shutdown” is really a hibernate, so crashes can loop in ways that make the reboot feel even more abrupt.
- OEM images keep the default. Dell, HP, and Lenovo factory images all ship with automatic restart turned on, so this behavior survives a factory reset.
- Group Policy can enforce it. On work or school laptops, an IT policy may re-enable automatic restart even after you turn it off.
How to fix it
Work through these in order. The first method is the easiest; the later ones are for laptops that crash too fast to change settings normally.
Fix 1: Turn it off in Startup and Recovery
This is the official graphical way, and it takes about thirty seconds.
- Press Win + R, type
sysdm.cpl, and press Enter to open System Properties. - Switch to the Advanced tab and click Settings under Startup and Recovery.
- Uncheck Automatically restart under System failure.
- Confirm the Write debugging information dropdown is set to Automatic memory dump so crash data is still collected.
- Click OK twice to save. The next blue screen will stay on screen until you hold the power button.
Fix 2: Disable it with a registry edit
If you prefer precision or want to script this across machines, the registry holds the same setting.
- Press Win + R, type
regedit, and press Enter. Approve the UAC prompt. - Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl.
- Double-click AutoReboot and set its value to
0. If the value does not exist, right-click in the pane, choose New > DWORD (32-bit) Value, name itAutoReboot, and set it to0. - Close Registry Editor and restart once so the change takes effect.
Fix 3: Disable it from an elevated Command Prompt
A single command does the same job, which is handy if you are helping someone over the phone.
- Press Win + S, type
cmd, right-click Command Prompt, and choose Run as administrator. - Run this command to disable automatic restart:
wmic RecoverOS set AutoReboot = False - On newer builds where WMIC is deprecated, use PowerShell instead. Open Windows PowerShell as administrator and run:
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\CrashControl" -Name AutoReboot -Value 0 - Restart your laptop to confirm the change sticks.
Fix 4: Change it from the Recovery Environment
When crashes happen so early that Windows never reaches the desktop, change the setting from WinRE.
- Hold the power button to force a shutdown while Windows is loading. Repeat twice.
- On the third boot, Windows enters the Recovery screen. Click Troubleshoot, then Advanced options, then Command Prompt.
- Type
regeditand press Enter to open Registry Editor. - Select HKEY_LOCAL_MACHINE, then go to File > Load Hive.
- Navigate to your Windows drive (often
D:in WinRE) at\Windows\System32\config\SYSTEM, give the hive a temporary name likeOfflineSys, and setOfflineSys\ControlSet001\Control\CrashControl\AutoRebootto0. - Select the loaded hive and choose File > Unload Hive, then close everything and choose Continue to boot normally.
Fix 5: Boot into Safe Mode to make the change
Safe Mode loads a minimal driver set, which often avoids the crashing driver long enough to change settings.
- From the Recovery screen, go to Troubleshoot > Advanced options > Startup Settings and click Restart.
- Press 4 for Safe Mode (or 5 for Safe Mode with Networking).
- Once in Safe Mode, use Fix 1 (the
sysdm.cplmethod) to uncheck Automatically restart. - Restart normally. If you need a refresher on getting in and out of Safe Mode, see our guide on how to boot Windows 11 in Safe Mode .
Fix 6: Read the stop code from the memory dump
Disabling the reboot is only half the battle — now you need to identify the culprit.
- Download BlueScreenView from NirSoft on another device if yours is unstable, and copy it over on a USB stick.
- Run it — it automatically reads
C:\Windows\Minidumpand lists every crash with its stop code and the driver highlighted in red. - Note the driver name (often something like
nvlddmkm.sysorrtwlanu.sys). That is your prime suspect for updating or rolling back. - You can also open Event Viewer, go to Windows Logs > System, and filter for Event ID 1001 (BugCheck) to see the same data without extra tools.
Fix 7: Update or roll back the suspect driver
Most recurring blue screens trace back to one bad driver, and now you know which one.
- Open Device Manager (Win + X, then Device Manager).
- Find the device matching the driver from Fix 6, right-click it, and choose Update driver > Search automatically for drivers.
- If the crash started right after a driver update, choose Properties > Driver > Roll Back Driver instead.
- For graphics and Wi-Fi drivers, grab the latest version directly from the manufacturer. Intel users can run the automatic check at Intel Driver & Support Assistant , and NVIDIA owners should use the official driver download page .
Fix 8: Repair system files if crashes persist
If no single driver stands out, corrupted system files may be triggering the bugchecks.
- Open an elevated Command Prompt and run:
sfc /scannow - When it finishes, run the DISM repair commands one at a time:
DISM /Online /Cleanup-Image /RestoreHealth - Restart and watch for further crashes. If they continue, a clean look at recent Windows updates is worthwhile — check Settings > Windows Update > Update history and uninstall anything installed just before the crashes began. Microsoft documents blue screen troubleshooting steps further at Windows support .
Closing
Disabling automatic restart will not fix the crash itself, but it turns a maddening half-second flash into a readable error screen — and a readable error is a solvable one. Change the setting using whichever method suits your situation, grab the stop code, chase down the faulty driver, and your laptop should be back to boring, reliable normality.
