[SOLVED] Can't in-place upgrade Win10 (0x800700C1), SFC and DISM failing

[dfx]

Hello - I've been trying to solve this issue for the past few days now without much success - searching similar cases here but not seeing one with exactly the same logs as me. Hoping you good folks can help. I wanted to get this machine up-to-date with most current windows updates but it's been stuck on trying to update to 22H2 for a while now.

I tried an in-place upgrade from an ISO setup to go from 1909 build 18363.1316 to 22H2 which has failed with 0x800700C1 in the setuperr log attached.

I've tried running sfc /scannow and that's failing with "Windows Resource Protection could not start the repair service". Checking CBS logs, all I see is " Failed to create CBS worker, crashed? [HRESULT = 0x80070570]".

I've tried DISM /online /cleanup-image /RestoreHealth and it fails with "Error: 1392 The file or directory is corrupted and unreadable." I've attached DISM logs as well.

I've tried ComponentScanner and it came back with no errors but some warnings (likely from me running SFC fixes not meant to run on my machine). I've attached the log for that too.

I also tried chkdsk and it came back clean.

Any help is appreciated - happy to send over any additional logs if you need

 

[Maxstar]

Hi and welcome to Sysnative,

Download the

Farbar Recovery Scan Tool and save it to your Desktop:

Download the 64 bit version: - Farbar Recovery Scan Tool Link

• Download the attachment fixlist.txt and save it to your desktop.
• Right-click on FRST.exe and select "Run as administrator".
• Press the Fix button.
• If for some reason the tool needs a restart, please make sure you let the system restart normally.
• When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
• Post the logfile Fixlog.txt as attachment in your next reply.

 

[dfx]

Thanks! Fixlog attached. I also attached farbar scan logs in case you need them.

 

[Maxstar]

Hi,

Here's the first fix.

Step 1. Download

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.

• 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.

DISM /online /cleanup-image /RestoreHealth

 

[dfx]

Wow! DISM actually ran to 100% this time. I attached the sfcfix logs. I ran sfc /scannow but it ran into files it can't fix.

C:\Windows\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

Attaching CBS and DISM logs

I'm attempting to redownload and install 22H2 from Windows Update now

 

[dfx]

Looks like that resolved the most difficult part and the machine is now on 22H2 - thank you! How does the servicing stack get corrupted? Did WU just do that on its own?

It is now failing on security update KB5034441 with error 0x80070643. A search suggests that I need to increase the recovery partition size in order to resolve - is this true? I've attached the latest CBS logs

 

[Maxstar]

Hi,

There are several reasons for these kind of corruptions, like connectivity issues, power cycle failures, forced shutdowns, system crashes, harddrive or memory corruptions. Allthough is difficult to ascertain what the exact cause was.

Yes, for KB5034441 you'll need to resize the WinRE partition using these intsructions. If you are not using Bitlocker you can also hide this update.

 

[dfx]

I ended up resizing the partition and that allowed the update to go through. Everything is up-to-date now. Thanks again!

 

[Maxstar]

You're welcome. Glad to hear everything is up-to-date now....