Windows 10: Error DISM restorehealth

Thank you Kyhi!

Now the corrupted dll seem to be fixed:
> sfc /scannow
Windows Resource Protection did not find any integrity violations.

However, I still get errors opening jpeg files. I get these errors in the event viewer:

Activation of app Microsoft.Windows.Photos_8wekyb3d8bbwe!App failed with error: The remote procedure call failed. See the Microsoft-Windows-TWinUI/Operational log for additional information.

ActivateApplicationForContractByAcidAsUserWithHost of the app Microsoft.Windows.Photos_8wekyb3d8bbwe!App for the Windows.File contract failed with The remote procedure call failed..

Activation of the app Microsoft.Windows.Photos_8wekyb3d8bbwe!App for the Windows.File contract failed with error: The remote procedure call failed..

Activation via contract helper of the app Microsoft.Windows.Photos_8wekyb3d8bbwe!App for the Windows.File contract failed with The remote procedure call failed..

Any suggestions? I can gather more information if needed.

P.S. RPC service is running and on automatic. RPC locator is not started and on manual.

Thank you in advance for the help!

Best regards,
Marin

 

Hello, i found this topic after searching the web about error 0x800f081f by DISM.
sfc /scannow finds errors and unable to fix them.
I ran IMAGE_HEALTH with Windows 10 Pro iso mounted and selected option 3.
Result is:
Code: =============================================================================== Found Source Install.wim on Drive J: =============================================================================== =============================================================================== Dism is restoring the online image health using the source Install.wim Please Wait.. This will take 10-15 minutes or more.. =============================================================================== Deployment Image Servicing and Management tool Version: 10.0.10240.16384 Image Version: 10.0.10240.16384 [==========================100.0%==========================] 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. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log Press any key to continue . . .[/quote] Content of dism.log is here: 2015-12-22 14:47:32, Info DISM PID=77184 TID=56492 Scratch di - Pastebin.com

Can you give me a direction for solving the issue?

 

Please select option 1, then option 2
Then option 0

If you have > IMAGE HEALTH - Version 12.10.2015 (if not you can download using link in my sig below)

it will place a dism.txt file on your desktop, please attach the .txt file to your reply post

 

Hello Kyhi,
Here is the report.Dism Details.txt

Edit: I found my Windows was not up-to-date.
After update option 1 prints :
No component store corruption detected.
The operation completed successfully.

 

