Windows 10 updates failing and SFC/DISM corruption

[frg]

Hello,

I'm new to the forum, and I'm looking for help with Windows Updates failing on Windows 10.

I've recently updated the computer from Windows 10 2004 to 21H2 using the Media Creation Tool. The computer did the upgrade successfully, although it took hours.

Once the upgrade was installed, I tried to search for updates on Windows Update to install the latest updates, but then every update fails. They're downloaded, but none of them are installed at all. They fail with error code 0x8007000d. Trying to install them from the .msu files fro Microsoft Update Catalog fails too. The Windows Update troubleshooter fails right after opening it too.

While running SFC and DISM to look for and repair Windows components corruption, SFC can't finish the operation after 5% showing error code 0x80071160 in the CBS.LOG. DISM fails with "Error 4448" "WOF driver encountered a corruption in the compressed file's resource table". I've used SFCFix (without scripts) to try to gather more information but it founds no corruption at all.

I've attached the CBS.LOG, DISM.LOG, SFCFIX.TXT, COMPONENTS hive and screen captures of SFC and DISM results (as instructed in the "Windows Update forum posting instructions"). Hope they would be usfeul. If any other information is needed, please, ask me.

Thank you in advance for any help, and for all the help provided in this forums :)

 

[DR M]

Hi.

Welcome to Sysnative Forums.

I am a Security Analyst and a Windows Update Trainee, and I will be assisting you regarding your computer's issues. Since I'm still in training, my fixes have to be approved by a qualified Update Expert, so there may be a slight delay in my replies. Look at it as a good thing though, since you will have two people looking at your problem.

I'll be back to you as soon as I am ready. Thank you for your patience.

 

[DR M]

Hi, frg.

Thank you for your patience.


1. SFCFix

Please do the following to start with.

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Download the attached SFCFix.zip and save it on your Desktop.
• Save any work you have open, and close all programs.
• Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
  
  
  
  
  
  
• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Attach that file to your next reply.

 

[frg]

Hi.

Welcome to Sysnative Forums.

Thanks

I am a Security Analyst and a Windows Update Trainee, and I will be assisting you regarding your computer's issues. Since I'm still in training, my fixes have to be approved by a qualified Update Expert, so there may be a slight delay in my replies. Look at it as a good thing though, since you will have two people looking at your problem.

Thanks a lot, and don't worry about any delays, take any time you may need.

1. SFCFix

Please do the following to start with.

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Download the attached SFCFix.zip and save it on your Desktop.
• Save any work you have open, and close all programs.
• Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Attach that file to your next reply.

I have downloaded the file and I'll try to run SFCFIX with it tonight (or tomorrow morning) and post a reply as soon as possible.

If SFCFIX seems to complete the fix succesfully, do you want me to attach any other files, or run again SFC or DISM and attach their updated logs?

Again, thank you for your help

 

[DR M]

Thanks for letting me know.

Yes, if the fix gets successfully processed, I would like you to run SFC and DISM (with this order), and provide to me screenshots with the result, when they complete. But let's first see the SFCFix.txt.

 

[frg]

But let's first see the SFCFix.txt.

Hello,

Sorry for the long delay to run the fix...

I couldn't take a screenshot of the SFCFIX results if it was of any help, but the SFCFIX.TXT is attached. It seems it completed its tasks successfully. If you say it's OK, I'll run SFC and DISM as you told me on the previous message. If you want to check something else or have me to attach any other files that you may need to look at, just tell me.

Thanks again for your time helping me, and sorry for the delay posting the fix results

 

[DR M]

Hi, frg.

The log seems fine. So now, let's see the 2 screenshots after the SFC and DISM scans.

 

[frg]

Hi,

I did run SFC and DISM, but they seem to fail at the same point as before... SFC says it can't perform the requested operation at 5% and DISM shows the "Error 4448: WOF driver encountered a corruption in the compressed file's resource table" at 6,9%.

I have attached the screen captures and the current CBS folder logs, the DISM log, and COMPONENTS, just in case you may need them too. If you need any other file, just tell me.

Thanks for your help

 

[DR M]

Hi, frg.

1. SFCFix

Please do the following:

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Download the attached SFCFix.zip and save it on your Desktop.
• Save any work you have open, and close all programs.
• Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
  
  
  
  
  
  
• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Attach that file to your next reply.

2. DISM/CBS

Run DISM command and attach the screenshot of the result. If it fails, attach a new CBS folder.

 

[frg]

• Download the attached SFCFix.zip and save it on your Desktop.

Hello again

Sorry, I can't see any attached files on your previous message...

 

[DR M]

OUPSSS!!! I did it again!!!

Apologies. Here it is.

 

[frg]

OUPSSS!!! I did it again!!!

Apologies. Here it is.

Thanks

I have downloaded the file and I'll try to run SFCFIX with it and post back with the results/logs as soon as possible.

Thanks you for your time helping me.

 

[frg]

Hello again

It seems it has improved after the last SFCFix repair. DISM has failed again with the same error message, but it ran up to 32% (previously, it failed at 6%).

I have attached the screen captures and the current CBS log (The CBS persist log is the same that was in the previous message). You didn't ask for the DISM log and COMPONENTS store, but I attached them too, just in case they may be useful to you. If you need any other file, just tell me.

Thank you

 

[DR M]

Hi, frg.

Moving on.


1. SFCFix

Please do the following:

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Download the attached SFCFix.zip and save it on your Desktop.
• Save any work you have open, and close all programs.
• Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
  
  
  
  
  
  
• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Attach that file to your next reply.

2. DISM/CBS

Run DISM command and attach the screenshot of the result. If it fails, attach a new CBS folder.


P.S. I don't need anything else to attach.

 

[DR M]

Hi, frg.

Are you still with us?

 

[frg]

Hello again,

Sorry for the delay... There was a ton of work on Monday and Tuesday and couldn't run the fix until yesterday night...

It seems it has improved again with the last SFCFix repair. DISM has failed again with the same error message, it ran up to 32%, but taking a peek at the end of CBS.log, it seems it's a different file, so there has been an improvement

I have attached the screen capture, the SFCFix.log and the current CBS log (other logs in the CBS folder have not changed).

Just a question: can I somehow check how this file corruption happened on first place, so it can be prevented in the future? I'm just curious about how it could happen, as this Windows installation was just upgraded from 2004 to 21H2 (using the Media Creation Tool, not an enablement pack with Windows Update), so that kind of upgrade should clear any files corruption, shouldn't it? Maybe the first updates that Windows Update tried to install failed somehow...?

Thanks again for your time and your help

 

[DR M]

Hi, frg.

Yes, it's a new file this time and it seems that a number of rounds of fixing will be needing.

I'll be back to you soon. :)

 

[frg]

Yes, it's a new file this time and it seems that a number of rounds of fixing will be needing.

No worries, it's not a problem if it takes some rounds. Because DISM signals the corrupted files one by one (probably due to that 4448 error), I suppose there is no other way do this. So let's keep going, if you think it's ok :)

Thanks :)

 

[DR M]

Hi, frg!

Thanks for your patience.

Moving on to the next step.


1. SFCFix

Please do the following:

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Download the attached SFCFix.zip and save it on your Desktop.
• Save any work you have open, and close all programs.
• Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
  
  
  
  
  
  
• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Attach that file to your next reply.

2. DISM/CBS

Run DISM command and attach the screenshot of the result. If it fails, attach a new CBS folder.


P.S. I don't need anything else to attach.

 

[frg]

Hello again

It seems DISM has run a bit farther than before, but still fails with the same error message.

Thanks :)