AORUS Preparing Automatic Repair

The AORUS “Preparing Automatic Repair” screen means Windows can’t boot; try Startup Repair, Safe Mode, then disk and BIOS checks.

Seeing “Preparing Automatic Repair” on an AORUS laptop or desktop is frustrating, but it’s not random. Windows has detected repeated start failures and has switched to its built-in recovery screen. The goal is simple. It gets you back to a normal start without data loss.

Follow steps in order; stop when it boots.

What “Preparing Automatic Repair” Means On AORUS

On many systems, Windows triggers the recovery screen after a few failed starts. It can be caused by a bad update, a driver crash, file-system errors, or a storage problem. On AORUS hardware, the same Windows rules apply, but BIOS boot settings and fast startup choices can make the loop feel worse.

What You See	Common Trigger	Best First Move
Spinning dots, then “Preparing Automatic Repair”	Windows start files can’t load	Run Startup Repair
Repair screen returns after restart	Disk errors or a broken update	Try Safe Mode, then uninstall the latest update
Blue screen before the repair screen	Driver crash or failing storage	Check disk health and run file checks

If your drive uses BitLocker, Windows may ask for a recovery code during some steps. Have your Microsoft account access ready, or use any saved recovery printout from when encryption was turned on.

AORUS Preparing Automatic Repair Loop On Boot

If the loop starts right after a new device, a BIOS change, or a Windows update, start with the quickest “no-tools” resets. These clear stuck power states and remove common blockers.

Unplug external devices — Remove USB drives, hubs, printers, game controllers, external SSDs, and extra displays.
Force a full power-off — Hold the power button until the machine turns off, then wait 20 seconds before turning it back on.
Drain leftover power — With the PC off, unplug the charger (and remove the battery if your model allows), then hold the power button for 15 seconds.
Check power and cables — On desktops, reseat the power cable and display cable; on laptops, try the original charger.

If you can reach the Windows sign-in screen after these steps, sign in and restart once more. A single clean restart can finish pending update work that was left half-done.

Use WinRE Without Letting It Loop Forever

When the repair screen appears, choose the option that leads to Troubleshoot and Advanced options. That menu is where the real tools live. Microsoft documents Startup Repair and Startup Settings as the first stops for start failures.

Quick Machine Recovery Option On Newer Windows 11

On some Windows 11 builds, you may see a “Quick machine recovery” option inside the recovery menus. It can try a cloud remediation when a widespread boot issue is detected. If it’s there, run it once, then restart and see if the loop is gone.

Run Built-In Recovery Tools First

Before typing commands, use the buttons. They handle common boot issues fast and they keep risk low. If one tool works, you don’t need the rest.

Startup Repair

Startup Repair checks core boot files and tries to fix start problems automatically. In WinRE, select Troubleshoot, then Advanced options, then Startup Repair. Let it finish, then restart. If it boots, you’re done.

Startup Settings And Safe Mode

Safe Mode starts Windows with a reduced set of drivers. It’s useful when a driver or startup app is crashing normal boot. In WinRE, select Troubleshoot, then Advanced options, then Startup Settings, then Restart, then pick Safe Mode.

Try Safe Mode with Networking — Use it if you need internet access to remove a bad driver package or run Windows Update.
Use Safe Mode with Command Prompt — Pick it when the desktop won’t load but you can run repair commands.

Try Safe Mode — If it loads, restart once in Safe Mode, then restart again in normal mode.
Remove recent drivers — In Device Manager, roll back or uninstall the driver you changed just before the loop began.
Uninstall the latest update — In Settings, go to Windows Update history and remove the newest quality update if the timing matches.

If the loop started after installing security software, a storage tool, or a GPU driver package, remove it in Safe Mode, then restart. Windows can rebuild its driver cache after that.

System Restore Or Update Removal

If Startup Repair fails, use the tools that roll the system back without wiping your files. In WinRE Advanced options, look for System Restore and Uninstall Updates. Pick the option that matches what changed right before the loop.

Use System Restore — Choose a restore point from before the problem started, then let the restore run.
Remove a quality update — Use Uninstall latest quality update if the issue began after Patch Tuesday.
Remove a feature update — Use Uninstall latest feature update if the issue began after a version upgrade.

Repair Windows Files From Command Prompt

If the boot loop keeps returning, Command Prompt in WinRE gives you repair tools that can fix corrupted files and disk errors. Take your time and type carefully. If you see a message asking for a recovery code, enter it and continue.

Find Your Windows Drive Letter In WinRE

In WinRE, the Windows drive letter is not always C. Check it before running file repairs so commands target the right folder.

