LockDown32
asked on
Windows 10 DISM Error - Source Files Not Found
The command line is DISM /Online /Cleanup-Image /RestoreHealth /Source:c:\w10x64\sources\ install.wi m /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.....
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.....
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/
https://windowsinstructed.com/clean-boot-windows-windows/
ASKER
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?
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?
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 ??
Winkey + R winver gives a better result.
John that like was incoherent <-- what was incoherent in my post ??
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
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
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.
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.
ASKER
This is the solution
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.