💻 My Streaming PC Died After a Simple Reboot, and Windows Recovery Fought Me the Whole Way

What I tried, what failed, the workarounds that got me in, and what I’m changing so it never happens again.

I’ve been building websites and fixing computers since 1996. Thirty years, thousands of machines, and I can count on one hand the problems I couldn’t solve myself. So when my streaming PC wouldn’t boot on a Thursday night, I figured I’d be back online in twenty minutes.

It took me into Friday night. Here’s the whole story, plus the tricks that finally worked, so if it happens to you, it takes you less time than it took me.

💀 What Happened

Nothing dramatic. I shut the computer down, walked away, came back, and turned it on. It wouldn’t boot. It dropped me into Windows Recovery and a command prompt.

My first guess was a full drive, so I started with the usual cleanup commands. That’s when things got weird.

⌨️ The Keyboard That Couldn’t Type a Backslash

Every time I typed C:\, the screen showed C:#.

I swapped keyboards. Same thing. That ruled out hardware: the recovery environment had loaded a UK keyboard layout. On a UK layout, the key where we Americans keep the backslash types a #, and the real backslash lives on an extra key next to the left Shift that US keyboards don’t have.

Nearly every Windows repair command needs a backslash. Losing it is like getting a toolbox with every wrench welded shut.

What I tried:

wpeutil SetKeyboardLayout 0409:00000409 (switches to US, no slashes needed). Didn’t take.
Alt codes: Alt + 92 on the number pad types \. Didn’t work in my recovery environment either.

🔧 The Workaround: Old-School DOS Navigation

If you can’t type a backslash, you can still get anywhere by moving one folder at a time:

E:
cd Windows
cd System32

And cd .. goes back up a level. Old DOS skills to the rescue.

Another handy trick: the command prompt remembers a separate current folder for each drive. So C:seth (no backslash) means “the seth folder inside wherever C: currently is.” That lets you copy between drives without ever typing a slash.

🔍 Your C: Drive Might Not Be C:

This one tripped me up for a while. In Windows Recovery, drive letters get shuffled. My Windows drive showed up as E:. Then C:. A USB stick grabbed E: at one point. The “C: drive” I’d been checking for free space didn’t even have a Windows folder on it.

Here’s how to find the real one:

diskpart
list volume
exit

Look for the big NTFS volume. Then run dir on that letter. If you see Windows, Users, and Program Files, you’ve found it. (X: is the recovery environment itself, so skip it.)

Bonus confusion: in list disk, a “Free” column of 0 B does not mean your drive is full. It means there’s no unpartitioned space. Use dir and read the bytes free line instead.

❌ Everything That Failed

Once I’d found the right drive, I went through the whole playbook:

Startup Repair: ran several times, couldn’t determine the cause.
Uninstall latest quality update: hung forever.
System Restore: the restore point was corrupted.
“Reset this PC” / reinstall from recovery: refused.
DISM: “not recognized as a command.” Then “unable to access image.”
xcopy and robocopy: also missing.

That last part was the big clue. DISM, xcopy, and robocopy are normally built into Windows Recovery. Missing tools plus the wrong keyboard layout meant the recovery environment itself was damaged. It lives on the same drive as Windows, so whatever broke Windows likely broke it too. I was trying to fix a broken system with broken tools.

🤔 So What Actually Caused It?

My best guess: an interrupted Windows update. When an update is pending, Windows often finishes installing it during shutdown, the “Working on updates, don’t turn off your computer” screen. If anything goes wrong in that window, you come back to a machine that won’t start.

Windows’ Fast Startup (on by default) makes it worse. It doesn’t fully shut down. It saves the system state to the drive and reloads it next boot. If that saved state gets corrupted, the next boot fails.

Before reinstalling, I ruled out hardware:

wmic diskdrive get model,status

That returned OK, and a chkdsk scan backed it up. Good news: the drive was healthy.

✅ What Finally Worked

Booting a Windows install USB directly didn’t work on this machine, so I did it the sideways way:

On another Windows PC, I formatted a USB stick as NTFS, mounted the Windows 11 ISO, and copied all the files inside it onto the stick. (Not the .iso file itself. Recovery can’t open that.)
Back in the recovery command prompt, I found the stick’s letter with diskpart → list volume.
Switched to it and launched the installer:

I:
setup

No backslash required. The full Windows installer opened right inside the broken recovery environment.

Then I made one smart call: I installed Windows onto a different partition instead of wiping the old one. My entire old profile stayed intact, so I could copy files out at my own pace afterward.

During setup I picked English (United States) and the US keyboard. That ended the # problem for good.

📦 Getting My Stuff Back

A few things I learned moving data from the old install:

The old partition may not get a drive letter. Fix it in Disk Management, or in diskpart: select volume 3 then assign letter=O. Never click “Initialize” or “Format” on it.
You’ll get “Access denied.” The new Windows sees your old user as a stranger, even with the same name. Take ownership in one shot from an admin command prompt:

takeown /f "O:\Users\yourname" /r /d y
icacls "O:\Users\yourname" /grant %USERNAME%:F /t /c

Don’t copy all of AppData\Roaming. Mine was 44 GB, mostly caches. I grabbed only the app folders I needed (like obs-studio, which holds every scene and source).
Install the app first, then restore its folder. Install, open once, close it, then paste the old folder over the new one.
Steam games don’t need a redownload. In Steam, go to Settings → Storage → Add Drive and point it at the old library. It finds the installed games and just verifies them.
Back up your browser bookmarks. I’m glad I had my Firefox bookmarks exported.

🛡️ What I’m Doing So This Never Happens Again

Turn off Fast Startup. Control Panel → Power Options → “Choose what the power buttons do.” A shutdown should be a real shutdown, and the boot menu key starts working again.
Set Windows Update active hours to cover streaming times, and pause updates during big stream weeks.
Build a rescue USB with Ventoy. Drop Windows 11, Ubuntu, and MemTest86 ISOs on one stick and boot whichever you need. No more depending on a recovery partition living on the same drive that just broke.
Make a recovery drive (search “Create a recovery drive” in Start) while everything is working.
Take a full drive image once the rig is set up. Next time, restore in 20 minutes instead of losing a weekend.
Turn on Firefox Sync so passwords and bookmarks follow me automatically.

🎮 Back Online

The streaming rig is back, running on a clean Windows install, with my files, scenes, and settings intact. It wasn’t the twenty-minute fix I expected, and the boot process wasn’t up to my standards, but I got it done without wiping a single file.

If your PC drops you at a recovery prompt and nothing works, don’t panic. Find the real drive letter, work around whatever’s broken, and remember the old DOS way still works: one folder at a time.

Need help with a PC that won’t boot, or a website that needs fixing? That’s what I do. Get in touch with SolarBlu.net.

— Seth