Close
Skip to content

46 Comments

  1. Ben
    July 9, 2021 @ 5:32 pm

    Don't give up, guys. I got to method 4 and it finally worked :)

    Reply

  2. Ken
    May 31, 2021 @ 10:16 am

    Thanks heaps, I had major crashes going on and only just managed to get Restore to load a previous version, but SFC was finding errors in that as well, the first method worked.. only after I ensured it was in fact able to access the internet. All good for now, thanks heaps

    Reply

  3. Tom
    April 23, 2021 @ 3:24 pm

    DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:H:\sources\install.wim:1 /LimitAccess

    I used the above command and got the following error: Error 87
    The restorehealth option is not recognized in this context.
    Also, when I downloaded the win 8.1 files to my ssd G drive, it couldn't
    find the path. For some reason the files also ended up on the H drive which is my
    CD drive. That is why I used the H drive in the command.

    Can you tell me what went wrong?

    Tom

    Reply

    • lakonst
      April 24, 2021 @ 9:09 am

      1. Error 87 often indicates a syntax error in the command, so ensure that you type it correctly.
      2. Ensure that you specified correctly the path of the source files. For your description the source files are on drive G:, so you have to type:
      DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:G:\sources\install.wim:1 /LimitAccess

      Reply

  4. Nicolas Mulfetti
    November 23, 2020 @ 5:53 am

    Thanks a lot for the help! I had been working with my laptop last 2 days to fix the issue with the Start Menu no working.
    My complete computer crashed trying things, like reinstalling the apps or resetting the OS.
    with Method 1. Clean and Analyze the WinSXS folder. It worked!!!!!

    Thanks again!!!! Hope you guys receive more success, blesses!

    Reply

  5. Leonardo Melo
    April 15, 2020 @ 2:51 pm

    Congratulation by this wonderful article. I had trouble wih my Windows 10. The O.S.'s updating does not work completly. And when I tried to use command DISM ( /Online /Cleanup-Image /RestoreHealth), system showed error 0x800f081f (The source files could not be found). Then, thanks to God I found your article. But was necessary performe four methods. Fortunately when I performed 4th method (Fix DISM Source Files Cannot be Found Error with Windows Repair Upgrade), the trouble was solved. God bless you !

    Reply

  6. JWHero123
    March 13, 2020 @ 7:17 am

    Hi, I'm still having problems. I tried all repair solutions on all articles and none of them worked.
    Note:
    Cmds Completed/Error:
    sfc /scannow – windows resource collection found corrupt files but were unable to fix some of them etc
    DISM /Online /Cleanup-Image /StartComponentCleanup – completed
    DISM /Online /Cleanup-Image /AnalyzeComponentStore – completed
    DISM /Online /Cleanup-Image /RestoreHealth – the source files could not be found etc

    I did the install.esd/install.wim method correctly and failed
    I previously tried using all these methods and articles a few months back and wiped and installed a fresh version of windows 10 home.
    I did not look to see if it worked after I did the DISM /Online /Cleanup-Image /RestoreHealth cmd or sfc /scannow cmd to see if it worked as I had no problems with windows update (my current problem)

    Whilst looking through registry editor I could not find my package but I found 2 with a similar registry folder name under "PackageDetect"
    I couldn't find any file anything similarly named in the package name in my Windows Explorer either in the Packages folder.

    However, I did notice it was not a windows related package it was Adobe Flash Player instead which I am aware that I have purposefully installed.

    These are the names of the packages (through cbs.log file) I hope we can find a solution to this:

    1. amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.18362.172_none_815470a5fb446c4e

    2. wow64_adobe-flash-for-windows_31bf3856ad364e35_10.0.18362.172_none_8ba91af82fa52e49

    Reply

    • lakonst
      March 13, 2020 @ 11:22 am

      JWHero123: Follow the instructions on step-2 and delete these registry keys. Then try to run the DISM again.

      Reply

  7. Adrian Southard
    November 24, 2019 @ 1:12 am

    Thank you. I couldn't get the command that utilizes the win10 iso as a repair source but method 1: "Clean and Analyze the Win SXS folder" fixed my corrupt file problem. I haven't had my computer freeze or the cortana search box disappear since. Thank you so much!!

    Reply

  8. fabio
    September 26, 2019 @ 7:57 am

    …after a couple of sleepless night and epic fails, finally I fixed it with method 4 of this article! Many thanks for your helpful site :)

    Reply

  9. Josh
    September 6, 2019 @ 4:04 am

    Yeah, hello. I followed through all the steps, none worked. Now at the regedit option I have my corrupt files to be
    "(p) CSI Payload Corrupt (n)
    amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18875.1000_none_2a030c985f27afeb\MSFT_MpComputerStatus.cdxml
    2019-09-06 01:36:35, Info
    CBS Repair failed: Missing replacement payload."

    There are nine(9) of these buggers there and when I search for them in the registry, somehow, they do not exist. I have tried to solve this dism with no luck. Anyone with any info on this issue, please share.

    Reply

    • lakonst
      September 10, 2019 @ 12:22 pm

      If DISM is not able to repair the system files, then I suggest to perform a repair install.

      Reply

      • Josh
        September 10, 2019 @ 9:39 pm

        Yeah, I have decided to do a neat install instead of trying to solve this issue… This issue really bugs me out. Thanks anyway

        Reply

  10. Chaim Pollak
    August 27, 2019 @ 5:12 pm

    My laptop can't connect to the internet. What are the other options to repair this issue?

    Reply

    • lakonst
      August 28, 2019 @ 9:51 am

      @Chaim Pollak: Follow the steps in this article.

      Reply

  11. Xenthos
    August 18, 2019 @ 6:19 pm

    thank you very much, method 1 worked for me :)

    Reply

  12. Imran Nazir
    August 11, 2019 @ 10:44 am

    DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:X:\sources\install.wim:IndexNumber /LimitAccess
    I used this command. Then I ran sfc/scannow. Then after that, I tried to install new driver software (my laptop model Dell Inspiron 3442 4th Gen Pentium dual core) made by Dell technologies. The driver software installation operation fails Everytime & shoes error. How to fix it?

    Reply

  13. Deardof
    August 7, 2019 @ 7:04 pm

    Thanks. I had fixed the problem. The method 4 worked for me.

    Reply

  14. Dave
    March 17, 2019 @ 6:16 am

    Thank god for this webpage. I kept trying each item going down the page and failing. But the windows media creation tool step did it. I'll send you a few $ if you have a patreon account.

    Reply

  15. Gweltaz
    February 12, 2019 @ 6:46 pm

    Had an error enabling .NET Framework 3.5 on W10.
    This did it: https://support.microsoft.com/en-ph/help/2734782/net-framework-3-5-installation-error-0x800f0906-0x800f081f-0x800f0907
    + Your Method 3 (group Policy) ->
    1) Create a Win10 ISO
    2) Open the MMC + group Policy
    3) Set the alternate dir to the [letter:sources\sxs] folder from the ISO and check to disable Windows Update
    4) Run "gpupdate /force"
    5) Run "dism /Online /Enable-Feature /FeatureName:WCF-HTTP-Activation /All" <- Yay!
    6) Restore the group Policy
    7) Run "gpupdate /force"

    :)

    Reply

  16. Wheelman
    January 10, 2019 @ 1:51 am

    I'm troubleshooting an issue with my GPU mining rig running the trial version of Windows 10. Suddenly, multiple different mining applications didn't recognize any of my AMD graphics cards, but they were shown in Device Manager. I noticed that I was getting the notification "Application has been blocked from accessing graphics hardware", which brought me here. DISM couldn't find the source files (error 0x800f081f) and also wouldn't recognize the install.wim file from the freshly downloaded ISO. Ultimately, Method 4 worked and a repair was successful. Thank you very much for taking the time to create such a thorough guide!

    Reply

  17. Margit
    December 5, 2018 @ 4:25 pm

    Just wanted to thank you for your excellent instructions how to fix this issue. Your article is the only one I found that helps people like me who aren't that computer savvy. In the end, I had to do a non-destructive Windows re-install to fix the update error.

    Reply

  18. Johan Rijpma
    November 4, 2018 @ 10:19 pm

    Even though the descriptions of the different methods are very clear, I wasn't able to solve the problem yet. I feel like I'm going in circles from one method to another now without making any progress. So If anyone could give me any hints based on the log file below I would be very grateful.

    Checking System Update Readiness.
    2018-11-04 14:33:51, Info CBS
    2018-11-04 14:33:51, Info CBS (p) CSI Manifest Corrupt (n) amd64_b6eb56d3a1ffc6dbde7f8d8eb688a286_31bf3856ad364e35_10.0.17134.165_none_90c9a1eb6668c11c
    2018-11-04 14:33:51, Info CBS Repair failed: Missing replacement manifest.
    2018-11-04 14:33:51, Info CBS (p) CSI Manifest Corrupt (n) amd64_f4ebfb19ca40545b5b70cb6de1d79fb0_31bf3856ad364e35_10.0.17134.165_none_5a9f0441ba4fe9a6
    2018-11-04 14:33:51, Info CBS Repair failed: Missing replacement manifest.
    2018-11-04 14:33:51, Info CBS
    2018-11-04 14:33:51, Info CBS Summary:
    2018-11-04 14:33:51, Info CBS Operation: Detect and Repair
    2018-11-04 14:33:51, Info CBS Operation result: 0x800f0907
    2018-11-04 14:33:51, Info CBS Last Successful Step: Entire operation completes.
    2018-11-04 14:33:51, Info CBS Total Detected Corruption: 2
    2018-11-04 14:33:51, Info CBS CBS Manifest Corruption: 0
    2018-11-04 14:33:51, Info CBS CBS Metadata Corruption: 0
    2018-11-04 14:33:51, Info CBS CSI Manifest Corruption: 2
    2018-11-04 14:33:51, Info CBS CSI Metadata Corruption: 0
    2018-11-04 14:33:51, Info CBS CSI Payload Corruption: 0
    2018-11-04 14:33:51, Info CBS Total Repaired Corruption: 0

    * I'm using windows Home version

    Reply

  19. Rodrigo
    September 21, 2018 @ 10:14 am

    Win10 Home. After try almost everything, couple times, i've been finding for any 'manually' approach. The 5th method – the log, the log!- seems to finally solved my problem.
    Thxs a lot.

    Reply

  20. Gnote
    September 20, 2018 @ 12:12 am

    Man… I've spent months trying to fix this error on and off. Went through every fix on all of these pages… except reinstall, which finally fixed it. Next time, I'm just reinstalling!!! Easy peasy!

    Reply

  21. Kaan
    May 15, 2018 @ 12:29 pm

    Hi I cant find those files in regedit, I cant repair it please help.

    =================================
    Checking System Update Readiness.

    (p) CSI Manifest Corrupt amd64_0e9075b73b1af304ca71bb474bade76e_31bf3856ad364e35_10.0.16299.371_none_402e1fbfb487c610
    Repair failed: Missing replacement manifest.
    (p) CSI Manifest Corrupt amd64_302f1d1561cd93b80b770710a9c6c951_31bf3856ad364e35_10.0.16299.371_none_45635903fb6c44b9
    Repair failed: Missing replacement manifest.

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

    Total Operation Time: 1390 seconds.

    Reply

    • lakonst
      May 15, 2018 @ 2:03 pm

      Reply

      • Kaan
        May 15, 2018 @ 3:11 pm

        Thanks , I tried all the steps.
        But it is still same
        CMD
        C:\>DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:c:\install.wim:1 /LimitAccess

        Deployment Image Servicing and Management tool
        Version: 10.0.16299.15

        Image Version: 10.0.16299.431

        [===========================89.1%=================== ]
        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 http://go.microsoft.com/fwlink/?LinkId=243077.
        …………………….
        Checking System Update Readiness.

        (p) CSI Manifest Corrupt amd64_0e9075b73b1af304ca71bb474bade76e_31bf3856ad364e35_10.0.16299.371_none_402e1fbfb487c610
        Repair failed: Missing replacement manifest.
        (p) CSI Manifest Corrupt amd64_302f1d1561cd93b80b770710a9c6c951_31bf3856ad364e35_10.0.16299.371_none_45635903fb6c44b9
        Repair failed: Missing replacement manifest.
        ……………

        Reply

        • lakonst
          May 15, 2018 @ 4:35 pm

          @Kaan: I think that the needed files belongs to a third party app. I suggest to repair Windows 10 with an in=-place upgrade.

          Reply

          • Kaan
            May 15, 2018 @ 5:27 pm

            Thank you very mcuh for your help.
            I think there are no solution left than make that reset to keep my files.
            Also I will ask a question.
            Can I keep using windows like this.

          • lakonst
            May 15, 2018 @ 8:00 pm

            @Kaan: I hope not

  22. GK
    November 12, 2017 @ 4:12 pm

    Worked fine for me!!

    Reply

  23. George Sinkinson
    September 7, 2017 @ 8:27 pm

    My Windows 10 Home 64-bit system suddenly started acting weird. I ran an sfc /scannow and noted 4 corruptions: fdeploy.dll, fde.dll, gptext.dll, and gpedit.dll.

    Followed your Method 1 and seem to have resolved the problem but am curious about the last sfc /scannow CBS.log – it showed 'source file in store is also corrupted' for all four corruptions, but then showed 'All files and registry keys listed in this transaction have been successfully repaired'

    Never even got to the DISM /Online /Cleanup-Image /RestoreHealth step.

    Is that even possible? Could sfc/scannow have cleaned things up without the RestoreHealth, given the stated corruptions?

    Or is this just one of the Microsoft mysteries?

    Reply

    • lakonst
      September 8, 2017 @ 1:11 pm

      @George Sinkinson: I suggest to run all the commands mentioned at the method 1, to ensure that your system is OK.

      Reply

  24. LUIZ
    May 30, 2017 @ 1:57 am

    Thanks. It was impossible to correct using DISM. Everything was correct, like path, Windows version. The outcome was always source not found. However method 4 worked. Sfc came out successfully and so DISM and errors gone.

    Reply

  25. Stuart Berg
    May 11, 2017 @ 8:43 pm

    With minor differences, I tried the solution at
    https://www.bleepingcomputer.com/forums/t/643994/windows-package-file-bad-digital-signature/
    posted by DAC324 and it worked perfectly:

    DISM /Online /Cleanup-Image /RestoreHealth
    Deployment Image Servicing and Management tool
    Version: 10.0.15063.0
    Image Version: 10.0.15063.0
    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.

    sfc /scannow
    Beginning system scan. This process will take some time.
    Beginning verification phase of system scan.
    Verification 100% complete.
    Windows Resource Protection did not find any integrity violations.

    Before I get into the details of what I did, I have a suggestion for this webpage: I would add a "last resort" Method 5 that describes running
    DISM /Online /Cleanup-Image /ScanHealth
    and then examining the bottom of the C:\Windows\Logs\CBS\CBS.log file to see exactly what the problem(s) is(are). Then search the Internet for possible solutions. In this case, it appears that someone at Microsoft left a "testroot" in the packages of the production version of Windows 10 when it shouldn't have been there.

    Here is what I did:
    1. I found two instances of "testroot" packages in the registry at
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex
    of my Windows 10 Home 64-bit version 1703 build 15063.296. They were:
    Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0
    Microsoft-Windows-TestRoot-and-FlightSigning-WOW64-Package~31bf3856ad364e35~amd64~~10.0.15063.0
    2. I exported each of these two registry entries to my desktop for safe keeping, just in case I needed them later.
    3. Then I changed the permissions on the two registry entries giving myself full control.
    4. Then I deleted both registry entries.
    5. Then I searched my C: drive (using the Everything program) for "testroot" files. There were 4, all located in the
    C:\Windows\Servicing\Packages folder:
    Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0.mum
    Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0.cat
    Microsoft-Windows-TestRoot-and-FlightSigning-WOW64-Package~31bf3856ad364e35~amd64~~10.0.15063.0.mum
    Microsoft-Windows-TestRoot-and-FlightSigning-WOW64-Package~31bf3856ad364e35~amd64~~10.0.15063.0.cat
    6. I MOVED all 4 to my Desktop for safe keeping, just in case I needed them later.
    7. The I rebooted.
    The reboot went perfectly and, as you saw above, "DISM /Online /Cleanup-Image /ScanHealth" and "SFC /Scannow" both work perfectly.
    Stu

    Reply

    • lakonst
      May 12, 2017 @ 12:20 pm

      Thank you for the info and I 'm glad that you found the solution.

      Reply

    • crazyfish35
      April 27, 2018 @ 6:17 pm

      Thanks a lot for this information! After a year it still helps people who still have this problem.

      Reply

  26. Stu Berg
    May 10, 2017 @ 3:03 pm

    Continuing from my mistakenly placed comments at the bottom of
    https://www.wintips.org/fix-dism-0x800f081f-error-in-windows-10-8/:

    I followed your instructions which were:
    Windows 10 has many bugs. Anyway try the following:
    1. In a elevated command prompt give the following commands in order:
    DISM /Online /Cleanup-Image /StartComponentCleanup
    SFC /SCANNOW
    DISM /Online /Cleanup-Image /AnalyzeComponentStore
    SFC /SCANNOW
    2. After SFC > Restart your computer.
    3. After Restart, open command prompt (as admin) again and try again > DISM /Online /Cleanup-Image /RestoreHealth

    Step 1:
    DISM /Online /Cleanup-Image /StartComponentCleanup completed successfully with no comments about fixing anything.
    SFC /SCANNOW just said "Verification 100% complete. Windows Resource Protection did not find any integrity violations.".
    DISM /Online /Cleanup-Image /AnalyzeComponentStore said:
    Component Store (WinSxS) information:
    Windows Explorer Reported Size of Component Store : 4.11 GB
    Actual Size of Component Store : 4.01 GB
    Shared with Windows : 3.41 GB
    Backups and Disabled Features : 451.65 MB
    Cache and Temporary Data : 145.43 MB
    Date of Last Cleanup : 2017-05-10 08:03:33
    Number of Reclaimable Packages : 0
    Component Store Cleanup Recommended : No
    The operation completed successfully.
    SFC /SCANNOW just said "Verification 100% complete. Windows Resource Protection did not find any integrity violations.".

    Step 2: The computer restarted normally.

    Step 3:
    DISM /Online /Cleanup-Image /RestoreHealth result was:
    [===========================98.2%======================== ]
    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 http://go.microsoft.com/fwlink/?LinkId=243077.
    The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

    What could it possibly be?

    Reply

    • lakonst
      May 11, 2017 @ 9:48 am

      @Stu Berg: Definitely this is a Windows bug and I 'm afraid that the only option is to perform a fresh Windows 10 installation.
      p.s. have you tried Method 2 & Method 3 from this article?

      Reply

      • Stuart Berg
        May 11, 2017 @ 2:33 pm

        Yes, I've tried all 4 methods and get the same problem. What makes me think I do NOT have to reinstall Windows 10 is that when I run
        DISM /Online /Cleanup-Image /CheckHealth
        I get
        Deployment Image Servicing and Management tool
        Version: 10.0.15063.0
        Image Version: 10.0.15063.0
        The component store is repairable.
        The operation completed successfully.

        It says "The component store is repairable" which means to me that there must be a way to repair it short of doing a complete reinstall from scratch. When I run
        DISM /Online /Cleanup-Image /ScanHealth
        the C:\Windows\Logs\CBS\CBS.log says
        2017-05-11 08:07:01, Info CBS Repr: CSI meta data corruption found, will commit repair transaction if repair is asked.
        2017-05-11 08:07:01, Info CBS Repr: CSI Store check completes
        2017-05-11 08:07:01, Info CBS Ensure WCP corruption flag is clear
        2017-05-11 08:07:01, Info CBS All CSI corruption was fixed, ensure CorruptionDetectedDuringAcr is clear
        2017-05-11 08:07:01, Info CBS Failed to clear CorruptionDetectedDuringAcr store corrupt flag (slow mode trigger). [HRESULT = 0x80070002 – ERROR_FILE_NOT_FOUND]
        2017-05-11 08:07:01, Info CBS
        =================================
        Checking System Update Readiness.
        (p) CBS MUM Corrupt Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0
        Summary:
        Operation: Detect only
        Operation result: 0x0
        Last Successful Step: CSI store detection completes.
        Total Detected Corruption: 1
        CBS Manifest Corruption: 1
        CBS Metadata Corruption: 0
        CSI Manifest Corruption: 0
        CSI Metadata Corruption: 0
        CSI Payload Corruption: 0
        Total Repaired Corruption: 0
        CBS Manifest Repaired: 0
        CSI Manifest Repaired: 0
        CSI Payload Repaired: 0
        CSI Store Metadata refreshed: True

        I believe I found the solution here:
        https://www.bleepingcomputer.com/forums/t/643994/windows-package-file-bad-digital-signature/
        Look for the posting by DAC324. What do you think? Should I try it?
        Stu

        Reply

    • jennie
      July 12, 2017 @ 1:18 pm

      I am downloading windows 8.1 media creation tool , why it is very slow.

      Reply

      • lakonst
        July 12, 2017 @ 1:54 pm

        @jennie: The download speed is slow because of Microsoft servers.

        Reply

        • jennie
          July 13, 2017 @ 12:39 am

          Lakonst, thanks for your reply .
          I have downloaded for 24 hours day and night. How long would it take to get all files ready?
          On the installation screen, there does not show how many percentage of files have been downloaded, only show “ estimating time” characters, but there is no any exact estimateing time indicated.
          Also, I did not see any files downloaded in my USB drive.
          Thanks again.

          Reply

          • lakonst
            July 13, 2017 @ 8:55 am

            @jennie: I suggest to stop the current operation/download and then to restart your computer. After restart start the Media Creation tool and try to download Windows 8.1 again.

Leave a Reply

Your email address will not be published. Required fields are marked *

css.php