[SOLVED] Windows Update, SFC and DISM all fail

[VelvetMonkey]

My windows update suddenly stopped working several months ago, and in trying to investigate and fix the issue I have discovered that this also extends to sfc and dism operations.

This amazing forum appeared in my googling, as my symptoms and error messages and log file contents appear virtually identical to a previous post which was solved (here, and in fact to many similar posts).

When I run sfc / scannow I get:

C:\Windows\system32>sfc /scannow

Windows Resource Protection could not start the repair service.

When I run dism /Online /Cleanup-Image /RestoreHealth I get:

C:\Windows\system32>dism /Online /Cleanup-Image /restoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19045.2965


Error: 193

%1 is not a valid Win32 application.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Following the error logs I end up with the following in CBS.log

Failed to load Core DLL from path: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.3025_none_7e36ee127c6f13fc\\cbscore.dll [HRESULT = 0x800700c1 - ERROR_BAD_EXE_FORMAT]

Suspecting some form of corruption in dism and related libraries, I tried booting from the latest Win10 bootable USB installation media, <shift>F10 to open a cmd window, and running a version dism from the 'clean' USB source, specifying /Image to be my PCs C: drive, and /Source to be the .esd or the .wim file from the installation media. This didn't work either, as dism then complained it didn't recognise the /cleanup-image switch (despite /? suggesting it was valid)

Hoping you'll be able to suggest a fix for this. I'm not over-keen on doing a fresh install and then finding and re-installing all the s/w, data, and updates that would lose.

 

[Maxstar]

Hi and welcome to Sysnative,

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

 

[VelvetMonkey]

Microsoft Windows [Version 10.0.19045.2965]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\system32>DISM /online /cleanup-image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19045.2965

[===========================84.9%================= ]
[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Windows\system32>

Great, so far so good, that seems to have worked! MANY THANKS!

I see you replaced the contents of that specific 'servicingstack' directory... any idea which file was 'corrupt' and how that might have happened? It would be useful for trying to avoid the same in the future, as this seems to be quite a common issue. And where did you get the files from - are they supplied by Microsoft?

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 and successfully repaired 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.

Windows update is running as I type. There are quite a few updates to process. I'll let you know if there are any further issues

Many thanks once again, what a fantastic service you offer.

 

[Maxstar]

That's great news!

1. Yes, I've replaced the current Servicing Stack directory with a known good copy. It seems cbscore.dll was corrupted, but possibly other files as well.
2. There are several reasons for these kind of corruptions: connectivity and power cycle issues, forced shutdowns, system crashes, etc. However it is always difficult to ascertain what the exact cause was.
3. Back in 2020 Microsoft has changed their of Servicing Stack deployment, but nowadays an Servicing Stack Update is a part of the Cumulative Update each month.

Let me know the result, if there are still some issue please provide the latest CBS logs.

 

[VelvetMonkey]

After several reboots and update sessions I think its all done. Now on latest windows update (I assume, 19045.4651?)

Next steps: complete maintenance (as per one of your tutorials) and then create full backup/restore point....

 

[Maxstar]

Hi,

Yes, 19045.4651 is the latest LCU from this month, so if everything is up and running we can mark this thread as solved...