Windows 10 Pro x64 Update failure

[dB333]

Hi guys,

I see similar posts and amazing results given what I've gone through and have nothing to show for it.

Here's the skinny:
Running Win10Pro x64 version 2004 (OS build 19041.329)

I recently noticed updates were not installing, ever since KB4571756 - Cumulative Update for Windows 10 Version 2004 for x64 based systems.

Attempted to rename/remove SoftwareDistribution and catroot2 folders, but this didn't help.

Tried using command "Dism /Online /Cleanup-Image /RestoreHealth" but that failed, I'm thinking for the same reason that Wupdate fails.

Out of desperation, reset the network config using netsh winsock reset.

Looking in CBS.log I found 64 corruptions ... mainly CBS Catalog Corrupt and CSI Manifest Corrupt. Attempting to fix yields "Manifest hash mismatch" over and over.

Can anyone make sense of this mess? I've attached the DISM.log but CBS.log is too large, so I've dropped a copy on Drive. (HERE)

Thanks in advance!

 

[dB333]

I ran SFC /scannow again not realizing this would overwrite CBS.log. On the bright side, it's much less cluttered and I've attached it in this post.

Total Detected Corruption: 64
2020-09-28 00:36:43, Info CBS CBS Manifest Corruption: 22
2020-09-28 00:36:43, Info CBS CBS Metadata Corruption: 0
2020-09-28 00:36:43, Info CBS CSI Manifest Corruption: 42
2020-09-28 00:36:43, Info CBS CSI Metadata Corruption: 0

Probably not good...

 

[dB333]

Is anyone available to help with this?

 

[dB333]

Still trying to figure this out, but I have a weird update. I checked the Update History and it turns out there are two updates that were "successfully installed", but that Windows is trying to install again and failing. One of these (KB4576754) I downloaded manually and installed. I don't see why this would matter, but giving it as detail.

I went through the same removing SoftwareDist and catroot2 folders again, and then resetting winsock, but that didn't fix it either.

I've run a chkdsk and the disk is good.

Also, I can no longer run sfc /scannow as I get the error "Windows Resource Protection could not start the repair service." I haven't found anything useful to fix that either.

I hope someone has a solution!

 

[Rich-M]

I went through a similar situation a few months ago and after trying everything I could think of I finally used System Restore back far enough
that I was able to get past this. I know that type of solution isn't helpful in terms of finding and solving the problem but since it worked and issue never came back
it was a time saver. Sometimes the "self torture" just isn't worth the effort!

 

[dB333]

I went through a similar situation a few months ago and after trying everything I could think of I finally used System Restore back far enough
that I was able to get past this. I know that type of solution isn't helpful in terms of finding and solving the problem but since it worked and issue never came back
it was a time saver. Sometimes the "self torture" just isn't worth the effort!

I tend to agree, and was inching toward that, but was still hoping beyond hope that there is a relatively simple fix!

I do appreciate the response, especially since you've run into the same thing. So frustrating!

Take care.