Server stuck in boot loop
Windows Server 2008 R2 Stuck in Recovery Loop? Here’s the Fix | LazyAdminBlog.com
A sudden power failure is the ultimate “stress test” for a server, and sometimes the OS fails that test, landing you in an endless loop of Startup Repair. If F8 > Last Known Good Configuration didn’t save your skin, it’s time to break out the installation media.
The Prerequisites
Before you start, ensure you have your Windows Server 2008 R2 Installation Disc (or a bootable USB) ready.
- Boot from the media.
- Select your language/input settings and click Next.
- Select Repair your computer.
- Choose the OS you want to fix and click Next.
- Select Command Prompt from the System Recovery Options.
Method 1: The System File Checker (SFC)
If the power cut corrupted a core system file, SFC is your first line of defense. It compares your system files against the “known good” versions on the disc.
- In the Command Prompt, type:
sfc /scannow - Wait: This can take a while. If it finds and fixes errors, reboot and see if the loop is broken.
Method 2: Rebuilding the BCD
Sometimes the boot configuration data gets scrambled. This command scans for Windows installations and lets you add them back to the boot list.
- In the Command Prompt, type:
Bootrec /RebuildBcd - If it finds a Windows installation, press Y to add it to the boot list.
Method 3: The “Nuclear” Boot Repair
If the Master Boot Record (MBR) or the boot sector itself is toast, you need to rewrite them entirely. This is the heavy-duty fix for when the BIOS simply can’t find where Windows starts.
Run these three commands in order:
- Fix the MBR:
BOOTREC /FIXMBR - Fix the Boot Sector:
BOOTREC /FIXBOOT - Force the Update:
D:\boot\Bootsect.exe /NT60 All(Note: Replace D: with the actual drive letter of your installation disc).