Using dism & sfc with errors

Question

@Docs
I was advised to create a new thread for my issues trying to repair a hybrid mbr/uefi installation of Windows 10 updated up to 21H1 through windows update.

Windows in this scenario will not allow an in place upgrade using windows 21H1 setup iso giving the usual lame reason of unusual uefi configuration.

All the Dism advice to fix Windows 10 21H1 failed for me apart from these two used consecutively:

dism.exe /Online /Cleanup-Image /AnalyzeComponentStore

dism.exe /Online /Cleanup-Image /StartComponentCleanup

Running
sfc /scannow I get
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.

Background - cloned a mbr with uefi bootloader from a sata hard disk to a sata ssd disk, had to do some adjusting so bootloader works with bcdboot command line after creating a fat32 esp partition.

Docs-4663 advised me to do this -

In the new thread post images or share links (one drive, drop box, or google drive) with these commands and results:

sfc /scannow
dism /online /cleanup-image /scanhealth
dism /online /cleanup-image /restorehealth
sfc /scannow

so since I did
sfc /scannow

I will complete with the rest i.e.
dism /online /cleanup-image /scanhealth
dism /online /cleanup-image /restorehealth
sfc /scannow

--- to be filled with results below... ---

C:\windows\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19043.1237

[==========================100.0%==========================] The component store is repairable.
The operation completed successfully.

C:\windows\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19043.1237

[==========================100.0%==========================]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see https://go.microsoft.com/fwlink/?LinkId=243077.

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

---

So the question is where is the source file - I did change the policy so it will use windows update as source, but it does not seem to comply...

since the last command failed, is there a point in running sfc / scannow again?

Answer 1

Finally - October 12, 2021—KB5006670 (OS Builds 19041.1288, 19042.1288, and 19043.1288)
Some update files are missing or have problems. We'll try to download the update again later. Error code: (0x80073712).

System successfully updated to KB5006670 on 22/10/2021.

I believe the repair package by Tweaking.com cleaned & repaired Windows Update for me.

Next step - I will clone this installation to an SSD so I can run it on other more powerful compatible PCs whilst keeping all the features & settings of my main PC - which btw is not compatible with Windows 11, & no sorry I won't pay for yet another PC for the "privilege" to use Windows 11.
The older cloned SSD I formatted because its installation was beyond repair.

cc @Docs

Answer 2

Finally - October 12, 2021—KB5006670 (OS Builds 19041.1288, 19042.1288, and 19043.1288)
Some update files are missing or have problems. We'll try to download the update again later. Error code: (0x80073712).
System successfully updated to KB5006670 on 22/10/2021.
I believe the repair package by Tweaking.com cleaned & repaired Windows Update for me.

It is not wise to use a compromised system I know, I am still unable to update to the critical update
October 12, 2021—KB5006670 (OS Builds 19041.1288, 19042.1288, and 19043.1288)
Some update files are missing or have problems. We'll try to download the update again later. Error code: (0x80073712).
Despite all my efforts & trials I could not get the system to correct the issue with Windows Update that keeps making the install of this security update to fail.
I will have to rely on Malwarebytes to hopefully protect my system as Microsoft Windows can't.

Answer 3

Well, the hard work I put in & some money I spent purchasing the repair package by Tweaking.com bore its fruit, with 21H1 results on the cloned image (the original it is based on is on my main less powerful PC which is still on 20H2)

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

C:\windows\system32>DISM /Online /Cleanup-Image /StartComponentCleanup

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19043.1288

[===== 10.0% ]
[==========================100.0%==========================]
The operation completed successfully.

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 did not find any integrity violations.

C:\windows\system32>DISM /Online /Cleanup-Image /AnalyzeComponentStore

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19043.1288

[==========================100.0%==========================]

Component Store (WinSxS) information:

Windows Explorer Reported Size of Component Store : 10.87 GB

Actual Size of Component Store : 10.55 GB

Shared with Windows : 5.50 GB
Backups and Disabled Features : 5.04 GB
Cache and Temporary Data :  0 bytes

Date of Last Cleanup : 2021-10-26 01:34:49

Number of Reclaimable Packages : 0
Component Store Cleanup Recommended : No

The operation completed successfully.

C:\windows\system32>

I am glad as this system has over 20 years worth of tinkering, since Windows 2000 in fact ;)
I lost some stuff with the previous clone which I accidentally formatted, but I can't remember what so it must be unimportant ;)

Answer 4

Again corruption occurred which I had to correct using the above listed tools - this is the exhibit outputs as of 16 Jan 2022

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

C:\Windows\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19044.1466

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

C:\Windows\system32>DISM /Online /Cleanup-Image /AnalyzeComponentStore

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19044.1466

[==========================100.0%==========================]

Component Store (WinSxS) information:

Windows Explorer Reported Size of Component Store : 13.95 GB

Actual Size of Component Store : 12.92 GB

Shared with Windows : 5.73 GB
Backups and Disabled Features : 6.66 GB
Cache and Temporary Data : 521.49 MB

Date of Last Cleanup : 2022-01-14 13:57:20

Number of Reclaimable Packages : 3
Component Store Cleanup Recommended : Yes

The operation completed successfully.

C:\Windows\system32>
C:\Windows\system32>DISM /Online /Cleanup-Image /StartComponentCleanup

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19044.1466

[===== 10.0% ]
[==========================100.0%==========================]
The operation completed successfully.

C:\Windows\system32>DISM /Online /Cleanup-Image /AnalyzeComponentStore

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19044.1466

[==========================100.0%==========================]

Component Store (WinSxS) information:

Windows Explorer Reported Size of Component Store : 11.37 GB

Actual Size of Component Store : 10.99 GB

Shared with Windows : 5.71 GB
Backups and Disabled Features : 5.27 GB
Cache and Temporary Data :  0 bytes

Date of Last Cleanup : 2022-01-15 22:01:15

Number of Reclaimable Packages : 0
Component Store Cleanup Recommended : No

The operation completed successfully.

C:\Windows\system32>