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

In the previous comment I wrote The End, but it is far from it.
Now the latest major security upgrade would not install
windows10.0-kb5006670-x64_51b78c3627885149a65b09dc92a936935017ff58
KB5006670 (~ 617MB) from either the normal upgrade rout or manually running the msu.

I can still get into safe mode, or normal mode, but there are still issues.

In the original installation on an Asus PC, sfc / scannow managed to correct corrupt files.
However on the cloned version using another computer it wouldn't.

Why am I so insistent in doing this, well I am retired with diability, & this makes me not stay idle, or do passive activities.

I have ben using Microsoft since DOS, Windows 3, 3.1, 95, 98, Millenium, NT 3.5, NT4, 2000, XP, up to the latest now, & I enjoy debugging them at my novice level.

So, I will look into the advice of MVP community advice expert @Docs & try to find out which files are corrupt from the log as he showed me.

Answer 3

Still struggling, after managing to correct system using sfc /scannow, now it is unable to update with KB5006670 giving error: 0x800f0831

This is getting very irritating, with updates creating problems instead of solving them.

Maybe I should come back to Linux, at least it is more manageable.

anyways ...

cc @Docs

I have used in safe mode
Tweaking.com - Windows Repair 2021 (v4.11.7) - Pre-Scan

│ Scanning Windows Packages Files.
│ Started at (14/10/2021 23:20:24)
│
│ These Files Are Possibly Corrupt (Bad Digital Signature): (Total: 5)
C:\windows\servicing\Packages\Microsoft-Windows-Client-Desktop-Required-Package0512~31bf3856ad364e35~amd64~~10.0.19041.1237.cat
C:\windows\servicing\Packages\HyperV-UX-UI-62-Package~31bf3856ad364e35~amd64~~10.0.19041.1237.mum
C:\windows\servicing\Packages\Microsoft-Windows-Client-Desktop-Required-Package0512~31bf3856ad364e35~amd64~~10.0.19041.1237.mum
C:\windows\servicing\Packages\Microsoft-Windows-Client-Desktop-Required-Package0519~31bf3856ad364e35~amd64~~10.0.19041.1237.mum
C:\windows\servicing\Packages\Package_2_for_KB5000736~31bf3856ad364e35~amd64~~10.0.1.3.mum
│
5 Combined Problems were found with the packages files, these files need to be replaced (These mainly only effect installing Windows Updates.)
│ The SFC (System File Checker) doesn't scan and replace some of these files, so you may need to replace them manually.
│
│ THESE FILES DO NOT KEEP THE REPAIRS FROM WORKING; YOU MAY STILL RUN THE REPAIRS IN THE PROGRAM.
│
│ Files Checked & Verified: 2,966
│
│ Done Scanning Windows Packages Files.(14/10/2021 23:28:21)
└─
It does not say how or where I can get these files, they might be the reason why I am no longer able to upgrade or update Windows 10.

Answer 4

cc @Docs

I have used in safe mode
Tweaking.com - Windows Repair 2021 (v4.11.7) - Pre-Scan

│ Scanning Windows Packages Files.
│ Started at (14/10/2021 23:20:24)
│
│ These Files Are Possibly Corrupt (Bad Digital Signature): (Total: 5)
C:\windows\servicing\Packages\Microsoft-Windows-Client-Desktop-Required-Package0512~31bf3856ad364e35~amd64~~10.0.19041.1237.cat
C:\windows\servicing\Packages\HyperV-UX-UI-62-Package~31bf3856ad364e35~amd64~~10.0.19041.1237.mum
C:\windows\servicing\Packages\Microsoft-Windows-Client-Desktop-Required-Package0512~31bf3856ad364e35~amd64~~10.0.19041.1237.mum
C:\windows\servicing\Packages\Microsoft-Windows-Client-Desktop-Required-Package0519~31bf3856ad364e35~amd64~~10.0.19041.1237.mum
C:\windows\servicing\Packages\Package_2_for_KB5000736~31bf3856ad364e35~amd64~~10.0.1.3.mum
│
5 Combined Problems were found with the packages files, these files need to be replaced (These mainly only effect installing Windows Updates.)
│ The SFC (System File Checker) doesn't scan and replace some of these files, so you may need to replace them manually.
│
│ THESE FILES DO NOT KEEP THE REPAIRS FROM WORKING; YOU MAY STILL RUN THE REPAIRS IN THE PROGRAM.
│
│ Files Checked & Verified: 2,966
│
│ Done Scanning Windows Packages Files.(14/10/2021 23:28:21)
└─
It does not say how or where I can get these files, they might be the reason why I am no longer able to upgrade or update Windows 10.

Answer 5

Windows Updates 21Hx are the disasters that keep giving.

It seems the core enablement activation package is the culprit.

I made the mistake of using it, now neither Dism nor sfc attempt at rescue work...

Details sourced to:

Feature Update to Windows10 21H1 via Enablement Package (KB5000736)
&
Servicing Stack 10.0.19041.1220

I should have stuck to 20H2 as moving from 20H2 to 21H1 through KB5000736 seems to have corrupted Windows Update capability.

I am trying to rescue my Windows 10 because of the configs & settings worth about 20 years work.

From scratch it works flawlessly as I tested on other PCs from install to upgrades, but on older systems it is poorly implemented by Microsoft.

Dism does not perform adequately even when it very oddly says the image is repairable.
sfc gives the cryptic statement cannot repair some corrupt files...

I will hold to my Windows 10 faulty install, & will use other newer installs for mission critical tasks.

Overall very disappointed with a platform I have been using for many years since DOS & Windows 3.1.

After many passes, finally sfc gives no errors:
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.

Also I uninstalled KB5000736 & am now back on 20H2.
I think I will leave it at that, the difference between 20H2 & 21H1 seems to be cosmetic, but 21H1 gives me problems.
cc @Docs