Windows 10: DISM Source files could not be found, sfc /scannow found corrupt files

Custom build for a friend.
OS: Windows 10 Pro, 64-bit
MB: MSI Z170-A Pro
Graphics Card: GeForce GTX 680
CPU: Intel i5 6600K @ 3.50GHz
RAM: 8g

Installed OS through bootable USB, as the build has no CD drive.

On completion of build I had some driver issues which were causing occasional BSoD - however on reading the logs and searching the internet, I finally decided to update to Mobo to the latest driver.
This solved all the issues, and the PC is now running like a dream.

However, on doing a routine scan of sfc /scannow it found corrupt files, but weren't able to fix them.
So I tried "Dism /Online /Cleanup-Image /RestoreHealth", this resulted in:
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 Configure a Windows Repair Source.

So I downloaded the Media Creation Tool and made an ISO, mounted it as a virtual drive and did "Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:G:\sources\install.wim:1 /limitaccess"

Same error code, same description - this is because the ISO from the MCT has the file install.esd instead of install.wim
Looking around, I was unable to find the TechBench download which supposedly had the correct files, all the links I found lead to dead ends.
Example: https://www.microsoft.com/en-us/soft...load/techbench
Leads to: https://www.microsoft.com/library/er...marterror.aspx

Has it been moved, or am I just blind?

The PC runs without fault, but I'd hate to hand the PC over, only for him to run into issues down the road due to something I failed to fix.

:)

 

Cannot sign-in with PIN code

sfc/scannow found no faults, DISM reported source file could not be found

 

Repeated SFC Failures; DISM Says It Can't Find Install Image That's in the DVD Drive

Repeated uses of sfc /scannow, with reboots, produce identical reports that corrupt but unfixable files exist.

This elevated command: "DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:E:\Sources\Install.wim:1 /LimitAccess", where E: is the drive containing the ISO used to install the system (10 Pro), produces this:

"Error: 0x800f081f

The source files could not be found."

Why is DISM reporting it cannot find the source image?

Why is sfc /scannow failing repeatedly?

What is the correct way to use these tools to eliminate file corruption reported by sfc?

 

You can use an ESD file, and the corresponding DISM command is

Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:H:\sources\install.esd:1 /limitaccess

The ISO file and the Windows on your system must match. You can determine the ISO version using the following command:

dism /Get-WimInfo /WimFile:H:\sources\install.esd /index:1

where H is the mounted drive for the ISO.

See also: https://www.tenforums.com/tutorials/...html#option1s7

 

you should also delete windows\logs\dism\dism.log prior to running command
then read the dism.log after running the command to determine the files causing corruption issue

Or use Image-Health (link also in sig below)
Windows 10 Recovery Tools - Bootable Rescue Disk

 

Thank you both!
Using the ESD file still gives the following error.

C:\Windows\system32>Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:H:\sources\install.esd:1 /limitaccessDeployment Image Servicing and Management toolVersion: 10.0.14393.0Image Version: 10.0.14393.0[===========================86.6%================== ]Error: 0x800f081fThe 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 MSN France: Hotmail, Outlook, actualités, météo, divertissement DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Looking through the dism.log the following errors were encountered:

2017-02-14 21:35:50, Warning DISM DISM OS Provider: PID=5308 TID=7200 Unable to set the DLL search path to the servicing stack folder. C:\Windows may not point to a valid Windows folder. - CDISMOSServiceManager::Final_OnConnect

2017-02-14 21:35:50, Warning DISM DISM Provider Store: PID=5308 TID=7200 Failed to Load the provider: C:\Users\Mikkel\AppData\Local\Temp\812DDDE9-0868-4FA6-B263-869A6E4D56AE\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

2017-02-14 21:35:50, Warning DISM DISM Provider Store: PID=5308 TID=7200 Failed to Load the provider: C:\Users\Mikkel\AppData\Local\Temp\812DDDE9-0868-4FA6-B263-869A6E4D56AE\EmbeddedProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

2017-02-14 21:35:52, Warning DISM DISM Package Manager: PID=5308 TID=7200 CBS AddSource failed with HRESULT=0x8007007b! - CDISMPackageManager::Internal_Finalize


2017-02-14 21:38:12, Error DISM DISM Package Manager: PID=5308 TID=7200 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f081f)2017-02-14 21:38:12, Error DISM DISM Package Manager: PID=5308 TID=7200 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg2017-02-14 21:38:12, Error DISM DISM Package Manager: PID=5308 TID=7200 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f081f)2017-02-14 21:38:12, Error DISM DISM Package Manager: PID=5308 TID=7200 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg2017-02-14 21:38:12, Error DISM DISM Package Manager: PID=5308 TID=7200 Failed to restore the image health. - CPackageManagerCLIHandler:rocessCmdLine_CleanupImage(hr:0x800f081f)2017-02-14 21:38:12, Error DISM DISM Package Manager: PID=5308 TID=7200 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)

I'll give Image-Health a shot tomorrow, thank you both for the suggestions.

 

Did you make sure the ISO and your Windows are the same version? This sounds like they may not be. Just sayin'

 

Hi,

That plus DISM really does not work well if at all with .ESD files. I'd try with a .WIM file of the correct version and language instead .

Cheers, *Wink

 

Yes, I realized I was using a wrong version of the ISO, after about two cups of coffee and an hour of intense staring at the screen.
Turns out I was just being blind and overthinking the problem. *Rolleyes

Anyway, using the correct ISO magically solved all the 'weird' issues I were facing.
Thank you all for your swift and on-point advice!

 

Glad it worked ... you are most welcome.

 

It will work fine with the Install.esd from the MCT if you give the correct index number for the source image file.

However, unless you look inside the install.esd, it is difficult to know how the file is arranged.

At a guess, the correct syntax is probably:

C:\Windows\system32>Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:H:\sources\install.esd:4 /limitaccess

but without checking the specific install.esd, it could be different.

Install.wim files also can contain multiple indexed images, and may fail in the same way.


See here: Windows 10 ISO Download

If you use 7-zip to open the image you will see what it contains and the [1].xml will detail the index numbers for the image you want to use as source.

 

That's some interesting information and explains my past difficulties using an ESD file. I always assumed the index was 1 because that's all you normally see in examples of the command. Thanks ...