A computer that won’t start right after an update is one of the most alarming tech problems there is — it usually happens with no warning, often overnight, and the screen gives you almost nothing to go on. The good news: in the vast majority of cases nothing is permanently broken. Windows updates touch low-level boot files, and when that process is interrupted or conflicts with a driver, the fix is almost always reversible if you know the right order to try things in.
Quick Decision Guide: What Are You Actually Seeing?
| What’s on screen | Start here |
|---|---|
| Completely black screen, no logo, fans spinning | Jump to Black Screen With No Error At All |
| “Automatic Repair couldn’t repair your PC” | Jump to When Automatic Repair Itself Fails |
| Stuck on the spinning dots / loading circle for 20+ minutes | Jump to Stuck On The Loading Screen |
| It boots but immediately restarts in a loop | Jump to Caught In A Restart Loop |
| You can reach Safe Mode but not normal Windows | Jump to If You Can Reach Safe Mode |
Step 1: Force the Recovery Environment to Appear
Before anything else, you need to get Windows to open its built-in recovery tools (Windows Recovery Environment, or WinRE). If it doesn’t appear automatically:
- Power the PC on, then hold the power button for 10 seconds to force a hard shutdown the moment you see the logo.
- Repeat this three times in a row. After the third failed boot, Windows automatically triggers Automatic Repair and opens WinRE — this is by design, not a bug.
- Once in WinRE, go to Troubleshoot > Advanced Options, where every fix below lives.
Automatic Repair vs. System Restore vs. Uninstall Updates: Which One First?
| Option | What it actually does | Risk to your files | Try this when |
|---|---|---|---|
| Startup Repair | Scans and fixes boot configuration files automatically | None | Always try this first — it’s the least invasive |
| Uninstall Updates | Removes the most recent quality or driver update specifically | None | The problem started right after a Windows Update notification |
| System Restore | Rolls the whole system back to an earlier saved restore point | None to personal files, but recent app installs may be undone | Startup Repair and Uninstall Updates both failed |
| Reset This PC (Keep Files) | Reinstalls Windows but keeps your personal files | Apps and settings are removed, files stay | Nothing above worked and you need the PC working today |
Black Screen With No Error At All
If the PC sounds like it’s running (fans, lights, maybe a logo flash) but the screen stays black with no error message, this is very often a graphics driver that the update touched. From WinRE, go to Troubleshoot > Advanced Options > Startup Settings > Restart, then press 4 to boot into Safe Mode. If Safe Mode displays correctly, the graphics driver is the prime suspect — uninstall it from Device Manager once you’re in, then let Windows reinstall a generic version on next boot.
When Automatic Repair Itself Fails
Seeing “Automatic Repair couldn’t repair your PC” doesn’t mean you’re out of options — it means the automated scan couldn’t identify a fixable cause, not that there isn’t one. From the same screen, open Advanced Options > Command Prompt and run these in order:
chkdsk C: /f /r sfc /scannow bootrec /fixmbr bootrec /fixboot bootrec /rebuildbcd
Each command targets a different layer (disk errors, system file corruption, and three different boot record issues). Running all five takes about 15-20 minutes total and resolves the large majority of “Automatic Repair failed” cases that aren’t hardware-related.
Stuck On The Loading Screen
If the spinning dots or Windows logo just sits there for far longer than normal (more than 20-30 minutes with the disk activity light not blinking), Windows is not actually working — it’s hung. Force a hard shutdown (hold power 10 seconds) and force WinRE open using the three-failed-boots method above, rather than waiting indefinitely.
Caught In A Restart Loop
A boot loop (Windows starts loading, then restarts itself, repeatedly) is almost always either a corrupted update file or a startup program/driver crashing the system before Windows finishes loading. The fastest fix is usually Uninstall Updates from WinRE’s Advanced Options, since this targets exactly the most recent change without touching anything else.
If You Can Reach Safe Mode
Being able to boot into Safe Mode but not normal Windows is actually good news — it confirms Windows itself is intact and the problem is a specific driver or startup program. From Safe Mode:
- Open Device Manager and check for any device with a yellow warning icon — that’s almost always the conflicting driver.
- Open Task Manager > Startup tab and disable anything you don’t recognize that was recently added.
- Run
sfc /scannowfrom an admin Command Prompt to repair corrupted system files while you have access.
Could It Be a Firmware (BIOS/UEFI) Problem?
This is the case almost nobody checks first, and it’s worth knowing about even though it’s less common. Some Windows updates bundle firmware updates for your specific motherboard or laptop model. If that firmware update was interrupted — by a power cut, a forced shutdown, or simply bad luck — the BIOS/UEFI itself can become corrupted, and the PC won’t even reach the point of trying to load Windows. Signs this is what’s happening: no logo at all, no beep codes, and WinRE never appears no matter how many times you force a hard shutdown. If you suspect this, check your motherboard or laptop manufacturer’s support site for a BIOS recovery procedure specific to your model — this is the one scenario on this page that genuinely can require a recovery USB provided by the manufacturer rather than anything inside Windows itself.
How to Avoid This Next Time
| Habit | Why it helps |
|---|---|
| Don’t force-shutdown during “Working on updates” screens | Interrupting the actual write process is the single most common cause of this exact problem |
| Keep at least one System Restore point enabled | Turns a multi-hour recovery into a 10-minute one |
| Update on a stable power source (plugged in, UPS if available) | A power cut mid-update is functionally identical to forcing a shutdown |
| Wait a few days after a major update before installing it everywhere | Widespread driver-conflict updates are usually identified and pulled within days |
Frequently Asked Questions
Will I lose my files if I use System Restore?
No. System Restore only affects system files, installed apps, and Windows settings — your personal documents, photos, and files are never touched by it.
How long should Automatic Repair actually take?
Usually 5-20 minutes. If it’s been running for over an hour with no progress and no disk activity, treat it as hung and force a restart rather than waiting longer.
Is “Uninstall Updates” the same as System Restore?
No. Uninstall Updates removes only the specific recent Windows Update package, leaving everything else (apps, other settings) untouched. System Restore is broader and rolls back to a whole saved snapshot in time.
What if I don’t have a System Restore point?
Then Startup Repair and Uninstall Updates are your two real options first. If both fail, Reset This PC (Keep Files) is the next step before considering a full reinstall.
Can a bad RAM stick cause this exact problem?
Yes, though less commonly. If you’ve tried everything above and still get random black screens or boot failures, especially if they’re inconsistent (works sometimes, fails others), run Windows Memory Diagnostic (search for it from WinRE’s Command Prompt with mdsched) to rule out hardware.
Why does this almost always happen right after an update specifically?
Updates are one of the few times Windows rewrites core boot files and driver files while the system is actually running. Any interruption during that specific window — a crash, a power loss, an incompatible driver being loaded — has a much higher chance of leaving things in a broken state than during normal day-to-day use.
Should I try to boot from a USB recovery drive instead?
Only if WinRE genuinely won’t appear after three forced shutdowns. If you can reach the Advanced Options menu at all, you don’t need external media — everything above works from the built-in recovery environment.
Is it safe to run chkdsk if I’m not sure there’s a disk problem?
Yes. chkdsk is non-destructive for a healthy drive — it scans and only takes action if it actually finds errors. There’s no downside to running it as a precaution.
My PC shows a manufacturer logo but nothing after that — is that the same problem?
If you never see Windows even start to load (just the manufacturer splash screen, indefinitely), that points more toward the firmware/BIOS scenario above rather than a Windows update issue, since Windows itself hasn’t been reached yet.
How do I know if it’s actually fixed and not just temporarily working?
Once you’re back in Windows, immediately check Settings > Windows Update > Update history to confirm the problematic update either failed or was successfully reinstalled cleanly, and let the PC fully restart once more normally before considering it resolved.