Server failed to boot after a Windows Update, I only see the logo.
A failed boot after an update is usually a broken servicing stack, a driver, or a rollback that didn't finish. Don't wipe immediately: usually repairable via WinRE or safe mode.
Try this first
- 1Force three reboots during splash to enter Windows Recovery (WinRE). There: Troubleshoot, Advanced, Startup Repair as the first attempt.
- 2If that fails: Command Prompt in WinRE, dism /image:c:\ /cleanup-image /revertpendingactions, then reboot. This rolls back partial updates.
- 3If safe mode works (msconfig in WinRE cmd or via boot menu), boot to safe mode and run wusa /uninstall /kb:XXXX for the offending update.
- 4If a driver broke boot: dism with /remove-driver in WinRE, pick the driver you recently pushed (often storage or network).
- 5If none of the above work: restore from last night's backup. Hence the importance of pre-patch snapshots or system state.
When to bring us in
For a DC that won't boot: check FSMO, other DCs take over automatically, so you can recover calmly. Do not force DCPromo or metadata cleanup until you are sure the DC is truly dead.
See also
- One DC or two DCs for an SMB office?Two is almost always the right answer; one DC is a single point of failure for logon, DNS and GPOs.
- Should I split FSMO roles across two DCs?For a small domain all on one DC is fine; with two DCs splitting is tidier but not required.
- How do I know my AD replication is healthy?Replication errors creep in silently; they only surface when logins or GPOs misbehave.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.