Open Command Prompt — In Advanced options, select Command Prompt.
List volumes — Type diskpart, then list volume, then find the volume with your Windows folder.
Exit DiskPart — Type exit to return to the normal prompt.

Run Disk Check

A disk check can clear file-system errors that trigger repeated repairs. Run it first, since file repairs depend on a stable disk.

Run CHKDSK — Type chkdsk C: /f /r and replace C: with your Windows drive letter.
Wait for completion — This can take a while on large drives or if errors are found.

Run SFC And DISM

System File Checker (SFC) checks protected Windows files. DISM can repair the component store that SFC relies on. Microsoft’s guidance pairs DISM and SFC for file repair work.

Run DISM online — If WinRE has network access, try dism /online /cleanup-image /restorehealth.
Run SFC — Then run sfc /scannow.
Restart the PC — Close Command Prompt and restart to test boot.

If the system still loops, rerun DISM and SFC once after CHKDSK has completed with no errors. Repeating them over and over rarely helps beyond that.

Check BIOS Boot Settings On AORUS

Boot settings can trap a PC in a loop when the wrong drive is first in the boot order or when a change flips the system between UEFI and legacy boot paths. For many GIGABYTE and AORUS boards, pressing Del during power-on opens BIOS setup, and F12 opens the one-time boot menu.

Enter BIOS setup — Power on and tap Del (some models use F2) until the BIOS screen appears.
Open the boot menu — Power on and tap F12 to pick the boot drive for one start.
Load defaults — Use the BIOS option to load default settings, then save and restart.

If you can reach Windows even once, you can reach firmware settings without timing at power-on. In Windows settings, use the recovery restart path that leads to Advanced startup, then pick the firmware option when it’s offered.

Check Secure Boot — Keep it in the same state it was in when Windows was installed. Flipping it can block boot on some setups.
Check CSM — If your drive uses UEFI, leave CSM off; if your install is legacy, keep CSM on. Mixing modes can cause loops.

Fix The Two Most Common Boot Traps

These two checks solve a lot of AORUS boot loops after updates or storage changes.

Confirm the correct boot drive — Put “Windows Boot Manager” on the internal drive first when it’s listed.
Keep UEFI consistent — If Windows was installed in UEFI mode, keep UEFI enabled and avoid switching to legacy boot.

When Fast Boot Blocks BIOS Entry

Fast boot can skip the startup logo and make it hard to enter BIOS with timing alone. GIGABYTE documents a Windows route: use the Shift + Restart path to reach the recovery menus, then enter firmware settings from there.

When The Loop Points To Hardware

If software fixes don’t stick, check for a failing SSD, loose storage cable, or unstable memory. A sudden rise in blue screens or freezes before the repair screen is a common warning sign.

Check drive health — In BIOS or with a bootable tool, review SMART status if available.
Reseat storage — On desktops, reseat SATA cables and power cables; on laptops, reseat the NVMe drive if you’re comfortable opening the back panel.
Test memory — Use Windows Memory Diagnostic from the recovery menus if it’s available, or run a bootable memory test.

If your AORUS system is under warranty and you suspect hardware, it can be smarter to stop and use the official service route instead of open the chassis further.

Last-Resort Options That Still Protect Data

If you still see the loop, you have two practical paths: reset Windows while keeping files, or do a clean install after backing up data. In WinRE, Reset this PC can keep personal files while reinstalling Windows. A clean install is more work but can clear deeper corruption.

Back up files first — In Command Prompt, copy files to an external drive, or boot from a USB installer and use its file copy options.
Try Reset this PC — Choose Keep my files when offered, then finish setup and run Windows Update.
Clean install Windows — Use official installation media, delete only the Windows partition if you understand the layout, then install fresh.

After you’re back in Windows, do three housekeeping steps so the loop doesn’t return. Install the latest Windows cumulative update, update chipset and storage drivers from the device maker, then run a full restart cycle twice.

Run Windows Update — Install pending updates, then restart.
Update AORUS drivers — Use the model page for chipset, storage, and Wi-Fi drivers.
Check disk space — Leave enough free space for updates and restore points.

After a successful boot, watch for repeats of the same crash. If “aorus preparing automatic repair” returns within a day, start with storage health checks and recent driver changes. If it returns after an update, pause updates for a time and apply the next cumulative update once it lands.

If you’re stuck and need a clear next move, write down the exact stop point in the repair screen and any error code shown. That single detail usually narrows the fix quickly.

One last note: if you saw the phrase “aorus preparing automatic repair” right after changing BIOS boot mode, undo that change first. A mismatch between the install mode and the boot mode can loop forever until it’s corrected.