Windows 10: How to overcome Error 0x800f081f "The source files could not be found" when performing DISM...

Discus and support How to overcome Error 0x800f081f "The source files could not be found" when performing DISM... in Windows 10 Installation and Upgrade to solve the problem; I have a dual-boot laptop with Ubuntu 18.04.2 and Windows 10 Home Edition. I can't get to the sign in screen in Windows because it always tries to... Discussion in 'Windows 10 Installation and Upgrade' started by HopefulComputerScientist, Jul 26, 2019.

  1. How to overcome Error 0x800f081f "The source files could not be found" when performing DISM...


    I have a dual-boot laptop with Ubuntu 18.04.2 and Windows 10 Home Edition. I can't get to the sign in screen in Windows because it always tries to perform a Startup Repair and fails. I've tried using System Restore: when using the most recent restore point, the Startup Repair problem persists. When using the second most recent point (and last I have), before a Windows Update I get the 0x81000204 error message. Here's what I've tried so far:

    • Following this guide with several adaptations due to not being able to boot into into Windows:
      • Ran the Command Line from the Recovery Environment (have used both the RE Windows takes me to after Startup Repair fails and the one accessible by booting from a Windows bootable USB)
      • Replaced /Online by /Image:C:
      • Downloaded the Windows 10 ISO image from the official website, then created a Windows bootable USB following the first method on this guide.
      • Used this guide to see which intall.wim files were inside the install.wim file inside the sources folder. There are a total of 13 editions, 3 of them pertaining to Windows 10 Home: the "regular one", one called Windows 10 Home N and one called Windows 10 Home Single Language.
      • Ran the following command to extract the (what I think is) relevant edition to my Windows primary partition:

    dism /export-image /SourceImageFile:G:\sources\install.wim /SourceIndex:1 /DestinationImageFile:C:\install.wim /Compress:max /CheckIntegrity

    (G: is the drive letter of the Windows bootable USB I created earlier). It ran without throwing out any errors.

    • Added the argument /Source with several differente variations:

    dism /Image:C: /Cleanup-Image /RestoreHealth /Source:Wim:C:\install.wim /LimitAccess

    dism /Image:C: /Cleanup-Image /RestoreHealth /Source:Wim:C:\install.wim:1 /LimitAccess


    As suggested in the Configure a Windows Repair Source Microsoft page, I've also tried to use a Windows side-by-side folder from the bootable USB, by running:

    dism /Image:C: /Cleanup-Image /RestoreHealth /Source:G:\sources\SxS


    Tried mounting the install.wim image first in my Windows primary partition by running the following command, which I found somewhere I can't remember:

    dism /mount-wim /wimfile:C:\install.wim /index:1 \mountdir:C:\Images\mounted


    This operation ran successfully. I then ran

    dism /Image:C: /Cleanup-Image /RestoreHealth /Source:C:\Images\mounted


    as suggested in point 1 of the Configure a Windows Repair Source page.


    I've tried diffrent indexes (1, 2 and 3), deleting the "Wim:" part from /Source:Wim:C:\install.wim, using the bootable USB directly as the /Source drive, creating a bootable USB in a Windows computer (in that case it comes with a install.esd which I handled acording to this guide. I've successfully ran


    DISM /Image:C: /Cleanup-Image /StartComponentCleanup and

    DISM /Online /Cleanup-Image /AnalyzeComponentStore

    I've run an offline SFC which returned Windows Resource Protection found corrupt files but was unable to fix some of them.


    Every single time I ran dism /Cleanup-Image /RestoreHealth commands I got the warning "The scratch directory size might be insufficient to perform this operation. This can cause unexpected behavior. Use the /ScratchDir option to point to a folder with sufficient scratcg space. The recommended size is at least 1024 MB". I don't know if this made any difference.


    But most importantly (and cause of much frustratrion) I always get the

    "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 (...)


    The DISM log file can be found at X:\windows\Logs\DISM\dism.log"

    I've looked through the log files and I can find what I suppose are relevant messages like


    2019-07-24 07:56:02, Info CBS Exec: Addsource called, Session: 6768_7899109, Client: DISM Package Manager Provider, from GPO: No, Path: C:\install2.wim

    2019-07-24 07:56:02, Warning CBS The alternate source path directory could not be accessed [HRESULT = 0x8007007b - ERROR_INVALID_NAME]

    2019-07-24 07:56:02, Info CBS Failed to add new file source [HRESULT = 0x8007007b - ERROR_INVALID_NAME]

    2019-07-24 07:56:02, Info CBS Failed to add alternate file source [HRESULT = 0x8007007b - ERROR_INVALID_NAME]

    2019-07-24 07:56:02, Info CBS Failed adding alternate source directory [HRESULT = 0x8007007b - ERROR_INVALID_NAME]

    2019-07-24 07:56:02, Warning DISM DISM Package Manager: PID=6768 TID=6792 CBS AddSource failed with HRESULT=0x8007007b! - CDISMPackageManager::Internal_Finalize



    2019-07-24 07:55:55, Warning DISM DISM Provider Store: PID=6736 TID=6740 Failed to load the provider: X:\Sources\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)



    2019-07-24 07:55:55, Info DISM DISM WIM Provider: PID=6736 TID=6740 [C:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize

    2019-07-24 07:55:55, Info DISM DISM VHD Provider: PID=6736 TID=6740 [C:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize

    2019-07-24 07:55:55, Warning DISM DISM Provider Store: PID=6736 TID=6740 Failed to retrieve the Provider Instance. - CDISMProviderStore::Internal_GetProvider(hr:0x80004005)

    2019-07-24 07:55:55, Info DISM DISM VHD Provider: PID=6736 TID=6740 [C:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize

    2019-07-24 07:55:55, Info DISM DISM Imaging Provider: PID=6736 TID=6740 The provider VHDManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage

    [6736] [0x80070002] FIOReadFileIntoBufferHow to overcome Error 0x800f081f "The source files could not be found" when performing DISM... :(1381): O sistema não conseguiu localizar o ficheiro especificado.

    [6736] [0xc142011c] UnmarshallImageHandleFromDirectoryHow to overcome Error 0x800f081f "The source files could not be found" when performing DISM... :(641)

    [6736] [0xc142011c] WIMGetMountedImageHandleHow to overcome Error 0x800f081f "The source files could not be found" when performing DISM... :(2897)

    2019-07-24 07:55:55, Info DISM DISM WIM Provider: PID=6736 TID=6740 [C:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize

    2019-07-24 07:55:55, Info DISM DISM Imaging Provider: PID=6736 TID=6740 The provider WimManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage

    2019-07-24 07:55:55, Info DISM DISM Imaging Provider: PID=6736 TID=6740 No imaging provider supported CreateDismImage for this path - CGenericImagingManager::CreateDismImage

    2019-07-24 07:55:55, Info DISM DISM Manager: PID=6736 TID=6740 physical location path: C:\ - CDISMManager::CreateImageSession


    and later


    2019-07-24 08:08:39, Error CSI 00000043@2019/7/24:08:08:39.495 (F) Attempting to mark store corrupt with category [l:18 ml:19]'CorruptPayloadFile'[gle=0x80004005]

    2019-07-24 08:08:39, Info CSI 00000044@2019/7/24:08:08:39.557 Corruption detection complete. numCorruptions = 65, Disp = 1.

    2019-07-24 08:08:39, Info CBS Repr: CSI meta data corruption found, will commit repair transaction if repair is asked.

    2019-07-24 08:08:39, Info CSI 00000045@2019/7/24:08:08:39.557 CSI Transaction @0x2bd46b75570 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000002 and client id 'TI5.6768_7899109:1/'


    and afterwards a huge amount of "Not able to find replacement file for component (...)"


    2019-07-24 08:08:39, Info CBS Repr: Not able to find replacement file for component amd64_microsoft-windows-sechealthui.appxmain_31bf3856ad364e35_10.0.17134.407_none_94c831bd33ee8579, file SecHealthUI.exe from any local source

    2019-07-24 08:08:39, Info CBS Repr: Not able to find replacement file for component amd64_microsoft-windows-s..emsettingsthreshold_31bf3856ad364e35_10.0.17134.441_none_011ac95e3400d5eb, file SystemSettings.dll from any local source

    2019-07-24 08:08:39, Info CBS Repr: Not able to find replacement file for component amd64_microsoft-windows-mapcontrol_31bf3856ad364e35_10.0.17134.619_none_f523e5336089c1e6, file BingMaps.dll from any local source

    2019-07-24 08:08:39, Info CBS Repr: Not able to find replacement file for component amd64_microsoft-windows-mapcontrol_31bf3856ad364e35_10.0.17134.619_none_f523e5336089c1e6, file mos.dll from any local source

    later still


    2019-07-24 08:08:39, Info CBS =================================

    2019-07-24 08:08:39, Info CBS Checking System Update Readiness.

    2019-07-24 08:08:39, Info CBS

    2019-07-24 08:08:39, Info CBS (p) CSI Payload Corrupt (n) amd64_microsoft-windows-sechealthui.appxmain_31bf3856ad364e35_10.0.17134.407_none_94c831bd33ee8579\SecHealthUI.exe

    2019-07-24 08:08:39, Info CBS Repair failed: Missing replacement payload.

    2019-07-24 08:08:39, Info CBS (p) CSI Payload Corrupt (n) amd64_microsoft-windows-s..emsettingsthreshold_31bf3856ad364e35_10.0.17134.441_none_011ac95e3400d5eb\SystemSettings.dll

    2019-07-24 08:08:39, Info CBS Repair failed: Missing replacement payload.

    2019-07-24 08:08:39, Info CBS (p) CSI Payload Corrupt (n) amd64_microsoft-windows-mapcontrol_31bf3856ad364e35_10.0.17134.619_none_f523e5336089c1e6\BingMaps.dll

    2019-07-24 08:08:39, Info CBS Repair failed: Missing replacement payload.

    2019-07-24 08:08:39, Info CBS (p) CSI Payload Corrupt (n) amd64_microsoft-windows-mapcontrol_31bf3856ad364e35_10.0.17134.619_none_f523e5336089c1e6\mos.dll

    So this makes me suspect I'm doing something wrong with the DISM source specification and maybe the replacement for /Online argument (I've tried /Image:C:\Windows and it didn't work), but I can't find out what. So my question is, given all of this information


    Is there a way to successfully run dism to repair my Windows image and if so, what is it?


    Thank you for your patience and sorry for such a long post.

    Best regards

    :)
     
    HopefulComputerScientist, Jul 26, 2019
    #1
  2. sedge1955 Win User

    DISM "error 0x800f081f The source files could not be found" still a plague

    This is a continuation of the post here:

    [RESOLVED] DISM "error 0x800f081f The source files could not be found" even with correct ISO and path

    which is not resolved for me.

    I have this error and have tried to follow all the suggestions in the post. I first noticed the problem a few weeks ago and my Windows 10 installation had only automatically applied the Creators Update maybe 2 months ago.

    Run DISM

    PS C:\WINDOWS\system32> DISM.exe /Online /Cleanup-image /Restorehealth

    Deployment Image Servicing and Management tool

    Version: 10.0.16299.15

    Image Version: 10.0.16299.125

    [===========================84.3%================ ]

    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

    Downloaded the ISO and had exactly the same result.

    PS C:\WINDOWS\system32> Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:E:\Sources\Install.wim:1 /limitaccess

    Deployment Image Servicing and Management tool

    Version: 10.0.16299.15

    Image Version: 10.0.16299.125

    [===========================84.4%================ ]

    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

    In the dism.log file:

    - 1 second after the process starts, this warning:

    2018-04-27 09:27:24, Warning DISM DISM OS Provider: PID=4860 TID=7108 Unable to set the DLL search path to the servicing stack folder. C:\Windows may not point to a valid Windows folder. - CDISMOSServiceManager::Final_OnConnect

    and

    2018-04-27 09:27:28, Warning DISM DISM Package Manager: PID=4860 TID=7108 CBS AddSource failed with HRESULT=0x80070002! - CDISMPackageManager::Internal_Finalize

    2018-04-27 09:27:28, Info DISM DISM Package Manager: PID=4860 TID=7108 CBS session options=0x20100! - CDISMPackageManager::Internal_Finalize
    then

    2018-04-27 09:41:02, Info DISM DISM Package Manager: PID=4860 TID=5772 Error in operation: source for package or file not found, ResolveSource() unsuccessful. (CBS HRESULT=0x800f081f) - CCbsConUIHandler::Error

    2018-04-27 09:41:02, Error DISM DISM Package Manager: PID=4860 TID=7108 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f081f)

    2018-04-27 09:41:02, Error DISM DISM Package Manager: PID=4860 TID=7108 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg

    2018-04-27 09:41:02, Error DISM DISM Package Manager: PID=4860 TID=7108 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f081f)

    2018-04-27 09:41:02, Error DISM DISM Package Manager: PID=4860 TID=7108 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg

    2018-04-27 09:41:02, Error DISM DISM Package Manager: PID=4860 TID=7108 Failed to restore the image health. - CPackageManagerCLIHandler:How to overcome Error 0x800f081f "The source files could not be found" when performing DISM... :processCmdLine_CleanupImage(hr:0x800f081f)

    2018-04-27 09:41:02, Error DISM DISM Package Manager: PID=4860 TID=7108 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)

    2018-04-27 09:41:02, Info DISM DISM Package Manager: PID=4860 TID=7108 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine

    I wasn't able to locate "Tech Bench ISO " to try that.

    The history of this PC was:

    - 2H 2015

    - Clean install of windows 7 Pro from original HP media

    - Apply all updates

    - Free windows 10 Upgrade

    - All windows updates applied in the interim, including "Anniversary Update"

    - 1Q 2018 Creators Update applied automatically.

    Can someone help provide this blockage to the Windows Update process?

    Thanks

    Steve
     
    sedge1955, Jul 26, 2019
    #2
  3. Error: 0x800f081f, "The source files could not be found." after performing DISM command

    After running the DISM /Online /Cleanup-Image /RestoreHealth,I receive "[==========================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."
    Since I upgraded A PREINSTALLED Windows 7 to Windows 10 I have no available ISO/IMG to point a source location.

    So, though it shows 100% completed operation, I am not sure it's OK.
    dism.exe /online /Cleanup-Image /StartComponentCleanup

    and

    sfc /scannow

    return messages for no problems.
    Could the problem be related to the fact that I run Windows under the Insider programme?

    If not what then should I do to get to a positive result?
     
    ОгнянПаскалев, Jul 26, 2019
    #3
  4. How to overcome Error 0x800f081f "The source files could not be found" when performing DISM...

    Error: 0x800f081f, "The source files could not be found." after performing DISM command

    I've run DISM /Online /Cleanup-Image /RestoreHealth with the following results:

    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
    .

    When I go to the suggested link
    http://go.microsoft.com/fwlink/?LinkId=243077
    this what I see:

    Choose a Repair Source

    You can use Windows Update to provide the files that are required to restore a Windows feature or repair a corrupted operating system. You can also configure Group Policy to gather the required files from a network location. Multiple source locations can
    be specified in the Group Policy.

    To use Windows Update to restore optional features and repair Windows images

    •Windows Update will be used by default if it is allowed by the policy settings on the computer.

    •If you want to use Windows Update as a primary or backup source for files that are used to restore optional features or repair Windows images, you should make sure that your firewall is configured to allow access to Windows Update.

    It really doesn't tell you how to designate a repairs source. How do you do that?

    Original title: How do I designate a Source for DISM Restorehealth
     
    KennethLang, Jul 26, 2019
    #4
