Asrock Preparing Automatic Repair | Stop The Boot Loop

What The Asrock “Preparing Automatic Repair” Screen Means

When your ASRock logo appears and the text “Preparing Automatic Repair” sits under the spinner, Windows is trying to fix a startup problem on its own. This screen is part of Windows, not a fault built into the ASRock board, and it appears when the system cannot reach the normal sign in screen safely.

In practice, the loop often starts after a bad shutdown, a power cut, a stalled update, storage errors, or a change in firmware settings. The board still passes the first checks, so you see the vendor splash screen, but Windows hits damaged files, a corrupted boot record, or a disk that does not respond in time. The result looks like an asrock preparing automatic repair freeze where nothing moves past that text.

Many users only see this message from time to time, then Windows continues. The real problem begins when the screen repeats on every startup, tosses you back to a black screen, or drops you into the blue recovery menu. At that point the built in fixer is stuck and you need to take control of the repair process.

Asrock Preparing Automatic Repair Fixes And First Checks

Before you open firmware menus or reinstall Windows, run through a short set of physical and basic software checks. These steps clear temporary glitches and remove simple causes that often keep the loop alive.

• Shut Down Fully — Press and hold the power button for ten seconds until the machine turns off, then unplug the power cable or switch the power supply off for one minute before starting again.
• Remove Extras — Disconnect external hard drives, extra USB sticks, game controllers, card readers, and printers so only keyboard, mouse, and monitor stay attached.
• Try A Second Outlet — Plug the system straight into a wall outlet or a different surge strip to rule out a weak power bar that resets the machine during startup.
• Let Repair Run Once — Power on, let “Preparing Automatic Repair” run through a full cycle, and see whether Windows reaches the desktop. Do not keep forcing hard power offs during this first run.
• Note New Noises — Listen for clicking, grinding, or repeated spin ups from the drive area, which can hint at a failing disk that pushes the repair loop to appear.

If the machine boots all the way into Windows after a clean power cycle and one repair attempt, keep an eye on it and back up important files. If it falls straight back to the same message or a black screen, move on to firmware checks on your ASRock board.

Enter Asrock Bios Safely And Reset Risky Settings

ASRock boards give you access to UEFI firmware with the Del or F2 button during the logo screen. Tap that button repeatedly as soon as the system turns on so you land in the main firmware page instead of the repair loop. From there you can undo changes that often trigger the message, especially on newer Windows 10 and Windows 11 builds.

• Load Default Settings — Find the option named Load UEFI Defaults, accept it, then save and exit. This clears risky overclocks and unusual boot tweaks.
• Check Boot Order — Make sure the system drive that holds Windows sits in the first boot slot and that old USB entries are moved below it or removed.
• Disable Fast Boot — Turn off firmware Fast Boot so the board runs full hardware checks on every start, which can prevent lockups during recovery.
• Rollback Recent Changes — If you recently changed CSM, TPM, or Secure Boot to meet Windows 11 checks, put those settings back to their previous state for now and test whether the loop stops.
• Update Firmware When Stable — Once the system boots again, visit the ASRock site for your exact model and apply the latest stable UEFI version using Instant Flash or the vendor’s update tool.

If returning firmware to defaults breaks the loop, you can later re enable features like TPM for Windows 11 once the system is stable. If even with safe defaults set you still see the same repair message every time, the fault usually sits with Windows itself or the storage that holds it.

Use Windows Recovery Menu To Repair Startup Files

When the automatic repair fails, Windows normally drops you into a blue recovery screen with a Troubleshoot button. That area holds several tools that can often fix the boot loop without wiping data, as long as the disk still responds.

• Open Advanced Options — On the recovery screen choose Troubleshoot, then Advanced options to see Startup Repair, System Restore, command prompt, and related tools.
• Run Startup Repair — Select Startup Repair and pick your Windows account. The tool scans for damaged boot entries and replaces them where possible.
• Use System Restore — If restore points are available, roll the system back to a date before the loop started so driver or update changes are reversed.
• Remove Broken Updates — Pick Uninstall Updates to roll back the latest feature update or quality update in case a patch left the system unable to boot.
• Try Safe Mode — Under Startup Settings choose Restart, then pick a safe mode option. If Windows loads in safe mode, uninstall recently added drivers or software there.

