Using dism & sfc with errors

54988485 96

@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?

Accepted answer

54988485 96 Reputation points

2021-10-22T03:18:04.293+00:00

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
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

15 additional answers

Docs 15,761 Reputation points

2021-09-29T22:52:48.503+00:00

Open disk management > by default some of the columns are compressed > widen each Volume and Status and make sure that non of the characters are cutoff > view the disk 0 row > widen the row as needed so that no characters are cutoff >post an image or share link into this thread
https://www.tenforums.com/tutorials/2503-how-post-screenshot-disk-management.html

Download and install Minitool partition wizard (free version) > click launch > post an image or share link into this thread
https://www.partitionwizard.com/

Find a flash drive that you can format ( > or = 8 GB).

Create a bootable Windows 10 iso 21H1:
https://www.tenforums.com/tutorials/9230-download-windows-10-iso-file.html
https://www.microsoft.com/en-us/software-download/windows10

List any of these installed or recently uninstalled non-Microsoft software:
a) antivirus
b) firewall
c) drive encryption

.
.
.
.
.
Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post: Vote = a helpful post
.
.
.
.
.
Please sign in to rate this answer.

1 person found this answer helpful.
54988485 96 Reputation points

2021-09-30T12:07:25.64+00:00

That looks very complex to me.
As far as firewall goes, I did indeed disable my malwarebytes one (all of it) but this didn't help.
I will go through your advice step by step & ask for the bits I can't figure out.
In the meantime there is this option to convert an mbr drive to uefi without data & without boot/settings loss - this will be my preferred option so I can do an in place upgrade, but I am concerned I will lose my installation altogether.
https://www.disk-utility.com/2021/07/convert-windows-10-from-old-bios-to.html

54988485 96 Reputation points

2021-09-30T13:55:33.657+00:00

Just as an experiment I tried to run sfc on the original HDD drive (which I cloned from to SSD as above) & the command ended successfully, it seems I either changed something after I cloned to the SSD result, or who knows...

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.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Docs 15,761 Reputation points

2021-09-30T13:39:21.873+00:00

The success and failure of an in place upgrade repair is not related to whether the BIOS is UEFI, UEFI with CSM, or Legacy BIOS.

Changing from Legacy BIOS to UEFI BIOS is independent.

It does not have to be done at this time and may add further confusion.

At a later time instruction can be posted for MBR to GPT or GPT to MBR or Legacy to UEFI or UEFI to Legacy.

.
.
.
.
.
Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post: Vote = a helpful post
.
.
.
.
.
Please sign in to rate this answer.

1 person found this answer helpful.
54988485 96 Reputation points

2021-09-30T14:45:07.113+00:00

Even though not an expert by far. I like troubleshooting & hacking operating systems within my meagre abilities, though getting old makes memory retention an issue, but tinkering with hardware/software helps me to get these misfiring neurones working ;)

Anyways, I would like to know why the original HDD works but the cloned SSD does not allow in place upgrading :)

Finally on the original HDD -

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

Deployment Image Servicing and Management tool
Version: 10.0.19041.572

Image Version: 10.0.19042.630

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

So something happened in the SSD that makes it not allow repairs or in place upgrades.

I can reclone of course & maybe this will solve it, but I have to go through the pain of repairing the bootloader, etc.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Docs 15,761 Reputation points

2021-10-01T22:20:51.773+00:00

When available please post the results from the earlier posts:

disk management
minitool partition wizard

List each: (use none if applicable)
antivirus
firewall
drive encryption

Run the V2 log collector (it was designed for BSOD and can be applied to non-BSOD problems) and post a share link into this thread using one drive, drop box, or google drive

https://www.windowsq.com/t/bsod-posting-instructions.17/
https://www.windowsq.com/resources/v2-log-collector.8/
https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

Run setupdiag > post a share link into this thread using one drive, drop box, or google drive
https://learn.microsoft.com/en-us/windows/deployment/upgrade/setupdiag

.
.
.
.
.
Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post: Vote = a helpful post
.
.
.
.
.
Please sign in to rate this answer.

1 person found this answer helpful.
54988485 96 Reputation points

2021-10-02T18:12:13.343+00:00

@Docs
I landed myself a more serious, maybe fatal problem on the HDD original version.
Maybe I need to open a new thread on this.
So I can access the cloned SSD which seems to have stabilised as I said with the latest update on top of 21H!.

On the HDD which has 20H2 with latest updates, but unable to do in place upgrade or windows update to 21H1, I ran chkdsk & rebooted to allow it to do it.

When I rebooted I could no longer login, it said that I needed to configure a new pin & could not use the facility anymore, sadly there was no other booting option (which there used to be in past versions), so I could no longer access the desktop, even in safe mode.

I made the tragic, & maybe fatal mistake to follow an advice from a few sites that said that deleting C:\Windows\ServiceProfiles\LocalService\AppData\Local\Microsoft\Ngc would help to reset the pin,

however what I didn't realise is that it assumed I could somewhat access the desktop which I can no longer do.

It was really dumb of Microsoft to remove the other login options, they make users' lives a nightmare.

I no longer have access to login now, the screen just has the welcome screen with a nice picture & if I press enter it becomes blurred but no login entry whatsoever.

How can I fix this? I scoured the web but most advice assumes one can access the desktop, or get it into safe mode, so pretty useless to me so far.

I can get a terminal prompt, but how to use that to re-access the desktop?

I might copy & paste this as a new question on the board.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
54988485 96 Reputation points

2021-10-01T10:29:51.53+00:00

I just want to add here that in place upgrade worked for me on another install with 20H2, however I had to get the latest 21H1 iso & selected not to update files before upgrading.
So overall not a seamless experience in all settings / configurations.

Also Microsoft update upgraded the 21H1 cloned on SSD, maybe this has solved the shutdown issues I had & repaired the corrupt files neither SFC nor DISM could repair.

So I would tentatively state for my intent & purpose the problem as somewhat solved.

It is unlikely I will upgrade to Windows 11, & not sure even if I can with the hardware I got.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Using dism & sfc with errors

15 additional answers

Your answer