[RESOLVED] DISM "error 0x800f081f The source files could not be found" even with correct ISO and path

<Updated edit July 8, 2016>

This has been resolved, see solution below.

I resolved this by downloading the Windows 10 ISO from the Microsoft Tech Bench Upgrade Program and using that as the source for the DISM command - see my post further below. 
I'm unable to mark this as the answer because I was also the Original Poster but it solved my issues.

<end edit>

<Original Post>

I can't seem to run SFC or DISM to repair the computer, althought I've tried quite a few avenues to fix it already (see below).

Note: All commands are being performed as administrator.

The PC has a clean installl (reformatted and installed post upgrade from Win8.1) of Windows 10 (version 1511, build 10586.104). It has recently started having some problems and blue screens (not virus or malware related).

When I run sfc /scannow (as admin) the corruptions cannot be repaired.

Tried to run:

Dism /Online /Cleanup-Image /RestoreHealth

But get following error:

Error: 0x800f081f

The source files could not be found.

Ran Dism /Online /Cleanup-Image /CheckHealth and get following result:

Deployment Image Servicing and Management tool
Version: 10.0.10586.0

Image Version: 10.0.10586.0

The component store is repairable.
The operation completed successfully.

Downloaded Windows 10 ISO (using Media Creation tool) and mounted it (to E:\) then tried to run:

Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:E:\Sources\Install.wim:1 /limitaccess

But get the same error:

Error: 0x800f081f

The source files could not be found.

Attached the USB key (that was used for the install) with Windows 10 on it (connected as I:\) and tried to run:

Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:I:\Sources\Install.esd:1 /limitaccess

But get the same error:

Error: 0x800f081f

The source files could not be found.

I also mounted the original ISO that I downloaded (sometime late last year) and tried using that as the source but also got the same error.

I followed the advice of some other posts to launch the Windows 10 installer and "refresh" (aka reinstall or upgrade) Windows 10 (choosing the option to keep all existing files and apps). But even after completing the refresh process, I get the same errors trying to run SFC or DISM commands.

I have also tried resetting the windows update components using the following:

net stop wuauserv
cd %systemroot%\SoftwareDistribution
ren Download Download.old
net start wuauserv
net stop bits
net start bits
net stop cryptsvccd %systemroot%\system32
ren catroot2 catroot2.old
net start cryptsvc 

Then tried running the DISM again, but still get the same error as above.

Am running a relatively new Samsung 850 Pro SSD (with latest firmware) with 15% overprovisioning. I decided to run chkdsk just to be sure and there are no errors.

Tried DISM and SFC again but same errors witth those.

Have read a bunch of threads, MS KB articles and MS Support articles and none of it has helped. I see a LOT of people with similar problems. This is ridiculously bad and wasting a lot of time for a lot of people. Microsoft need to resolve this problem.

And I'd really like some help to get a solution for my issue now as no matter what I do, I can't seem to get this repaired.

 

Question Info


Last updated August 20, 2019 Views 38,308 Applies to:

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

You are running a 10586.0 image and your OS is 10586.104  there are files on 104 that are not on the .0 image.

What is the underlying issue that prompted you to run SFC/DISM?

If you are still crashing upload the DMP files

Cat herder
Windows Insider MVP
MVP-Windows and Devices for IT
http://www.zigzag3143.com/

7 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hey ZigZag3143,

Thanks.

You mention that I'm running a 10586.0 image. Do you mean the ISO that I'm using for the DISM source is 10586.0?

If so,  how do I get the current image.  I did just download a new ISO today. 

The problems are blue screens, sometimes PC won't shutdown (hangs saying shutting down or restarting) and sometimes insanely slow performance.

I can upload dump files, but I'd also like to know how I can successfully run DISM?

And why refreshing my Win10 install didn't fix SFC or DISM? 

The guidance from Microsoft on these seems to be lacking, especially given there importance. 

4 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Yes the mounted image (as shown in your snip) is 10586.0  There is no ISO for 10586.104 because Microsoft only publishes the zero level ISO, and the updates are done via windows updates called cumulative updates.

