For the second time I have had a Windows Update that failed?

[MikeHawthorne]

I got another notice of a new update and told it to go ahead, but after going through the process, it said something didn't go right. Don't worry, we are undoing the update.

Then it went through the installation process, gave me the same message, and finally loaded Windows.
I don't recall whether the previous one was ever installed.

I got a large update recently that went through.

Any ideas about what's going on?

Nothing that I found shows any error messages except the update!

 

[10thdimension]

oh i see your fix didnt work, visit my guide for a full proof fix! i linked it in this convo, also its in the first section in the windows forum section named [SOLVED]

 

[ChatGPT]

If you’re replying to another member in this thread, it’ll come across better (and get more cooperation) if you avoid “your fix didn’t work” and instead frame it as “if the usual steps didn’t work for you, here’s the proven path that fixed mine.”
Here’s a clean reply you can paste:

If you’re still failing KB5077181 with 0x800f0983 / PSFX_E_MATCHING_COMPONENT_DIRECTORY_MISSING (often stalls around 78–79% with TrustedInstaller/WER behavior), the standard SFC/DISM/WU-reset steps usually won’t fix it.
I documented a full start-to-finish fix here (includes ISO build checks + BitLocker notes):
https://windowsforum.com/threads/401132[/url]
Quick requirement: the ISO must match your edition/arch and be same or newer build than your current install (e.g., 26200.7840 vs 26200.7623) so “Keep personal files and apps” is available.

If you want to make it even more actionable, ask them to post these two lines so you can confirm they’re on the same failure pattern:

• winver (Version + OS Build)
• The exact CBS error line(s) showing 0x800f0983 / PSFX_E_MATCHING_COMPONENT_DIRECTORY_MISSING

That keeps the discussion technical and avoids it turning into “works for me / doesn’t work for you” back-and-forth.

 

[10thdimension]

If you’re replying to another member in this thread, it’ll come across better (and get more cooperation) if you avoid “your fix didn’t work” and instead frame it as “if the usual steps didn’t work for you, here’s the proven path that fixed mine.”
Here’s a clean reply you can paste:

If you want to make it even more actionable, ask them to post these two lines so you can confirm they’re on the same failure pattern:

• winver (Version + OS Build)
• The exact CBS error line(s) showing 0x800f0983 / PSFX_E_MATCHING_COMPONENT_DIRECTORY_MISSING

That keeps the discussion technical and avoids it turning into “works for me / doesn’t work for you” back-and-forth.

yeah i meant YOUR fix didnt work mr BOT, my fix does lol

 

[ChatGPT]

My fix was the same fix you ultimately used in your guide: verify the ISO is same branch/edition + newer build (26200.7840), then do an in-place repair upgrade (keep files/apps) and re-try Windows Update.
So if you mean “the early/basic steps like SFC/DISM/WU reset didn’t work,” I agree—and your guide correctly documents that the repair-install is the durable solution for this PSFX/servicing-baseline mismatch.
If you want a short one-liner to reply back with (that’s accurate and not adversarial), use:

The standard SFC/DISM/WU-reset steps often won’t fix 0x800f0983 / PSFX_E_MATCHING_COMPONENT_DIRECTORY_MISSING. The reliable fix is an in-place repair upgrade using same edition/arch media that’s the same-or-newer build (e.g., 26200.7840), then rerun Windows Update.

If you tell me which post you’re replying to (or quote it), I can tailor the wording to that person’s exact error/build.

 

[10thdimension]

My fix was the same fix you ultimately used in your guide: verify the ISO is same branch/edition + newer build (26200.7840), then do an in-place repair upgrade (keep files/apps) and re-try Windows Update.
So if you mean “the early/basic steps like SFC/DISM/WU reset didn’t work,” I agree—and your guide correctly documents that the repair-install is the durable solution for this PSFX/servicing-baseline mismatch.
If you want a short one-liner to reply back with (that’s accurate and not adversarial), use:

If you tell me which post you’re replying to (or quote it), I can tailor the wording to that person’s exact error/build.

[SOLVED] KB5077181 Failing at 78–79% — Full Start‑to‑Finish Fix Guide (With ISO Checks + BitLocker Notes)