Code: Checking System Update Readiness. (p) CSI Payload Corrupt amd64_microsoft-windows-p..erandprintui-pmcppc_31bf3856ad364e35_10.0.10240.16384_none_1368b39b1b5ef02c\Print Management.lnk (p) CSI Payload Corrupt amd64_microsoft-windows-s..ment-policytools-ex_31bf3856ad364e35_10.0.10240.16384_none_615fc74cdbc2e977\Security Configuration Management.lnk (p) CSI Payload Corrupt amd64_microsoft-windows-c..s-admin-compsvclink_31bf3856ad364e35_10.0.10240.16384_none_da92c3787526666b\Component Services.lnk (p) CSI Payload Corrupt amd64_microsoft-windows-xpsreachviewer_31bf3856ad364e35_10.0.10240.16384_none_1d1bc52ee8e4cc32\XPS Viewer.lnk (p) CSI Payload Corrupt wow64_microsoft-windows-m..-odbc-administrator_31bf3856ad364e35_10.0.10240.16384_none_56a5035f0cc518cc\ODBC Data Sources (32-bit).lnk (p) CSI Payload Corrupt amd64_networking-mpssvc_31bf3856ad364e35_10.0.10240.16384_none_1279f88853d7ed1e\Windows Firewall with Advanced Security.lnk (p) CSI Payload Corrupt amd64_microsoft-windows-t..minalservicesclient_31bf3856ad364e35_10.0.10240.16384_none_55dcbf43bbc4daa2\Remote Desktop Connection.lnk (p) CSI Payload Corrupt amd64_microsoft-windows-defrag-adminui_31bf3856ad364e35_10.0.10240.16384_none_a116806d2af23e0d\dfrgui.lnk (p) CSI Payload Corrupt amd64_microsoft-windows-m..diagnostic-schedule_31bf3856ad364e35_10.0.10240.16384_none_9bd70deb1464ceed\Memory Diagnostics Tool.lnk (p) CSI Payload Corrupt amd64_microsoft-windows-msconfig-exe_31bf3856ad364e35_10.0.10240.16384_none_e27ab032386d5b35\System Configuration.lnk (p) CSI Payload Corrupt amd64_microsoft-windows-advancedtaskmanager_31bf3856ad364e35_10.0.10240.16384_none_b6e74c8e862c9bea\Task Manager.lnk (p) CSI Payload Corrupt amd64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_10.0.10240.16384_none_a40a2fda3ba13ab4\Resource Monitor.lnk (p) CSI Payload Corrupt amd64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_10.0.10240.16384_none_a40a2fda3ba13ab4\Performance Monitor.lnk (p) CSI Payload Corrupt amd64_microsoft-windows-a..roblemstepsrecorder_31bf3856ad364e35_10.0.10240.16384_none_e2f202dae5a70d92\Steps Recorder.lnk (p) CSI Payload Corrupt amd64_microsoft-windows-msinfo32-exe_31bf3856ad364e35_10.0.10240.16384_none_b3dcd885945b93dc\System Information.lnk (p) CSI Payload Corrupt amd64_microsoft-windows-mediaplayer-shortcut_31bf3856ad364e35_10.0.10240.16384_none_b6d1e3f2e862a82a\Windows Media Player.lnk (p) CSI Payload Corrupt amd64_microsoft-windows-servicessnapin_31bf3856ad364e35_10.0.10240.16384_none_d7645452e0682f87\services.lnk (p) CSI Payload Corrupt amd64_eventviewersettings_31bf3856ad364e35_10.0.10240.16384_none_fcf849b59e606ea6\Event Viewer.lnk (p) CSI Payload Corrupt amd64_taskschedulersettings_31bf3856ad364e35_10.0.10240.16384_none_52eb75789f0a2f2a\Task Scheduler.lnk (p) CSI Payload Corrupt amd64_microsoft-windows-c..termanagementsnapin_31bf3856ad364e35_10.0.10240.16384_none_531691da110444d9\Computer Management.lnk (p) CSI Payload Corrupt amd64_microsoft-windows-m..-odbc-administrator_31bf3856ad364e35_10.0.10240.16384_none_4c50590cd86456d1\ODBC Data Sources (64-bit).lnk (p) CSI Payload Corrupt amd64_microsoft-windows-t..etpc-mathinputpanel_31bf3856ad364e35_10.0.10240.16384_none_d2a1f4c6eb98bc14\Math Input Panel.lnk (p) CSI Payload Corrupt amd64_microsoft-windows-charmap_31bf3856ad364e35_10.0.10240.16384_none_fa5a2f0d3f08718c\Character Map.lnk (p) CSI Payload Corrupt amd64_microsoft-windows-sud-link_31bf3856ad364e35_10.0.10240.16384_none_d72e8d0d677dbba1\Default Programs.lnk (p) CSI Payload Corrupt amd64_microsoft-windows-wordpad_31bf3856ad364e35_10.0.10240.16384_none_35baeae20792cf65\Wordpad.lnk (p) CSI Payload Corrupt amd64_microsoft-windows-cleanmgr_31bf3856ad364e35_10.0.10240.16384_none_7544a80ff8391bd7\Disk Cleanup.lnk (p) CSI Payload Corrupt amd64_microsoft-windows-mspaint_31bf3856ad364e35_10.0.10240.16384_none_961df853893f03be\Paint.lnk (p) CSI Payload Corrupt amd64_microsoft-windows-f..client-applications_31bf3856ad364e35_10.0.10240.16384_none_80fa1e15c313af85\Windows Fax and Scan.lnk (p) CSI Payload Corrupt amd64_microsoft-windows-iscsi_initiator_ui_31bf3856ad364e35_10.0.10240.16384_none_dfeb9c5ff6bf29c8\iSCSI Initiator.lnk (p) CSI Payload Corrupt amd64_microsoft-windows-snippingtool-app_31bf3856ad364e35_10.0.10240.16384_none_a1c473de24503e86\Snipping Tool.lnk (p) CSI Payload Corrupt amd64_microsoft-windows-stickynotes-app_31bf3856ad364e35_10.0.10240.16384_none_f54728ac53f8da94\Sticky Notes.lnk Summary: Operation: Detect only Operation result: 0x0 Last Successful Step: CSI store detection completes. Total Detected Corruption: 31 CBS Manifest Corruption: 0 CBS Metadata Corruption: 0 CSI Manifest Corruption: 0 CSI Metadata Corruption: 0 CSI Payload Corruption: 31 Total Repaired Corruption: 0 CBS Manifest Repaired: 0 CSI Manifest Repaired: 0 CSI Payload Repaired: 0 CSI Store Metadata refreshed: True Total Operation Time: 67 seconds.[/quote]

 

