[SOLVED] Windows 10 Home 22H2 - SFC/DISM Errors

R

robdb

Active member
Joined
Aug 14, 2024
Posts
40
Hello,

I had a bad Windows update event, during which the computer stuck on the updating/don't reboot screen for multiple hours. I eventually reset the power, and now I'm getting occasional BSODs, and SFC/DISM are reporting errors/unable to fix.

I have attempted to run DISM with an Install.wim file from the media creation tool as a /source without success—DISM error 0x800f081f. The CBS log shows 114 CBS Manifest Corruption hits and 1 CSI Payload Corruption hit preceded by messages regarding missing multiple mum/cat pairs.

Thank you for your time!
 

Attachments

Can anyone assist with this issue? Unfortunately, the BSODs are still happening randomly.
 
Hi and welcome to Sysnative,

I'm not an BSOD expert, but do the following first, then I can take a quick look at the dump files before we start with replacing the missing / corrupted files.

Download the
6092ba29b640f-SysnativeBSODCollectionApp_101-2.png
Sysnative BSOD Dump + System File Collection App to your desktop.
  • Right-click on SysnativeBSODCollectionApp.exe and select "Run as administrator".
  • When the tool is ready, it will open the directory: C:\Users\<username>\Documents.
  • Post the zipfile: SysnativeFileCollectionApp.zip as attachment in your next reply.
  • The textfile 'BSODPostingsInstructions' you may close.
 
Hello, and thank you! I've attached the collected information. The output indicated that it skipped the services and tracert reports because they took too long to generate.
 

Attachments

Could you be seeing old data? I discovered a faulty stick while running HP diagnostics a week or two ago. I replaced the defective stick, and all four test fine now.

Edit: I checked my Amazon order history. Replacement RAM was delivered on August 13th, and I installed it that day.
 
The latest dump is from Thu Aug 29 15:22:58, and there's still an memory issue as far as I can tell.
So I would strongly suggest to start a new thread in the BSOD section. Then you will receive advice of one of the BSOD experts, post also a link to this thread as reference.

Afterwards, we can resume this thread to recover the corruptions.
 
I ended up replacing my RAM entirely. I'll wait a week or so before continuing, but is there anything in the interim that I can check/clear/keep an eye on before we continue repairing the system?
 
Hi,

Please run the following DISM command and attach a new copy of the CBS logs.
Code: 
DISM /online /cleanup-image /RestoreHealth
 
Hi,

Step 1. Download
67139f7e69a58-SFCFix-ico.PNG
SFCFix and save it to your desktop.

Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
67139f52b3c1e-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code: 
DISM /online /cleanup-image /RestoreHealth
 

Attachments

DISM completed without error. I was also able to install Windows Updates once again. For good measure, I also ran SFC, and it found no issues.
 

Attachments

Hi,

That's great news. If there are no remaining issues whe can mark this thread as solved... (y)
 
Sigh. I may have spoken too soon. More minor Windows Updates are successful, but the larger feature pack is still erroring out. Since the other symptoms have been alleviated, could this be unrelated? I've attempted to install it twice, but I checked DISM and SFC in between—both ran without error.

Here's what I see in Event Viewer:


XML: 
Log Name:      System
Source:        Microsoft-Windows-WindowsUpdateClient
Date:          11/23/2024 4:04:17 PM
Event ID:      20
Task Category: Windows Update Agent
Level:         Error
Keywords:      Failure,Installation
User:          SYSTEM
Computer:      VORTEX
Description:
Installation Failure: Windows failed to install the following update with error 0x800707E7: Feature update to Windows 10, version 22H2.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WindowsUpdateClient" Guid="{945a8954-c147-4acd-923f-40c45405a658}" />
    <EventID>20</EventID>
    <Version>1</Version>
    <Level>2</Level>
    <Task>1</Task>
    <Opcode>13</Opcode>
    <Keywords>0x8000000000000028</Keywords>
    <TimeCreated SystemTime="2024-11-23T22:04:17.3803506Z" />
    <EventRecordID>643361</EventRecordID>
    <Correlation />
    <Execution ProcessID="10004" ThreadID="11724" />
    <Channel>System</Channel>
    <Computer>VORTEX</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="errorCode">0x800707e7</Data>
    <Data Name="updateTitle">Feature update to Windows 10, version 22H2</Data>
    <Data Name="updateGuid">{098e93a5-93b5-405b-814e-3009a27b4864}</Data>
    <Data Name="updateRevisionNumber">1</Data>
    <Data Name="serviceGuid">{8b24b027-1dee-babb-9a95-3517dfb9c552}</Data>
  </EventData>
</Event>
 
Hi,

Upload a copy of the CBS folder
  • Open Windows Explorer and browse to the C:\Windows\Logs folder.
  • Right-click on the CBS folder and choose Send to > Compressed (zipped) folder.
  • Now the message will appear, "Windows cannot create the Compressed (zipped) Folder here. Do you want it to be placed on the desktop instead?"
  • Click on the Yes button here.
653a64385d891-618e949e09fef-CBS-Folder.png

  • Attach the file CBS.zip to your next reply. If the file is too large to attach, upload the CBS.zip file to www.wetransfer.com and post the link in your next reply.
 
Hi,

Upload your COMPONENTS hive.
  • Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
  • Please copy this file to your desktop.
  • Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
  • Right-click on this file on your desktop and select Send To > Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
  • If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.
 
File attached.

It did nothing when I attempted to open C:\Windows\System32\Config directly from the run prompt. When I navigated to C:\Windows\System32\ in Explorer, I could not open the folder at all - no errors or messages about not having permission, simply no reaction whatsoever. I ended up copying it to my Desktop via cmd as admin.
 

Attachments

Hi,

Open an elevated command prompt run the following commands and copy paste the result in your next post.
Code: 
dir /s /a %systemroot%\WinSxS\amd64_microsoft-windows-e..oyment-languagepack_31bf3856ad364e35_10.0.19041.4355_en-us_35d4af7ab21f03a8 > "%userprofile%\Desktop\Dirlist.txt"
certutil -hashfile %systemroot\WinSxS\Manifests\amd64_microsoft-windows-e..oyment-languagepack_31bf3856ad364e35_10.0.19041.4355_en-us_35d4af7ab21f03a8.manifest SHA256
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top