How to Exit the Preparing Automatic Repair Black Screen on Windows 11
🔍 WiseChecker

How to Exit the Preparing Automatic Repair Black Screen on Windows 11

Quick fix: Force-shutdown by holding the power button for 10 seconds, wait, power on, immediately mash F8 as Windows starts — interrupts the Automatic Repair entry and gives you Recovery Environment options.

Windows boots, displays “Preparing Automatic Repair,” goes to a black screen, and stays there for hours. The spinning dots disappear. The disk light is off. No keyboard input responds. Windows is technically in a transitional state — the bootloader handed off to Automatic Repair, but Automatic Repair is hung mid-diagnostic. Waiting won’t help; you need to break out and use the Recovery Environment directly.

Symptom: Windows 11 boot reaches “Preparing Automatic Repair” black screen and never advances.
Affects: Windows 11 (and Windows 10) on a PC unable to complete normal boot.
Fix time: ~15 minutes.

ADVERTISEMENT

What causes this

The bootloader detects a previous failed boot and triggers Automatic Repair. Automatic Repair’s first task is to scan the disk and read system files to determine what to repair — if any read takes too long (storage issue, driver waiting for hardware response that never comes), the scan hangs without timing out. The screen goes black because the GPU enters a low-power state during the long wait, and Automatic Repair never recovers because its scan never returns.

The fix is to interrupt the hang, force the system into the Recovery Environment menu (instead of letting Automatic Repair retry), and use manual repair tools from there.

Method 1: Force three failed boots to trigger Recovery Environment

The most reliable interrupt path. Triggers Windows’ built-in “boot failed three times” recovery flow.

  1. Force shutdown: hold the power button for 10 seconds until the PC powers off.
  2. Wait 5 seconds.
  3. Power on. Wait for the “Preparing Automatic Repair” or Windows logo to appear.
  4. Force shutdown again with the power button.
  5. Repeat: power on, wait for logo, force shutdown. Total of three failed boots.
  6. On the fourth power-on, Windows enters Recovery Environment automatically — you see the blue Choose an option screen instead of Automatic Repair.
  7. Click Troubleshoot → Advanced options.
  8. From here, choose one of: Startup Repair, Startup Settings (for Safe Mode), Command Prompt, System Restore, or Uninstall Updates.

Recovery Environment opens a clear set of options instead of the hung Automatic Repair.

ADVERTISEMENT

Method 2: Boot from Windows installation USB

When Method 1 doesn’t reach Recovery Environment, or when the disk is so degraded that all options fail.

  1. On another working PC, create a Windows 11 installation USB using the Media Creation Tool from microsoft.com/software-download/windows11.
  2. Plug the USB into the affected PC. Force shutdown.
  3. Power on. Mash the boot menu key (F12 / F11 / Esc, depending on manufacturer) to open the boot device selector.
  4. Choose your USB drive.
  5. Wait for “Press any key to boot from USB” — press a key.
  6. Windows Setup loads. On the language screen, click Next.
  7. Click Repair your computer in the bottom-left corner (not Install).
  8. You now have access to Recovery Environment with all its tools.
  9. From here: Command Prompt to run repair commands, System Restore to roll back, or Startup Repair to retry the broken auto-repair from a different angle.

The installation USB’s Recovery Environment is identical to the built-in one, but accessible from a working external boot source.

Method 3: Disable Automatic Repair entirely to attempt normal boot

Use this from Command Prompt in Recovery Environment if you suspect Automatic Repair itself is the problem — and normal boot would succeed if Windows just stopped trying to repair.

  1. Reach Recovery Environment (Method 1 or 2).
  2. Open Troubleshoot → Advanced options → Command Prompt.
  3. If asked for a password, enter your account password.
  4. Disable Automatic Repair on next boot:
    bcdedit /set {default} recoveryenabled No
  5. Optionally also disable the boot status policy check:
    bcdedit /set {default} bootstatuspolicy ignoreallfailures
  6. Close Command Prompt. Choose Continue: Exit and continue to Windows 11.
  7. The PC attempts normal boot without invoking Automatic Repair.
  8. Once you’re back in Windows, diagnose the underlying issue and re-enable Automatic Repair: bcdedit /set {default} recoveryenabled Yes.

This bypasses the hung Automatic Repair logic. Useful as a triage step when you suspect Windows itself is mostly fine.

How to verify the fix worked

  • Windows boots past the “Preparing Automatic Repair” screen.
  • You either reach the desktop normally (if Method 3 worked), or you’re in Recovery Environment with full menu access (Methods 1 and 2).
  • From Recovery Environment, run chkdsk D: /f (D: is your Windows drive) to confirm filesystem health.

If none of these work

If you can’t escape the “Preparing Automatic Repair” black screen even with USB boot and three-failure trigger, hardware is the most likely cause. Failing storage: the drive may be so degraded that any read attempt hangs. Test by booting a Linux live USB and trying to read files from the Windows drive — if Linux also hangs, the drive is failing and needs replacement before any Windows recovery is possible. Bad RAM: run Memtest86 from a USB; let it complete at least one full pass. Any errors mean RAM needs replacement. Disconnected cable: for desktops, open the case and reseat SATA/NVMe and power cables. For laptops, this is harder but a recent service event or drop could have loosened the M.2 SSD. UEFI corruption: clear CMOS (remove the small battery for 30 seconds on a desktop; check laptop manual). For chronic Automatic Repair stuck scenarios on aging hardware, the practical path forward is to image the drive (if possible) from a Linux live USB, then replace the drive and restore from the image.

Bottom line: The “Preparing Automatic Repair” black screen is escapable — force three failed boots to reach Recovery Environment, then use its tools directly. Don’t wait it out; it doesn’t recover on its own.

ADVERTISEMENT