I have run various options to try and fix this Error: 0x800f081f including this script with no sucess
The dism log is showing 15 corrupt files.

sfc /scannow - FAILED
[Windows Resource Protection found corrupt files but was unable to fix some
of them]


DISM /Online /Cleanup-Image /ScanHealth - COMPLETED FINE

DISM /Online /Cleanup-Image /StartComponentCleanup - COMPLETED FINE
[Image Version: 10.0.10240.16384
[==========================100.0%==========================]
The component store is repairable.
The operation completed successfully.]

DISM /Online /Cleanup-Image /AnalyzeComponentStore - COMPLETED
[Component Store (WinSxS) information:
Windows Explorer Reported Size of Component Store : 6.46 GB
Actual Size of Component Store : 6.35 GB
Shared with Windows : 5.28 GB
Backups and Disabled Features : 749.77 MB
Cache and Temporary Data : 314.80 MB
Date of Last Cleanup : 2016-01-06 12:34:05
Number of Reclaimable Packages : 0
Component Store Cleanup Recommended : No
The operation completed successfully.]

Tried both below with same result
DISM /Online /Cleanup-Image /RestoreHealth "/source:WIM:G:\sources\install.wim:1" /LimitAccess - FAILED
DISM /Online /Cleanup-Image /RestoreHealth "/source:WIM:C:\install.wim:1" /LimitAccess - FAILED
[Error: 0x800f081f
The source files could not be found.]

These are the file reported as mismatch
\SystemRoot\WinSxS\amd64_microsoft-windows-d..gement-winproviders_31bf3856ad364e35_10.0.10240.16401_none_bf4fdc1e3f97bf49\ do not match actual file [l:38{19}]"GenericProvider.dll" :
\SystemRoot\WinSxS\wow64_taskschedulersettings_31bf3856ad364e35_10.0.10240.16384_none_5d401fcad36af1 25\taskschd.msc do not match actual file [l:24{12}]"taskschd.msc" :
\SystemRoot\WinSxS\amd64_microsoft-windows-s..ing-shell-extension_31bf3856ad364e35_10.0.10240.16384_none_128248d2bef0d07a\wshext.dll do not match actual file [l:20{10}]"wshext.dll" :
\SystemRoot\WinSxS\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_10.0.10240.16384_none_ae5eda2c7001fcaf\perfmon.msc do not match actual file [l:22{11}]"perfmon.msc" :
\SystemRoot\WinSxS\amd64_fdssdp_31bf3856ad364e35_10.0.10240.16384_none_42de64460eebac05\fdSSDP.dll do not match actual file [l:20{10}]"fdSSDP.dll" :
\SystemRoot\WinSxS\amd64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_10.0.10240.16384_none_a40a2fda3ba13ab4\perfmon.msc do not match actual file [l:22{11}]"perfmon.msc" :
\SystemRoot\WinSxS\amd64_microsoft-windows-mediaplayer-wmpdxm_31bf3856ad364e35_10.0.10240.16384_none_ac389508c278d3bb\wmpdxm.dll do not match actual file [l:20{10}]"wmpdxm.dll" :
\SystemRoot\WinSxS\msil_system.io.log_b03f5f7f11d50a3a_4.0.10240.16384_none_dc7fbbfd30edbd4b\System. IO.Log.dll do not match actual file [l:34{17}]"System.IO.Log.dll" :
\SystemRoot\WinSxS\amd64_microsoft-windows-msident_31bf3856ad364e35_10.0.10240.16384_none_2025ab28e76325a6\msident.dll do not match actual file [l:22{11}]"msident.dll" :
\SystemRoot\WinSxS\amd64_microsoft-windows-wpt-perfcore_31bf3856ad364e35_10.0.10240.16384_none_98767bf5b73a86ec\perfcore.dll do not match actual file [l:24{12}]"perfcore.dll" :
\SystemRoot\WinSxS\wow64_microsoft-windows-s..engine-nativeengine_31bf3856ad364e35_10.0.10240.16384_none_06c4d22a43fd8e25\sdiageng.dll do not match actual file [l:24{12}]"sdiageng.dll" :
\SystemRoot\WinSxS\amd64_microsoft-windows-p..etoolsgui.resources_31bf3856ad364e35_10.0.10240.16384_en-us_5d8a0398de68091f\perfmon.msc do not match actual file [l:22{11}]"perfmon.msc" :
\SystemRoot\WinSxS\amd64_microsoft-windows-p..cemanager.resources_31bf3856ad364e35_10.0.10240.16384_en-us_a9847510c177fa1c\devmgmt.msc do not match actual file [l:22{11}]"devmgmt.msc" :
\SystemRoot\WinSxS\wow64_microsoft-windows-p..etoolsgui.resources_31bf3856ad364e35_10.0.10240.16384_en-us_67deadeb12c8cb1a\perfmon.msc do not match actual file [l:22{11}]"perfmon.msc" :
\SystemRoot\WinSxS\x86_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.1_none_dcc7eae99ad0d9cf\mfc90.d ll do not match file [l:18{9}]"mfc90.dll" :

