Windows 10 DISM Error - Source Files Not Found

The command line is DISM /Online /Cleanup-Image /RestoreHealth /Source:c:\w10x64\sources\install.wim /LimitAccess

It fails with error 0x800f081f  The source files could not be found. The install.wim is verified as being there. I somehow think the error is not accurate. Any ideas?

This particular computer was one of 10 I upgraded abot three weeks ago and I have a feeling they would all probably fail with the same error.....
LVL 15
LockDown32OwnerAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
LockDown32Connect With a Mentor OwnerAuthor Commented:
Your post was not incoherent. The thread you posted a link to was incoherent.

My Windows is fine but I need to be in a position to support my customers. You look through a lot of these posts about Windows 10 problems and more times then not the recommendation is to run sfc followed by dism if sfc reports corruption.

Anyway... I read enough posts that I mace across a fix. Several specific things need to be done:

1) Download the ISO from Tech Bench. The ISO created with the Windows Media Creation Tool will not work. It is a esd and supposedly only a wim will work.

2) The ISO needs to be mounted. Technically mounted. Copying the files somewhere and running DISM specifying where you copied them doesn't seem to work.

Those two items did the trick. There were several suggestion like case sensitivity, preceding the restorehealth  with other DISM commands and others but just doing #1 and #2 seemed to work. DISM ram.
0
 
JohnBusiness Consultant (Owner)Commented:
DISM goes out of date with new builds for Windows 10. I have not found any way to keep it current.

Here is a Ten Forums post with methods to update DISM.

http://www.tenforums.com/performance-maintenance/23654-error-dism-restorehealth-5.html

I have found the update to DISM not worth the effort. The Windows 10 build number change every month.

I do not know if the next version of Windows 10 (due out in a couple of weeks) will fix this.

At this point, I fix major issues with the Windows 10 Repair Install from the Media Creation Link and Keep Everything.
0
 
awawadaCommented:
If you are using a third party security software, try to uninstall it temporary, after start in a Clean Boot under Windows 10 and check DISM again.

https://windowsinstructed.com/clean-boot-windows-windows/
0
Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

 
LockDown32OwnerAuthor Commented:
Unloading the virus software did not help. John that like was incoherent. People jumping in late and no real solution or did I miss something?

The one thing that was always mentioned what that the Image Version had to match the Windows Version. When you run DISM the first two things you see on the screen are:

DISM 10.0.10586.0 (That is the version of DISM isn't it? and in-turn the version of Windows?)

Image Version 10.0.10586 (That must be the version if the install.wim being used)

and just for grins I opened a command prompt and type "ver". Cam back with Microsoft Windows 10.0.10586

so... it looks like the versions are the same all the way down the line no?
0
 
JohnBusiness Consultant (Owner)Commented:
I opened a command prompt and type "ver".

Winkey + R winver gives a better result.

John that like was incoherent  <-- what was incoherent in my post ??
0
 
JohnBusiness Consultant (Owner)Commented:
My DISM (errors out like yours, but I have no problems, so do not need it) shows:

C:\>dism /?

Deployment Image Servicing and Management tool
Version: 10.0.10586.0

Winver says Build 10586.494.  

I think that is the difference.

Something may have gone wrong with DISM itself., but it would be very low priority to fix it on my machine because nothing is wrong with it
0
 
JohnBusiness Consultant (Owner)Commented:
Thank you for the above.

I had figure out the Mount issue from the DISM Log file and articles I read.

But of course that does not work with ESD files.

Your post about Tech Bench to get the correct ISO file was what I had not found.

Thanks again.
0
 
LockDown32OwnerAuthor Commented:
This is the solution
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.