Posting this to help anyone dealing with the same issue I spent days fighting. My system refused to install KB5077181 (26200.7840) and always failed in the exact same way. Here is everything I did from start to finish, including the final fix and the verification steps recommended by others in this thread.

---------------------------------------
1. Symptoms of the Problem
---------------------------------------
• Update would reach 78%
• Instantly jump to 79%
• Windows Error Reporting (WER) would pop up and stay open
• TrustedInstaller.exe would crash
• CPU would drop to 0%
• Update would immediately fail
• Manual MSU installs failed the same way
• CBS logs showed error 0x800F0983 (PSFX_E_MATCHING_COMPONENT_DIRECTORY_MISSING)

This is classic behavior of a PSFX commit/hydration failure, often caused by a baseline/component mismatch or missing component directory.

---------------------------------------
2. Things I Tried That DID NOT Fix It
---------------------------------------
These did nothing to resolve the underlying issue:
• SFC /scannow
• DISM /restorehealth
• Resetting Windows Update components
• Clearing SoftwareDistribution
• Renaming Catroot2
• Manual MSU installs
• Safe Mode installs
• Reboots
• Removing optional features/languages
• Full OS reset (the failure returned immediately)

None of these touched the real corruption.

---------------------------------------
3. ISO Sanity Check (Important Before Repair-Install)
---------------------------------------
Before running setup.exe, I verified the ISO was the correct build and edition.

Command:
dism /Get-WimInfo /WimFile:X:\sources\install.wim

I confirmed:
• Architecture matched (x64)
• Edition matched (**Home**, Index 1)
• ServicePack Build was **7840**, which is newer than my broken system’s **7623**

This ensures “Keep personal files and apps” works and that the repair install actually lays down a newer servicing baseline.

---------------------------------------
4. BitLocker Safety Step (Highly Recommended)
---------------------------------------
Because I previously hit a BitLocker recovery prompt during failed servicing attempts, I suspended BitLocker before running the repair install.

Commands:
manage-bde -protectors -disable C:
(After everything was stable)
manage-bde -protectors -enable C:

To confirm BitLocker is fully re-enabled afterward:
manage-bde -protectors -get C:

---------------------------------------
5. The Actual Fix (The Only Thing That Worked)
---------------------------------------
I performed a full **repair‑install (in‑place upgrade)** using the verified Windows 11 ISO.

This rebuilds:
• WinSxS (component store)
• Servicing stack
• Catalogs and manifests
• PSFX delta structures
• Baseline component versions

This step completely resets the servicing chain without wiping apps or files.

---------------------------------------
6. What Happened After the Repair‑Install
---------------------------------------
After the repair‑install, I ran Windows Update again.

This time the behavior was totally different:
• It stayed at 78% for 15–20 minutes (normal during commit/hydration)
• TrustedInstaller used 1–2 GB RAM (normal)
• WER flashed briefly but did NOT stay open
• No crash
• No jump to 79%
• No rollback

Eventually it moved to 95%, then 100%, and completed successfully.

---------------------------------------
7. Post-Fix Verification (Recommended)
---------------------------------------
To confirm everything was correct, I ran:

winver
dism /online /get-packages | findstr /i 5077181

Both confirmed:
• System is now on the newer 26200.7840 baseline
• KB5077181 is properly installed
• Windows Update no longer offers the update

---------------------------------------
8. Final Result
---------------------------------------
Windows Update now shows:
• KB5077181 — Completed
• Windows Security Platform Update — Completed
• System fully up to date and stable

---------------------------------------
9. Optional Cleanup
---------------------------------------
After confirming stability for a day or two, you can safely remove the leftover Windows.old folder:

Settings → System → Storage → Temporary files
(or Disk Cleanup → “Previous Windows installation(s)”)

---------------------------------------
10. Conclusion
---------------------------------------
If KB5077181 (or any LCU) fails at 78→79% with a WER crash, the issue is a **baseline/component store mismatch (PSFX) that DISM cannot repair**.

A **repair‑install using correct or newer ISO media** is the fix.

Extra credit tip: keep the working ISO or USB you used — it becomes a known-good recovery path if servicing ever gets stuck again.

Optional cleanup (after confirming everything is stable):

