 |
| Step-by-step Windows Automatic Repair and Blue Screen troubleshooting with Safe Mode, driver repair, System Restore, CHKDSK, SFC and DISM. |
Windows 10 and 11 Automatic Repair Loop and Blue Screen Fix Guide.
A Windows PC that repeatedly shows Automatic Repair, “Your PC did not start correctly," Startup Repair could not repair your PC, or a Blue Screen of Death (BSOD) could appear to have a serious hardware failure. In many cases, however, the problem is related to a corrupted system file, problematic driver, failed Windows update, damaged boot configuration, disk errors, or a software change.
The important point is that formatting Windows should not be the first solution. A number of recovery tools are already available inside the Windows Recovery Environment (WinRE), including Startup Repair, Startup Settings, System Restore, Uninstall Updates, and Command Prompt.
This guide explains the repair process in a practical order, starting with safer methods and moving toward advanced command-line repair only when necessary.
Start With a Simple Restart.
Restart Windows from the Automatic Repair Screen.
When the Automatic Repair screen appears, select Restart first.
A temporary boot failure can sometimes disappear after a normal restart. This is especially possible when the problem was caused by a one-time driver, update, or startup process failure.
If Windows starts normally after the restart, avoid immediately making additional system changes. First check whether the problem returns during another restart.
If Automatic Repair appears again, continue with advanced options.
Open Windows Recovery Environment.
Navigate to Advanced Troubleshooting Tools.
From the recovery screen, the usual path is:
Advanced options → Troubleshoot → Advanced options
Windows Recovery Environment is designed specifically for startup and recovery problems and contains several tools for repairing a system without immediately reinstalling Windows.
Before using advanced repair tools, disconnect unnecessary USB storage devices, memory card readers, external drives, and other peripherals. A faulty external device or incorrect boot priority can sometimes complicate startup troubleshooting.
If BitLocker or device encryption is enabled, some recovery operations may require the BitLocker recovery key.
Try Startup Repair First.
Use the built-in startup repair tool.
Select:
Troubleshoot → Advanced options → Startup Repair
Startup Repair is designed to diagnose and repair common problems that prevent Windows from starting. Microsoft lists issues such as damaged system files, boot configuration problems, incompatible drivers, and certain startup-related errors among the conditions it can attempt to repair.
Allow the process to finish completely and then restart the computer.
Startup Repair does not fix every type of Blue Screen or Automatic Repair loop. If it reports that it could not repair the PC, move to the next diagnostic method instead of repeatedly running the same repair.
Use Startup Settings to Test Safe Mode.
Start Windows With Minimal Drivers and Services.
Open:
Troubleshoot → Advanced options → Startup Settings → Restart
Windows will then display several startup options. Safe Mode starts Windows with a limited set of drivers and services, which makes it useful for determining whether a normal startup component is causing the crash.
On many Windows systems, the relevant choices include:
4 — Enable Safe Mode
5 — Enable Safe Mode with Networking
6 — Enable Safe Mode with Command Prompt
The exact display can vary between systems.
Start with Safe Mode with Networking when you need internet access for diagnostics. If networking itself causes another crash or prevents Windows from loading, return to Startup Settings and choose normal Safe Mode instead.
What Safe Mode Tells You.
If Windows runs reliably in Safe Mode but crashes during a normal startup, that is a useful diagnostic clue.
It can point toward a third-party driver, startup application, recently installed software component, or another service that is not loaded in the same way during Safe Mode. Microsoft also describes Safe Mode as a method for narrowing down problems caused by ordinary settings, drivers, and services.
Safe Mode does not automatically prove that a driver is defective, but it significantly narrows the troubleshooting path.
Identify the blue screen cause.
Check the crash dump with BlueScreenView.
If the system can start in Safe Mode with Networking, you can examine the crash information using a utility such as BlueScreenView from NirSoft.
BlueScreenView can read Windows minidump files and display information associated with previous Blue Screen crashes, including the bug check information and drivers referenced by the dump.
Download it only from the official NirSoft website:
https://www.nirsoft.net/utils/blue_screen_view.html
The utility is offered in 32-bit and 64-bit versions, including ZIP packages.
Extract the downloaded ZIP file and run the appropriate executable.
Interpret the Result Carefully.
If BlueScreenView identifies a driver file, write down its name before making changes.
Do not automatically assume that the displayed driver is definitely the root cause. A crash dump can identify the component involved in the crash, while the underlying reason may be a driver conflict, damaged system component, hardware instability, or another dependency.
This distinction is important because randomly uninstalling system drivers can create additional problems.
Repair a Suspected Graphics or Device Driver.
Uninstall the problematic driver from Device Manager.
If the crash appears to be associated with a graphics or other hardware driver, open Device Manager while in Safe Mode.
For a graphics problem:
Right-click Start → Device Manager → Display adapters
Expand the relevant category and identify the installed device.
Before uninstalling anything, record the exact device model so that you can obtain the correct driver later from the computer manufacturer or the hardware manufacturer's official website.
Right-click the device and select Uninstall device when appropriate.
Do not remove unknown system components simply because they appear in Device Manager.
Restart Into Normal Windows.
After removing a suspected problematic driver, restart the computer normally.
If Windows now starts without the previous Blue Screen, that strongly suggests the removed driver or its associated software deserves further investigation.
Once Windows is stable, install a compatible driver from the official manufacturer or computer manufacturer's support page instead of immediately installing random third-party driver packages.
For graphics hardware, prefer the current stable driver that officially supports your Windows version and GPU model.
Remove a Recently Installed Windows Update.
Use the " Uninstall Updates From WinRE" option.
A broken or incompatible update can sometimes trigger startup failures.
From the recovery environment, go to:
Troubleshoot → Advanced options → Uninstall Updates
Windows can provide options for removing recently installed update types. The exact choices shown can vary.
This is particularly useful when the automatic repair or blue screen problem began shortly after the Windows update completed.
Microsoft includes "Uninstall Updates" as one of the recovery tools available through the Windows Recovery Environment.
After removing a recent update, restart the computer and check whether normal Windows startup has returned.
Use System Restore When the Problem Started After a Recent Change.
Restore Windows to an Earlier Working State.
System Restore is especially useful when the PC was working correctly and the problem began after a driver installation, application installation, system change, or similar modification.
Open:
Troubleshoot → Advanced options → System Restore
Choose a restore point created before the problem began.
System Restore can roll back system files, registry settings, installed programs, drivers, and other system configuration changes while generally leaving personal files untouched.
Choose the Restore Point Carefully.
The best restore point is normally one created before the first appearance of the Blue Screen or automatic repair loop.
You can also use the option to scan for affected programs when available, helping you understand what software changes may be reversed.
If no suitable restore point exists, move to command-line diagnostics instead of repeatedly attempting unsuccessful restores.
Check the Windows drive for file-system errors.
First, identify the correct Windows drive letter.
When Command Prompt is opened from WinRE, the Windows installation is not guaranteed to be assigned the normal C: drive letter.
This is one of the most important details in offline repair.
At Command Prompt, you can inspect available drives with commands such as:
diskpart
list volume
exit
Or inspect a suspected drive with:
dir C:\
Look for the Windows folder, Users folder, and Program Files folder.
For example, if D:\Windows exists while C:\Windows does not, your offline Windows installation may be on D: in the recovery environment.
Never blindly assume that the Windows partition is C:.
Run CHKDSK.
After identifying the Windows volume, run:
chkdsk C: /f
Replace C: with the actual Windows volume letter if necessary.
The /f parameter tells CHKDSK to correct file-system errors when possible.
The scan can take considerable time, especially on large or heavily used drives. Do not interrupt the process unless the system is clearly unresponsive for an unusually long period.
If the drive shows serious hardware warnings, repeated read errors, or abnormal behaviour, repair should not be treated as a substitute for checking the physical condition of the SSD or hard drive.
Repair Damaged Windows System Files With SFC.
Run Offline System File Checker.
Once the correct Windows drive is known, use the offline SFC syntax.
For a Windows installation on C:, the command is:
sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows
Microsoft documents /offbootdir and /offwindir specifically for repairing an offline Windows installation from another recovery environment.
If Windows is actually installed on D:, use:
sfc /scannow /offbootdir=D:\ /offwindir=D:\Windows
Do not copy the drive letter from an example without checking your own system first.
Understand the SFC Result.
SFC may report that it found no integrity violations, repaired corrupted files, or found some files that could not be repaired.
A successful SFC result is useful, but it does not prove that every possible startup problem has been fixed.
If SFC cannot repair the component store or reports corruption that remains unresolved, continue with DISM.
Repair the Windows Component Store with DISM.
Run DISM From WinRE.
For an offline Windows installation on C:, use:
DISM /Image:C:\ /Cleanup-Image /RestoreHealth
For D:, replace the drive letter accordingly.
Microsoft's Windows recovery troubleshooting documentation also uses offline DISM together with offline SFC when repairing an unbootable Windows installation.
The operation can take time and may appear to pause at certain percentages. Avoid assuming that a temporary lack of visible progress means the command has failed.
Run SFC Again After DISM.
If DISM completes successfully, run the offline SFC scan again:
sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows
This second pass is useful because DISM can repair the component store that SFC relies on for system-file repair.
Microsoft specifically recommends repeating SFC after successful image repair when appropriate.
After the scans finish, close Command Prompt and restart Windows.
Repair a Damaged EFI Boot Partition Carefully.
Use This Method Only When the Boot Files Are the Problem.
The disk-partition and boot-file procedure is more advanced than the previous methods.
It should not be performed simply because Windows displays a Blue Screen.
A wrong partition selection or accidental formatting of the wrong volume can make data inaccessible or prevent Windows from booting.
This procedure is most relevant when the EFI System Partition or Windows boot files are damaged.
Identify the EFI System Partition.
At Command Prompt, start DiskPart:
diskpart
list disk
Select the disk containing Windows, for example:
select disk 0
list volume
Carefully inspect the listed volumes.
The EFI System Partition is normally a small FAT32 partition. Its size and volume number can vary by computer.
Do not select a partition based only on its size. Verify the partition type, file system, and overall disk layout before proceeding.
Temporarily Assign a Drive Letter.
For example:
select volume 3
assign letter=V
The volume number must match your own EFI partition.
Then leave DiskPart:
exit
Format Only the Correct EFI Partition.
This is a destructive operation for the selected partition.
If you have positively verified that V: is the correct EFI System Partition, a quick FAT32 format can be performed with:
format V: /FS:FAT32 /Q
Confirm the operation only after verifying the selected volume again.
Do not run this command against your Windows partition, personal-data partition, recovery partition, or external drive.
Rebuild the Windows Boot Files.
After formatting the correct EFI partition, use bcdboot:
bcdboot C:\Windows /s V: /f UEFI
Replace C:\Windows if the Windows installation is located on another drive letter.
The command rebuilds the boot files on the specified system partition.
Afterward, you can remove the temporary drive letter if needed by returning to DiskPart:
diskpart
select volume 3
remove letter=V
exit
The exact volume number must match the partition you selected earlier.
This procedure is not a universal Blue Screen repair. It is specifically for boot-environment problems and should be approached with extra care.
Check Hardware When Software Repair Does Not Work.
Inspect the SSD or Hard Drive.
Repeated Windows corruption can sometimes be caused by failing storage hardware.
Watch for symptoms such as:
Frequent file corruption.
Extremely slow disk access.
Repeated CHKDSK problems.
Random application crashes.
Missing or unreadable files.
SMART warnings.
The same Windows corruption returning after repair.
If important data is still accessible, back it up before performing destructive repair operations.
Check RAM and Other Components.
Unstable memory can also cause apparently unrelated Blue Screen errors.
If software repair repeatedly fails and crashes occur even after clean driver installation, consider testing:
System RAM.
SSD or hard-drive health.
GPU stability.
CPU temperatures.
Power supply stability.
Motherboard-related hardware issues.
A Blue Screen is not always a Windows software problem. Persistent failures across a clean or repaired installation can justify professional hardware diagnostics.
Avoid Formatting Windows Too Early.
Why a Clean Install Should Not Be the First Step.
Formatting or resetting the computer can remove applications, settings, or personal data depending on the selected recovery option.
When WinRE tools can repair the underlying issue, there is no reason to immediately erase a working Windows installation.
Microsoft's recovery guidance separates startup repair, System Restore, update removal, reset, and full reinstall as different recovery paths depending on the type of failure.
A sensible repair order is:
Restart → Startup Repair → Safe Mode → Driver diagnosis → Uninstall Updates → System Restore → CHKDSK → SFC → DISM → Boot-file repair when required → Hardware diagnostics → Reset or reinstall as a last resort.
This order reduces unnecessary data loss and helps identify the actual cause instead of simply replacing the operating system.
Use the Correct Windows Drive Letter During Command-Line Repair.
One of the most common mistakes in WinRE troubleshooting is using the wrong drive letter.
For example, normal Windows may use:
C:\Windows
But Command Prompt inside WinRE might expose the same Windows installation as:
D:\Windows
Before running SFC, DISM, CHKDSK, or BCDBOOT, verify the correct partition.
A simple check such as:
dir C:\
and:
dir D:\
can help identify which volume contains the Windows directory.
This small verification step can prevent an otherwise correct repair command from being aimed at the wrong installation.
Important Tips Before Running Advanced Repair Commands.
Keep the charger connected on a laptop during long repair operations.
Do not interrupt CHKDSK, DISM, or SFC simply because the progress appears slow.
Disconnect unnecessary external storage while diagnosing boot problems.
Back up accessible personal files before performing partition formatting or major recovery operations.
Do not delete or format a partition unless you have positively identified its purpose.
Download drivers from the hardware manufacturer's official website whenever possible.
Treat third-party driver-updater software cautiously. Manual installation from a trusted manufacturer is usually easier to verify.
If Windows repeatedly crashes after a new driver or update, investigate that recent change first.
If a Blue Screen contains a specific STOP CODE, record it. It can provide an additional clue during diagnosis.
Windows 10 and Windows 11 Recovery Difference to Keep in Mind.
The recovery tools discussed here apply to both Windows 10 and Windows 11, but Microsoft states that support for Windows 10 ended on October 14, 2025. After that date, Microsoft no longer provides normal free Windows Update software updates, technical assistance, or security fixes for Windows 10.
Therefore, if the affected computer is still running Windows 10, long-term reliability and security should also be considered when deciding whether to repair the existing installation or move to a supported Windows 11 configuration.
Official Resources for Further Verification.
Microsoft Windows Recovery Environment:
https://support.microsoft.com/windows/windows-recovery-environment
Microsoft Startup Repair:
https://support.microsoft.com/windows/startup-repair
Microsoft System Restore:
https://support.microsoft.com/windows/system-restore
Microsoft SFC Command Documentation:
https://learn.microsoft.com/windows-server/administration/windows-commands/sfc
NirSoft BlueScreenView:
https://www.nirsoft.net/utils/blue_screen_view.html
Note Point: Always identify the actual cause before formatting or deleting partitions, because many Automatic Repair and Blue Screen problems can be repaired without erasing personal data.
Disclaimer: The procedures involving drivers, partitions, formatting, DiskPart, and boot files can cause data loss or make Windows unbootable if used incorrectly, so verify every drive and partition before making changes.
