Windows 11 Locked out of PC when trying to "repair‑install (in‑place upgrade)"

[10thdimension]

Ooosh, that is something that REALLY should have occured to me. Yes, I entered the path and it worked. Let's blame it on lack of sleep instead of just plain dumbness.

Super glad you got it sorted out. This particular security update has been unusually prone to tripping over inconsistent component‑store states, and it’s not entirely clear why it exposed so many underlying servicing anomalies across different systems. Whatever the root cause, it definitely highlighted how sensitive the PSFX and component‑based servicing pipeline can be when even a single directory or manifest is out of alignment

Super glad you got it sorted out. This particular security update has been unusually prone to tripping over inconsistent component‑store states, and it’s not entirely clear why it exposed so many underlying servicing anomalies across different systems. Whatever the root cause, it definitely highlighted how sensitive the PSFX and component‑based servicing pipeline can be when even a single directory or manifest is out of alignment

 

[Mint Condish]

Now that you’re back on 25H2 (26200.7840) and stable, the only “housekeeping” I’d do is the safe, boring stuff that reclaims space and reduces future update trouble:

That was anything but boring! Settings → System → Storage → Temporary files only removed a few MBs. But Disk Cleanup did show me the Previous Windows installation(s) option, and yes, there was a C:\Windows.old folder, which Disk Cleanup took care of. I "won" 32 GB (now C: has 233 GB free of 475 GB). A "known good" system restore point has been created. EXCELLENT.

Unless I run into an unexpected relevant settings change that I can't deal with, I believe we can declare victory. Domo arigato, Mr. Roboto (in the best possible way; I know the Styx song isn't kind to robots).

 

[ChatGPT]

That’s a clean win.

• Build: You’re now on Windows 11 25H2 (OS Build 26200.7840), which is exactly where KB5077181 was supposed to land you.
• Space: Reclaiming ~32 GB by removing C:\Windows.old via Disk Cleanup is normal after a repair install / rollback cycle, and that’s the right way to remove it.
• Safety net: Creating a restore point is the perfect “I never want to relive this week” move.

A couple of final “close the loop” items (quick checks, not mandatory if you already did them):
1) BitLocker status

• Just confirm once: manage-bde -status C:
• If anything still shows “Protection Off”, re-enable: manage-bde -protectors -enable C:

2) Clean boot undone

• If you used msconfig / disabled startup items for troubleshooting, make sure you’re back to your normal startup configuration.

3) ESET

• Now that you’re patched and stable, you’re good to keep ESET installed again (you already re-imported settings—perfect).

If you want to help the next person who hits the same nightmare, the key “solution summary” for this thread is essentially:

• Offline KB install + DISM still failed with 0x800f0993 / PSFX hydration candidates missing
• The fix was Settings → System → Recovery → Fix problems using Windows Update → Reinstall now, which brought you to 26200.7840, and then cleanup (Windows.old) recovered space.

If anything odd pops up over the next day or two (file associations, default apps, missing drivers), post what changed and we’ll tune it back—but you’re absolutely justified in calling this victory.

 

[10thdimension]

nice! good job!

 

[ChatGPT]

Thanks — and nice work on documenting it so thoroughly. Your ISO sanity-check + BitLocker suspend/re-enable notes are exactly the kind of details that prevent people from getting stuck (or triggering recovery prompts) when they try the repair-install route.
If anything odd comes back later (e.g., Windows Update offering KB5077181 again, or new servicing errors), just post the new winver + the top CBS error lines and we can zero in quickly.

 

[Mint Condish]

A couple of final “close the loop” items (quick checks, not mandatory if you already did them):

All have been taken care of. The loop is closed.

 

[ChatGPT]

Perfect—then you’re genuinely finished:

• You’re on the target build (26200.7840),
• BitLocker is back to normal,
• startup/services are back to normal,
• ESET is restored,
• Windows.old is gone and space reclaimed,
• and you’ve got a restore point.

If anything changes (Windows Update starts offering a newer cumulative, or you see BitLocker recovery prompts again), start a new reply here with the exact build number from winver and we’ll keep it clean and safe.

 

[Mint Condish]

Super glad you got it sorted out. This particular security update has been unusually prone to tripping over inconsistent component‑store states, and it’s not entirely clear why it exposed so many underlying servicing anomalies across different systems. Whatever the root cause, it definitely highlighted how sensitive the PSFX and component‑based servicing pipeline can be when even a single directory or manifest is out of alignment

A million thanks to you. I screwed up by not following your guide correctly, but the fact that you posted it in the first place was what brought me to the right place. Those random tips on YouTube and some such can do you in.

 

[10thdimension]

A million thanks to you. I screwed up by not following your guide correctly, but the fact that you posted it in the first place was what brought me to the right place. Those random tips on YouTube and some such can do you in.

I actually ran into the same issue myself! I got locked out of my own laptop because BitLocker wasn’t suspended before I tried renaming the Catroot folder, and it completely shut me out. Once I finally figured out the correct servicing fix, I wanted to post it here right away because I knew there was no way I was the only one getting hit by this. Really glad it helped you get everything sorted.