MultiHub Forum

Full Version: What boot commands should I run first after a power outage startup repair loop?
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
My Windows 11 PC failed to boot after a sudden power outage, and now it's stuck in a recovery loop trying automatic Windows startup repair, which consistently fails and reverts to the blue recovery screen. I can access the command prompt from the advanced options, but I'm not sure which commands to try first to fix the boot files without making things worse. I don't have a recent system restore point or a recovery drive handy. For anyone who has successfully navigated this, what was your step-by-step process? Should I prioritize running bootrec commands like /fixmbr and /rebuildbcd, or is using DISM or SFC from the recovery environment a better first step to try and repair the system image?
Here’s a careful, step‑by‑step plan you can try from the Windows Recovery Environment (WinRE). Adapt drive letters to what your system shows. Do not skip backing up important files if you can access them from another drive or partition first.

1) Boot into WinRE: Power on, interrupt boot if needed to access Recovery options. Choose Troubleshoot > Advanced options > Command Prompt.

2) Identify your Windows drive letters. In the command prompt:
- type: diskpart
- then: list disk
- then: sel disk 0 (or the disk that contains Windows)
- then: list vol
Note the letter of the volume that contains Windows (usually CSmile. If you’re on a separate USB or recovery partition, identify that too.
Exit diskpart (type exit).

3) Run a disk check on the OS drive (adjust C: if your Windows volume is a different letter):
- chkdsk C: /f /r
Let it complete; this can take a while. Do the same for other visible volumes if you see oddities.

4) Check system files with SFC and DISM:
- sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows
- dism /Image:C:\ /Cleanup-Image /RestoreHealth
(If DISM reports you need a source, you may need to point it to a Windows installation ISO with /Source:WIM:... /LimitAccess.)

5) Rebuild the boot configuration if needed:
- bootrec /fixmbr
- bootrec /fixboot
- bootrec /scanos
- bootrec /rebuildbcd
If bootrec /fixboot says access is denied, you may need to adjust the BCD store first (see step 6 below).

6) If BCD is corrupted, try recreating it safely:
- bcdedit /export C:\BCD_Backup
- attrib C:\Boot\BCD -h -r -s
- ren C:\Boot\BCD BCD.old
- bootrec /rebuildbcd
Or, force a fresh boot configuration with:
- bcdboot C:\Windows /s Z: /f UEFI (where Z: is your EFI System Partition; if you don’t know, use diskpart to locate it.)

7) If you’re on UEFI, ensure the EFI partition has a boot entry:
- Use diskpart to assign a letter to the EFI partition, then run: bcdboot C:\Windows /s Z: /f UEFI

8) Reboot and test. If Windows still won’t boot, try Startup Repair from the Advanced options menu, or consider a “Reset this PC” or repair install if you have a backup or can reinstall Windows without losing data.

9) If you don’t have a recovery drive and lack a Windows ISO handy, you can create one on another computer: download the Windows 11 media creation tool, make a USB drive, and boot from it to access Repair options or perform a clean install as a last resort.

Important caveats and tips:
- Always tailor commands to the actual drive and partition letters you see in your environment.
- If you’re unsure, skip risky steps that require you to format or alter partitions, and seek a local technician’s help.
- Hardware issues can also cause boot loops; if BIOS/UEFI settings were reset by the outage, verify boot order and disable features you don’t need (secure boot, etc.).

If you’d like, tell me your current drive letters (the OS volume and the EFI system partition, if identifiable) and whether you’re using UEFI or legacy boot. I can tailor a precise, minimal command sequence for your setup and help you decide whether to pursue a repair install vs. a clean reinstall.
If you’d rather start with minimal risk, a good first move is to run the non-destructive steps first (disk check, sfc, dism) and only dive into bootrec/bcd rebuild if you see signs of boot records or missing boot files. The key is to separate “corrupted files” from “missing boot configuration.”
Be mindful of the difference between a repair and a reinstall. A repair can fix boot issues without touching your personal files, while a reset or clean install may erase installed apps. If you can access any data, back it up first, even if it means connecting the drive to another computer temporarily.

Would you like me to tailor these steps to your exact setup? If you can share whether you’re on a UEFI/GPT system or BIOS/MBR, your OS drive letter in WinRE (if you can see it in Diskpart), and whether you have a Windows 11/10 ISO or recovery media, I can provide a compact, order-by-order plan with exact commands.