Settings → System → Storage → Temporary files
Remove “Previous Windows installation(s)” (this deletes C:\Windows.old)

Note: Some OEM tools (like Dell SupportAssist) may automatically remove Windows.old or setup temp files. If you only see a small amount of cleanup data (e.g., ~5–6 GB), that’s normal — it just means the system already cleaned up the leftover setup files.

(Note: The screenshot below is from BEFORE the repair-install.)

here is my full guide^

 

[ChatGPT]

Thanks for reposting it — that version is complete and internally consistent now (error signature, “what didn’t work,” ISO build/edition sanity check, BitLocker suspend/re-enable, in-place repair upgrade, and the post-fix verification block).
If you want to make it even easier for others skimming the thread, two small “presentation” tweaks help a lot:
1) Put the two “must match” requirements in one bold line near the top

• Same edition + architecture (Home x64)
• ISO ServicePack Build must be ≥ current UBR (your example: 7840 > 7623)

2) Add a “fast triage” mini-block (right after Symptoms) so people can quickly confirm they’re on the same failure pattern:

winver
findstr /i 0x800f0983 %windir%\Logs\CBS\CBS.log | more

Other than that, it’s genuinely “copy/paste and follow” quality. If the thread has a “Solution” selector, make sure the forum marks that post as the accepted solution so searchers land on it immediately.

 

[datawizard0103]

When I logged in a few minutes ago it tried without asking, and failed again.
It went though the whole thing again and then Reset it again without completing it.

Windows is still trying to finish that failed update during boot. Run dism /online /cleanup-image /startcomponentcleanup as admin, then reboot twice to clear any stuck update files. Check Update History to make sure KB5077181 is not partially installed. If it keeps retrying after that, an in place repair install with the latest Windows 11 ISO will reset the update system without deleting your files.

 

[10thdimension]

Windows is still trying to finish that failed update during boot. Run dism /online /cleanup-image /startcomponentcleanup as admin, then reboot twice to clear any stuck update files. Check Update History to make sure KB5077181 is not partially installed. If it keeps retrying after that, an in place repair install with the latest Windows 11 ISO will reset the update system without deleting your files.

may I ask, I'm running on a dell xps 16 (9640), what kind of machine are you having these problems with? it seems to only be affecting a small amount of people leading me to believe it has to be a certain laptop or brand. yes, definitely do the in place reinstall, you'll get a clean image with all; your stuff kept.

 

[datawizard0103]

may I ask, I'm running on a dell xps 16 (9640), what kind of machine are you having these problems with? it seems to only be affecting a small amount of people leading me to believe it has to be a certain laptop or brand. yes, definitely do the in place reinstall, you'll get a clean image with all; your stuff kept.

I’ve seen this on different PCs, not just one model, but newer Dell XPS systems do hit it more when the BIOS or chipset drivers are outdated. First update your BIOS and drivers from Dell Support. Then pause updates and clear the Windows Update cache by stopping the Windows Update service, renaming the SoftwareDistribution folder, and starting the service again. This forces Windows to rebuild the update files. If it still keeps looping, the in place repair install is the safest fix and keeps your files.

 

[MikeHawthorne]

I'm Running a Falcon NoRth West Talon computeR that cost almost 5,000 dollaRs.

I finally solved the problem! SoRt of.
I found some code that stops updates and applied it.

Now to the R pR oblem?
I want to emphasize this.
This only happens on this fo um.

Eveything woks fine evey place else. This must have something to do with the coding in this foum somewhee. If this isn't happening to anyone else, I can't imagine what else would be causing it. The places whe e a space appea s I put the space in because it wouldn't type any thing the e, unless I typed a capitol R!

I Repeat. I've neveR seen this anywheeR except on this foRum! My spell checkeR does catch the pRoblem but it can't coRRect it!
It shows it, but can't overcome what causes it.

 

[ChatGPT]

Mike — I believe you.
If it only happens on this forum, then this is almost certainly not a Windows keyboard problem. It points much more toward a browser + rich-text editor interaction on this site, or a site-specific extension/cache issue. XenForo-based forums do have a BB-code/plain-text editor toggle, and XenForo discussions also point to browser/cache/editor-specific problems with the rich editor. Browser-level key glitches that affect only web text boxes are also a real thing.

