Page 5 of 8 FirstFirst ... 34567 ... LastLast
  1.    16 Nov 2015 #41
    Join Date : Sep 2014
    Warsaw, Poland
    Posts : 36
    Win 10 Pro 64-bit (Anniversary 1607)

    The script has helped me perfectly - with using the latest installation media all was like a breeze!
    Thank you, Kyhi!
      My System SpecsSystem Spec

  2.    01 Dec 2015 #42
    Join Date : Dec 2015
    Ponte Vedra Beach, FL
    Posts : 1
    Windows 10 Professional 64-Bit

    My thanks to Lx07, KYHI and others.
    The combination of Image_Health and the .iso from TechBench solved my DISM problem.
    (The url's for the above are posted in this thread.)
      My System SpecsSystem Spec

  3.    01 Dec 2015 #43
    Join Date : Nov 2015
    Posts : 31
    Windows 10 Pro

    Quote Originally Posted by Kyhi View Post
    twp things..

    Executing command line: Dism /Online /Cleanup-Image /RestoreHealth /Source:"D:\Users\Hali\Downloads\IMAGE_HEALTH\IMAGE_HEALTH_SXS\Temp\Mount\windows\winsxs" /LimitAccess

    Place the "Image_health" folder on C - you are running the command 9 folders deep...
    Place Image_health-sxs.cmd inside "image_health" folder
    Image health sxs cmd was and is only a TEST cmd
    Image-health is the normal cmd...

    Attachment 39329

    "C:\Windows\Logs\CBS\CBS.log" post the CBS.log

    Also dism /scanhealth gives a better file report in the dism.log

    Your damaged files appear to be that from a windows update, as windows update files are not on setup media..

    step 1 delete current dism and cbs log files
    step 2 run Image_Health.cmd - option 1 = scanhealth
    step 3 run Image health - option 2 = restorehealth
    step 4 run image health - option 3 = restorehealth /source
    step 5 post dism.log and cbs.log (note: you can post logs as .txt > cbs.txt dism.txt)
    Having being frustrated with having the dism error (0x800f081f error) which was unfixable after a clean Windows 10 install time after time, it was great to find this fix which works a treat and and allows "sfc scannow" to complete error free as well as dism.

    I do have a question though, what causes these errors in the first place? I have had the same thing happen twice in the space of 3 weeks and tonight also. Maybe it is something I am doing which I don't realise is causing it. My system is clean and the latest Windows 10 build and my system shows no symptoms of any kind.
    Again running the "Image health cmd" fixes it. Is it a case of don't worry about it and just carry on?

    Thanks in advance.

    Edit.... I updated my Nvidia drivers tonight. Maybe they are the culprit.
      My System SpecsSystem Spec

  4.    07 Dec 2015 #44
    Join Date : Dec 2015
    Posts : 9
    Windows 10 N

    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,
      My System SpecsSystem Spec

  5.    22 Dec 2015 #45
    Join Date : Dec 2015
    Posts : 2
    Windows 10 pro

    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:
      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
    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
    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
    Press any key to continue . . .
    Content of dism.log is here: 2015-12-22 14:47:32, Info DISM PID=77184 TID=56492 Scratch di -

    Can you give me a direction for solving the issue?
      My System SpecsSystem Spec

  6.    22 Dec 2015 #46
    Join Date : Jun 2015
    Posts : 1,580
    Windows 3.1 to Windows 10

    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
      My System SpecsSystem Spec

  7.    22 Dec 2015 #47
    Join Date : Dec 2015
    Posts : 2
    Windows 10 pro

    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.
    Last edited by biro; 22 Dec 2015 at 12:23.
      My System SpecsSystem Spec

  8.    22 Dec 2015 #48
    Join Date : Jun 2015
    Posts : 1,580
    Windows 3.1 to Windows 10

    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
    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.
      My System SpecsSystem Spec

  9.    06 Jan 2016 #49
    Join Date : Jan 2016
    Posts : 5
    Win 10

    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
    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\\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\\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 ?
      My System SpecsSystem Spec

  10.    06 Jan 2016 #50
    Join Date : Aug 2015
    Penn's Woods
    Posts : 1,176
    Windows 10 Home RTM + Insider

    Quote Originally Posted by spud312r View Post
    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.]

    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.
      My System SpecsSystem Spec

Page 5 of 8 FirstFirst ... 34567 ... LastLast

Similar Threads
Thread Forum
SFC Scannow or DISM/RestoreHealth using Image
Windows 10 user. Having some trouble with my system after coming back from a weekend. Nothing major...just having trouble playing some games that require plugins etc Regardless if it's related, I just wanted to run an SFC/Scannow or...
Performance & Maintenance
Error 0x800f081f when Running DISM. Need Help!
I recently updated to Windows 10 (from Windows 7) and I feel there is something wrong with the performance of my ASUS Zenbook. I run DISM and I got the following error message: 1. DISM /Online /Cleanup-Image /RestoreHealthDISM /Online...
Performance & Maintenance
DISM COMException Error
I've discovered a weird issue on Windows 10x64 10525 Any solution yet?
Performance & Maintenance
About /dism /restorehealth BSOD and reset PC
There is a link between all of them, and after doing tests I think I found a way to make things right. What I did on 2 computers (1 with BIOS and 1 with UEFI). Both have only one SSD. I kept the things as simple as possible. Both are x64 versions of...
General Support
10130 - DISM error
Getting this error when running DISM after a clean install: Log file is available if anyone wants it. I looked at it but don't understand what it's saying.
General Support
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 13:29.
Find Us
Twitter Facebook Google+

Windows 10 Forums