SFC only scans the system files and compares them to the stored backup (winsxs folder)  Dism repairs the system files.  Neither will help with freezing & BSODS.

There are other tools for diagnosing startup/shutdown issues, and for BSODS.

Cat herder
Windows Insider MVP
MVP-Windows and Devices for IT
http://www.zigzag3143.com/

2 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Thanks for the speedy responses ZigZag3143.

I'm somewhat confused.

1. What's the point of DISM if it doesn't work once you've upgraded past the base level ISO?

2. Both SFC and DISM report error that need to be repaired, but can't be. How do I repair these then?  

3. What tools would you suggest I use to troubleshoot the BSOD and shutdown issues?

3 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

1-In most cases if there is an OS problem the files are the same.

2-Depends on the errors

3-For start/shutdown I would run a windows performance recorder trace.  For BSOD'S upload the dumps

In order to diagnose your problem we need to run Windows performance toolkit the instructions for which can be found in this wiki


If you have any questions feel free to ask

Please run the trace when you are experiencing the problem

Cat herder
Windows Insider MVP
MVP-Windows and Devices for IT
http://www.zigzag3143.com/

2 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Thanks for the links. I'll follow up on that.

Just some feedback on running conflicting versions of DISM. I still don't understand why DISM wouldn't work with prior versions... that just doesn't make sense to design a tool that way. As soon as an update is released the tool becomes useless.

So, as a last resort (and not entirely trusting your comment about version matching, because of my logic above) I downloaded the Tech Bench Upgrade Program ISO, mounted it as F:\ drive and ran the same DISM command:

Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:F:\Sources\Install.wim:1 /limitaccess

But this time I got the result I was looking for:

Deployment Image Servicing and Management tool
Version: 10.0.10586.0

Image Version: 10.0.10586.0

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

The restore operation completed successfully.

The operation completed successfully.

A subsequent check health command (dism /online /cleanup-image /checkhealth) reports an improved component store:

Deployment Image Servicing and Management tool

Version: 10.0.10586.0
Image Version: 10.0.10586.0
No component store corruption detected.
The operation completed successfully.

The image version of the Tech Bench ISO is the same as the one I was using previously (10.0.10586.0) and your belief seems to be that it's because the image version of the ISO doesn't match the version of Windows 10 (build 10586.104) that causes DISM to give the error. So how has DISM managed to repair the errors this time?

7 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

And further, after the successful repairing with DISM using the Tech Bench ISO, I can now also run SFC /scannow and get a successful repair:h

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.

Now I'm not saying that this will fix the BSOD and shutdown issues, but the Tech Bench ISO has certainly allowed these two tools to work as intended. And it appears to be the same version as every other ISO I've previously tried.

So why does that work when other ISOs don't?

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Simple, when the files are present SFC/DISM repairs the differences, when the files are not present it says sources not found.  Obviously what it successfully repaired this time was different.

If one wanted they could examine the log file (CBS.LOG) generated by SFC to find out what could not be fixed but frankly I dont have the time.

If you continue to experience SFC/DISM errors it may point to a hardware issue (HD)

Cat herder
Windows Insider MVP
MVP-Windows and Devices for IT
http://www.zigzag3143.com/

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I understand why SFC works post DISM.

But that's not a logical answer for why DISM worked with the Tech Bench ISO. Your response doesn't justify why DISM worked with the Tech Bench ISO and why it didn't with all other previous Windows 10 ISOs, even though DISM still shows the version number as being 10.0.10586.0 and I'm running build 10586.104.

Nothing had changed on my system between using the previous ISO and the Tech Bench ISO (it hadn't even been restarted until AFTER running DISM using the Tech Bench ISO).


3 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

You seem to be more fixated of the why's OF SFC/DISM than fixing the problem.  I did explain why to the best of my ability.

Cat herder
Windows Insider MVP
MVP-Windows and Devices for IT
http://www.zigzag3143.com/

8 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.