I can see the files in winsxs - should i boot to USB and manually copy th efiles from winsxs to the files folders ? or copy from the win 10 image Win10_1511_English_x64.iso that i recently downloaded or the original win 10 Windows.iso that i had ?

 

Was there actually install.wim at either path specified in both instances quoted above? You should use the iso corresponding to the build you currently have installed.

Did the current version iso come from Media Creation tool or Tech Bench? Only the Tech Bench iso will have install.wim (MCT iso will have install.esd). If you have an MCT iso with install.esd, you can process that into an install.wim, but Tech Bench iso will already have install.wim. You have to mount the iso and point source at its path or else copy the install.wim to another location you reference in the /source specification.

 

Hi

I have 2 iso's the windows.iso which was created when upgrading from Win7 to win10 - free from MS
the other Win10_1511_English_x64.iso was downloaded from the Tech bench yesterday

I have mounted both images and tried

DISM /Online /Cleanup-Image /RestoreHealth "/source:WIM:G:\sources\install.wim:1" /LimitAccess [Win10_1511_English_x64.iso]

DISM /Online /Cleanup-Image /RestoreHealth "/source:WIM:H:\sources\install.wim:1" /LimitAccess
[windows.iso]
with same results Error: 0x800f081f

i have also extracted the install.wim file from both .iso files \sources folder and copied to c:\
DISM /Online /Cleanup-Image /RestoreHealth "/source:WIM:C:\install.wim:1" /LimitAccess
with same results Error: 0x800f081f

Maybe if i create an image with Media Creation tool and try that .. would that work ?

 

To: spud312r

ONLY use the iso you downloaded from Tech Bench.

Please copy and paste this command line........................

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

Make sure you change the drive letter H to your actual drive letter.

 

Yes i have already tried that - see previous post G: is the mounted drive

DISM /Online /Cleanup-Image /RestoreHealth "/Source:WIM:G:\sources\install.wim:1" /limitAccess
i have removed the "" as well still same results..

I have noticed there is a update waiting to be installed..
Upgrade to Windows 10 Pro, version 1511, 10586

 

Sorry to hear that.

I have no answer for you.

Do not use MCT's ISO for this. It contains the Install.esd, not Install.wim which is what you need.

 

I notice i have a win10 update waiting - so dont know if this will help..

Upgrade to Windows 10 Pro, version 1511, 10586

 

Oh. The ISO you downloaded from Tech Bench is for the current version 10586.
Yet, you didn't even have 10586 installed until just now ?

Well, let the installation begin and then take it from then.

 

Thanks , i will try that tonight

 

Just to be clear.......................

If your Win 10 version is 10240, and you want to run a dism command, you will need a 10240 ISO.
If your Win 10 version is 10586, and you want to run a dism command, you will need a 10586 ISO.

You cannot "mix & match ".