First: about the update​

What you did likely stopped the symptom, not the root cause.
If you want the real fix later, the solved thread on this forum was the repair-install / in-place upgrade method using matching or newer ISO media. That is the proper path if you decide to fix Windows Update instead of just blocking it.

---

Now the forum typing problem​

Let’s treat this as a site-specific editor issue.

Do these in order​

1) Test the forum in InPrivate / Incognito​

1. Open your browser’s InPrivate/Incognito window.
2. Log into WindowsForum.
3. Try typing several words with lowercase r.

Expected result​

• If the problem is gone, the cause is almost certainly an extension or saved site data.

---

2) Try a different browser​

1. If you use Chrome, try Edge or Firefox.
2. If you use Edge, try Firefox or Chrome.
3. Type a reply here.

Expected result​

• If it only happens in one browser, then the problem is local to that browser, not your keyboard and probably not the forum code alone.

---

3) Disable writing-related extensions​

Temporarily disable anything that touches text boxes:

• Grammarly
• Microsoft Editor
• LanguageTool
• Any AI writing helper
• Any autocorrect / spellcheck / keyboard remap extension

Then refresh the forum and test again.
This is the most likely cause if the issue is only here.

---

4) Clear site data for windowsforum.com​

Do this only for this site, not your whole browser.

In Edge / Chrome​

1. Open WindowsForum.
2. Click the padlock or site info icon next to the address bar.
3. Open Site settings.
4. Clear data / reset permissions for this site.
5. Close the tab.
6. Reopen the forum and sign in again.

This clears corrupted site-specific editor data without touching everything else.

---

5) Switch out of the rich-text editor​

If the editor toolbar shows a BB code / plain text toggle, use it and test there.
This matters because rich-text editors can behave differently from plain text ones, and that difference is exactly where these odd “one letter won’t type correctly” bugs tend to show up.

---

6) Temporary workaround​

Until it’s fixed:

1. Type your post in Notepad.
2. Copy it.
3. Paste it into the forum.

That won’t solve the cause, but it will stop the irritation.

---

What I need from you next​

Please reply with just these 3 things:

1. Which browser are you using?
2. Does it still happen in InPrivate / Incognito?
3. Does it still happen in a different browser?

If you give me those three answers, I can narrow this down very fast.

 

[10thdimension]

I'm Running a Falcon NoRth West Talon computeR that cost almost 5,000 dollaRs.

I finally solved the problem! SoRt of.
I found some code that stops updates and applied it.

Now to the R pR oblem?
I want to emphasize this.
This only happens on this fo um.

Eveything woks fine evey place else. This must have something to do with the coding in this foum somewhee. If this isn't happening to anyone else, I can't imagine what else would be causing it. The places whe e a space appea s I put the space in because it wouldn't type any thing the e, unless I typed a capitol R!

I Repeat. I've neveR seen this anywheeR except on this foRum! My spell checkeR does catch the pRoblem but it can't coRRect it!
It shows it, but can't overcome what causes it.

This is literally the funniest thing I've seen in a long time. Thank you for making me laugh today. I would say you're probably correct and not to worry too much about it, read ChatGPT's response and listen, usually the AI is correct on these type of things. I'm watching this thread incase you actually need some help by a human

 

[Mike]

I'm Running a Falcon NoRth West Talon computeR that cost almost 5,000 dollaRs.

I finally solved the problem! SoRt of.
I found some code that stops updates and applied it.

Now to the R pR oblem?
I want to emphasize this.
This only happens on this fo um.

Eveything woks fine evey place else. This must have something to do with the coding in this foum somewhee. If this isn't happening to anyone else, I can't imagine what else would be causing it. The places whe e a space appea s I put the space in because it wouldn't type any thing the e, unless I typed a capitol R!

I Repeat. I've neveR seen this anywheeR except on this foRum! My spell checkeR does catch the pRoblem but it can't coRRect it!
It shows it, but can't overcome what causes it.

There's no issues with the text editor on this site, in fact, though, it has been planned to be swapped out for some time. I can't tell you what the cause is but its unusual and strange in that universally it should not happen in Chrome, Edge, Firefox, Brave, Comet, or I suppose, other browsers.