Error DISM restorehealth

Hello friends

I'm running crazy, trying to solve a internet Explorer not working in Windows 10. I suspected a corrupted update issue since my windows was running perfectly fine but after the last update in January 15...my IE and Skype and a lot other programs that rely on it went south!. January 15 hot fixed problems in IE related to flash.

Let me tell you guys what I have found so far :

I use the Windows ISO from techbench compatible with my current version 1511 (10.0.10586.0) and the iso is "Win10_1511_EnglishInternational_x64.iso" from:
Tech Bench

I mounted the iso and downloaded "IMAGE_HEALTH.zip" and run the .cmd file option 1 results OK, option 2 tells me to use a source but option 3 tells me i don't have the source correct:

DISM log is this (a summary):


2016-01-25 00:19:12, Info DISM DISM Package Manager: PID=5428 TID=4900 Error in operation: source for package or file not found, ResolveSource() unsuccessful. (CBS HRESULT=0x800f081f) - CCbsConUIHandler::Error
2016-01-25 00:19:12, Error DISM DISM Package Manager: PID=5428 TID=4616 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f081f)
2016-01-25 00:19:12, Error DISM DISM Package Manager: PID=5428 TID=4616 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg
2016-01-25 00:19:12, Error DISM DISM Package Manager: PID=5428 TID=4616 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f081f)
2016-01-25 00:19:12, Error DISM DISM Package Manager: PID=5428 TID=4616 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg
2016-01-25 00:19:12, Error DISM DISM Package Manager: PID=5428 TID=4616 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x800f081f)
2016-01-25 00:19:12, Error DISM DISM Package Manager: PID=5428 TID=4616 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)
2016-01-25 00:19:12, Info DISM DISM Package Manager: PID=5428 TID=4616 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine


CBS log is this (a summary):

Checking System Update Readiness.

(p) CBS Catalog Missing Microsoft-Windows-Editions-Education-Package~31bf3856ad364e35~amd64~en-US~10.0.10586.0
(p) CBS Catalog Missing Microsoft-Windows-NetJoin-ds-Package~31bf3856ad364e35~amd64~en-US~10.0.10586.0
(p) CBS Catalog Missing Microsoft-Windows-Network-Security-MPSSVC-WOW64-ds-Package~31bf3856ad364e35~amd64~en-US~10.0.10586.0
(p) CBS Catalog Missing Microsoft-Windows-PeerToPeer-Full-Package~31bf3856ad364e35~amd64~en-US~10.0.10586.0
(p) CBS Catalog Missing Microsoft-Windows-PushNotifications-Feature-WOW64-Package~31bf3856ad364e35~amd64~en-US~10.0.10586.0
(p) CBS Catalog Missing (Fixed) Microsoft-Windows-Search2-shell-Package~31bf3856ad364e35~amd64~~10.0.10586.0
(p) CBS Catalog Missing Microsoft-Windows-Settings-Package~31bf3856ad364e35~amd64~en-US~10.0.10586.0
(p) CBS Catalog Missing Microsoft-Windows-Settings-WOW64-Package~31bf3856ad364e35~amd64~en-US~10.0.10586.0
(p) CBS Catalog Corrupt Multimedia-RestrictedCodecsExt-WOW64-multimedia-Package~31bf3856ad364e35~amd64~en-US~10.0.10586.0

Summary:
Operation: Detect and Repair
Operation result: 0x800f081f
Last Successful Step: Entire operation completes.
Total Detected Corruption: 9
CBS Manifest Corruption: 9
CBS Metadata Corruption: 0
CSI Manifest Corruption: 0
CSI Metadata Corruption: 0
CSI Payload Corruption: 0
Total Repaired Corruption: 1
CBS Manifest Repaired: 1
CSI Manifest Repaired: 0
CSI Payload Repaired: 0
CSI Store Metadata refreshed: True

Total Operation Time: 186 seconds.



If I run:

DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:K:\Sources\Install.wim:1 /LimitAccess

with or without the "" is the same problem....error 0x800f081f comes up and everything is again the same.


Friends, how to solve this MS "mess" ?

I suspect that "Win10_1511_EnglishInternational_x64.iso" does not have the files for repair that DISM is looking for. Is that correct ?Dism Details.txt

Thank you guys in advance for this excellent forum.

Kyhi said:

do an in-place repair install...

run the repair source media setup.exe file from within your current OS

Dear Kyhi, thank you for your prompt help. It went smoothly following Brink's tutorial:

Repair Install Windows 10 with an In-place Upgrade - Windows 10 Forums


My last question now it's been resolved is how to maintain a cleanup local windows image in order NOT to have to recur to installation ISO. What happens if in a few days MS incorporates a new release build, then the "end user" will have to download that specific ISO ?

Thank you and all the excellent administrators of the forum.

If any of you has Avast AV and trouble fixing image, stop Avast self defence module and all 3 shields. Try fixing again. Worked for me.

I just wanted to drop my appreciation to you Kyhi for putting together and sharing this wonderful and nifty little tool with us. It's very helpful. I've spent hours looking to fix this issues but I've finally arrived at the right place. THANK YOU.:)

Hi Kyhi, I am a layman and have the same problem with Windows 10. Really not following exactly what I need to do to fix this. I upgraded from Windows 8 to 10, and I am also getting this. Thanks so much for any help you can give me. Screenshot attached.

Hi there,

I have a quick qn,

I'm also experiencing the sfc cannot repair stuff for a dll file....

2016-04-14 21:35:52, Info CSI 00004ed6 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

My question is, if I run those commands in the sequence stated, I'd like to know if that means the Surface Book is experiencing that issue will be wiped out all of its data.

May you please, clarify that?

Thank you