Thema:

How to overcome Error 0x800f081f "The source files could not be found" when performing DISM...

Loading...
  1. How to overcome Error 0x800f081f "The source files could not be found" when performing DISM... - Similar Threads - overcome Error 0x800f081f

  2. DISM error 0x800f081f - Source file could not be found

    in Windows 10 Gaming
    DISM error 0x800f081f - Source file could not be found: Hi -I've been having issues recently installing Windows updates and I found that my Windows "Sandbox" environment is no longer working. I've recently been messing with my .net installation to get a specific application working I'm pretty sure that's how I got into this mess...
  3. DISM error 0x800f081f - Source file could not be found

    in Windows 10 Software and Apps
    DISM error 0x800f081f - Source file could not be found: Hi -I've been having issues recently installing Windows updates and I found that my Windows "Sandbox" environment is no longer working. I've recently been messing with my .net installation to get a specific application working I'm pretty sure that's how I got into this mess...
  4. DISM error 0x800f081f - Source file could not be found

    in Windows 10 BSOD Crashes and Debugging
    DISM error 0x800f081f - Source file could not be found: Hi -I've been having issues recently installing Windows updates and I found that my Windows "Sandbox" environment is no longer working. I've recently been messing with my .net installation to get a specific application working I'm pretty sure that's how I got into this mess...
  5. DISM "error 0x800f081f The source files could not be found".

    in Windows 10 Software and Apps
    DISM "error 0x800f081f The source files could not be found".: I am unable to complete the repair using DISM command tool.My Lap runs Windows 10 version 22H2, build 19045.2364. It has recently started having some problem with windows update showing errors0x80071160 and 0x800706ba.RanDISM /Online /Cleanup-Image /CheckHealth Deployment...
  6. DISM "error 0x800f081f The source files could not be found".

    in Windows 10 Customization
    DISM "error 0x800f081f The source files could not be found".: I am unable to complete the repair using DISM command tool.My Lap runs Windows 10 version 22H2, build 19045.2364. It has recently started having some problem with windows update showing errors0x80071160 and 0x800706ba.RanDISM /Online /Cleanup-Image /CheckHealth Deployment...
  7. DISM "error 0x800f081f The source files could not be found".

    in Windows 10 Gaming
    DISM "error 0x800f081f The source files could not be found".: I am unable to complete the repair using DISM command tool.My Lap runs Windows 10 version 22H2, build 19045.2364. It has recently started having some problem with windows update showing errors0x80071160 and 0x800706ba.RanDISM /Online /Cleanup-Image /CheckHealth Deployment...
  8. DISM "error 0x800f081f The source files could not be found"

    in Windows 10 BSOD Crashes and Debugging
    DISM "error 0x800f081f The source files could not be found": I have the same exact issue documented in this thread: https://answers.microsoft.com/en-us/windows/forum/windows_10-performance-winpc/resolved-dism-error-0x800f081f-the-source-files/1a58faa1-6e7a-4eac-8327-5e6888e0d57b I am running windows 10 C:\WINDOWS\system32>Dism...
  9. DISM 0x800f081f; source files could not be found

    in Windows 10 Installation and Upgrade
    DISM 0x800f081f; source files could not be found: Hi all, I've been having issues with getting DISM to successfully run the following: DISM /Online /Cleanup-Image /RestoreHealth When I do, it gives me a 0x800f081f; source files could not be found. Part of my problem is that I'm on image version 10.0.19041.508 Windows...
  10. The source files could not be found Error: 0x800f081f DISM Help.

    in Windows 10 BSOD Crashes and Debugging
    The source files could not be found Error: 0x800f081f DISM Help.: Some files got corrupted today idk how, many applications won't won't open. I tried using the Command Prompt using /Online /Cleanup-Image /RestoreHealth /Source:WIM:I:\Sources\Install.wim:1 /LimitAccess. But the it says The source files could not be found Error: 0x800f081f....
Tags:

Users found this page by searching for:

  1. 0x800f081f even with specifying source

    ,
  2. dism restorehealth error 0x800f081f addsource resolvesource

    ,
  3. Error in operation: source for package or file not found ResolveSource() unsuccessful. (CBS HRESULT=0x800f081f)

    ,
  4. yahoo error code 6740,
  5. Failed to find payload files component:amd64_windows-defender-,
  6. Error in operation: source for package or file not found ResolveSource() unsuccessful. (CBS HRESULT=0x800f081f) - CCbsConUIHandler::Error,
  7. HP laptop ran DISM error 0x800f081f source file could not be found,
  8. CBS AddSource failed with HRESULT 0x8007007b,
  9. windows 2016 the source files could not be found