These tools make their changes inside the existing installation, so user files stay on the drive. If none of them change the behaviour and the automatic repair loop still appears, it is time to bring in a bootable installer so you can run deeper checks from outside the broken system.

Create A Windows Usb And Run Deeper Command Repairs

A fresh Windows 10 or Windows 11 installer on a USB stick gives you another path into repair tools when the local recovery copy no longer loads. You can create the stick on another PC with the official media creation tool, then use the ASRock boot menu to start from that drive.

• Build The Installer — On a working Windows machine download the current media creation tool, plug in an empty eight gigabyte USB stick, and let the tool write setup files for the correct Windows version.
• Boot From Usb — Plug the stick into the ASRock system, power on, and press F11 or the shortcut listed for Boot Menu on screen, then choose the USB drive entry.
• Open Repair Tools — When Windows setup appears, pick your language, then use the small “Repair your computer” link instead of the Install button to reach the familiar Advanced options menu.

From that menu, command prompt lets you run file system and boot record repairs even when the main installation will not start. Work through the options in order, watching for red error messages that hint at hardware faults.

• Check The Disk — Run chkdsk C: /f /r to scan the system volume for file system errors and bad sectors, then let it finish and restart.
• Repair System Files — Run sfc /scannow to scan protected Windows files and replace missing or damaged copies from the installer image.
• Rebuild Boot Data — Use bootrec /fixmbr, bootrec /fixboot, and bootrec /rebuildbcd in turn to refresh the boot loader configuration.

If these commands finish without heavy error output but the machine still drops back to automatic repair, backing up data and planning for a repair install or clean install is usually the next steady move.

Use A Repair Install Or Reset To Keep Your Files

When corruption runs deep but the drive still behaves, an in place repair install or a reset that keeps user files can refresh Windows while leaving personal folders in place. Both options still carry some risk for apps and settings, so copy documents to another drive or cloud storage first if you can reach them.

• Start Reset This Pc — From the recovery menu pick Troubleshoot then Reset this PC, choose Keep my files, and follow the prompts so Windows reinstalls its core files on top of the existing copy.
• Run Setup From Usb — If reset fails, boot from the installer USB again, pick Install this time, and choose the option that keeps personal files while refreshing system files.
• Reinstall Drivers Cleanly — After the system boots, reinstall graphics, chipset, and storage drivers from the ASRock and device vendor pages instead of old driver packs.

Once the system runs cleanly, turn to regular backup habits and cautious update installs so another asrock preparing automatic repair loop is less likely to trap you for long.

Spot Hardware Failures That Can Trigger The Loop

Not every repair loop comes from software. A failing drive, weak power delivery, or faulty memory can interrupt startup in ways that leave Windows stuck in self repair on an ASRock board. A short check of hardware health saves time chasing software problems on a dying device.

• Test Storage Health — In firmware or with a tool on a bootable USB, read the SMART values for the system drive and look for warnings, reallocated sectors, or read errors.
• Swap Cables And Ports — Move a SATA data cable to a new port and replace worn power leads to rule out a loose connection that cuts drive power during boot.
• Run Memory Tests — Use Windows Memory Diagnostic or a USB tool such as MemTest86 to check for repeatable memory errors.
• Try Minimal Hardware — Boot with only CPU, one stick of RAM, system drive, and integrated graphics where available to see whether add in cards or extras cause the loop.

If storage tests show heavy error counts or the system hangs whenever that drive is connected, replacement is the safe route. Install a fresh copy of Windows on the new disk, then restore data from backups or from a one time copy of the old drive taken with a separate adapter.

Quick Reference Table For Common Loop Causes

Visible Symptom	Likely Source	Fix Section
Stuck on logo with “Preparing Automatic Repair” text	Corrupted boot files or broken update	Windows Recovery Menu, Usb Command Repairs
Instant return to blue recovery menu	Repeated failed repair attempts	Windows Recovery Menu, Repair Install Or Reset
Black screen, disk clicking or grinding	Failing hard drive or SSD	Hardware Failure Checks, New Drive Install
Loop began after firmware setting changes	CSM, TPM, or boot order change	Enter Asrock Bios And Reset Settings

Work through these sections in order, starting with basic power and firmware checks, then software repairs, and only then hardware swaps or fresh installs so each step can point to the real fault without losing recoverable data that still matters to you.