Windows 10 DISM 0x800f081f: The source files could not be found.

B

bobmanzoidzo

Member
Joined
Feb 15, 2022
Posts
7
Hello,

Recently, my Windows 10 installation failed to boot from the drive. There's no BSOD, it just goes straight to the Windows Recovery Environment. Anything in the WRE also fails to work (system reset etc fails to complete or unexpectedly reboots, and no restore points show up). I installed Windows 10 on another connected drive and have tried running SFC, DISM, and other recovery tools to no avail.

chkdsk returns no errors

SFC scan returns "Windows Resource Protection found corrupt files but was unable to fix some of them."

Running DISM returns:

Code: 
Deployment Image Servicing and Management tool

Version: 10.0.19041.844


Image Version: 10.0.19044.1526


[==========================100.0%==========================]

Error: 0x800f081f


The source files could not be found.

I have tried running SFCFix but I'm not sure how to specify that it should run on the offline drive, so I don't think it's done anything.

I've tried running DISM with every variety of inputs, from esd, to every version of iso I could find, to WinSxS, but in all cases the progress goes to around 60% before jumping to 100% and giving the same error code. The DISM log shows:

Code: 
2022-02-15 09:59:14, Info                  CBS    Summary:
2022-02-15 09:59:14, Info                  CBS    Operation: Detect and Repair
2022-02-15 09:59:14, Info                  CBS    Operation result: 0x800f081f
2022-02-15 09:59:14, Info                  CBS    Last Successful Step: Remove staged packages completes.
2022-02-15 09:59:14, Info                  CBS    Total Detected Corruption:    542
2022-02-15 09:59:14, Info                  CBS        CBS Manifest Corruption:    342
2022-02-15 09:59:14, Info                  CBS        CBS Metadata Corruption:    0
2022-02-15 09:59:14, Info                  CBS        CSI Manifest Corruption:    86
2022-02-15 09:59:14, Info                  CBS        CSI Metadata Corruption:    0
2022-02-15 09:59:14, Info                  CBS        CSI Payload Corruption:    114
2022-02-15 09:59:14, Info                  CBS    Total Repaired Corruption:    0
2022-02-15 09:59:14, Info                  CBS        CBS Manifest Repaired:    0
2022-02-15 09:59:14, Info                  CBS        CSI Manifest Repaired:    0
2022-02-15 09:59:14, Info                  CBS        CSI Payload Repaired:    0
2022-02-15 09:59:14, Info                  CBS        CSI Store Metadata refreshed:    True
2022-02-15 09:59:14, Info                  CBS    Staged Packages:
2022-02-15 09:59:14, Info                  CBS        CBS Staged packages:    0
2022-02-15 09:59:14, Info                  CBS        CBS Staged packages removed:    0
2022-02-15 09:59:14, Info                  CBS   
2022-02-15 09:59:14, Info                  CBS    Total Operation Time: 124 seconds.
2022-02-15 09:59:14, Info                  CBS    Not all CSI corruption was fixed, create CorruptionDetectedDuringAcr flag for slow mode reset
2022-02-15 09:59:14, Info                  CBS    CheckSur: hrStatus: 0x800f081f [CBS_E_SOURCE_MISSING], download results: <none>
2022-02-15 09:59:14, Info                  CBS    Count of times corruption detected: 1
2022-02-15 09:59:14, Info                  CBS    Seconds between initial corruption detections: -1
2022-02-15 09:59:14, Info                  CBS    Seconds between corruption and repair: -1
2022-02-15 09:59:14, Info                  CBS    Failed to run Detect and repair. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2022-02-15 09:59:14, Info                  CBS    Exec: Processing complete, session(Corruption Repairing): 12880_67188468 [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]

So it appears there are quite a few corrupted files. Presumably because I run the SFC tool in the offbootdir/offwindir form, it does not update the CBS.log, so I don't have anything from there to upload.
 
Since you have a number of issues, then the best approach would be to attempt an in-place upgrade (repair install) using a Windows 10 ISO, if you haven't done so already.
 
Thank you for the reply!

From what I see, a repair install can only be done from within the Windows 10 environment. Given I cannot boot into Windows on the original drive, how would I go about a repair install on it?
 
The setup tool should provide an option to be able to create an installation media for another computer. Do you have access to another working computer to be able to do this?
 
Yes, I can create an installation media from the Windows installation on the other drive. What would be the process to do a "repair install" from the installation media?
 
I looked through and followed the instructions from the guide you provided. The problem it seems is that this guide only works for the currently running version of windows, and I can't boot into the installation of Windows that I need to repair. Running the setup only reinstalls Windows on the drive I run it off of, which does not have the issue. As far as I can tell there is no way to run a repair install on an offline version of Windows that won't boot?
 
You'll need to use the Setup.exe to create an installation ISO and then transfer that to a DVD/USB to boot from. From there, you'll be able to follow the same steps as before and perform a repair install by doing an in-place upgrade.

Download Windows 10
 
So, I've created installation media on a USB using both the MCT and third party tools, but when I boot using the drive, I am presented with the options to Install Windows or Repair.

Repair just opens up the same options I already have in the Recovery Environment, none of which have worked (startup repair, restore etc).

Install Windows gives the options to either Upgrade Windows or Install Windows. However, clicking "Upgrade" just shows "Compatibility Report: The upgrade option isn't available if you start your computer using Windows installation media" and asks you run the software from within a running version of Windows.

The instructions from britechguy don't specify anything outside of doing a repair install/upgrade from within Windows, so I'm still at a loss as to how you're supposed to do a repair install if the installed version of Windows cannot boot.

I'm not going to have access to the computer in question for the next week or so, so no rush on responses, but thank you for looking into the issue so far!
 
Unfortunately that proposal isn't going to work which is frustrating.

bobmanzoidzo said:
Repair just opens up the same options I already have in the Recovery Environment, none of which have worked (startup repair, restore etc).
Click to expand...
Could you please check if the following file exists?

Rich (BB code): 
C:\Windows\System32\Logfiles\Srt\SrtTrail.txt

It may be worthwhile ensuring that there is no SSD/HDD problems by running a hard-disk diagnostic test from your manufacturer. Some examples in this thread here - Hard Drive (HDD) Diagnostics (Sea Tools for DOS) & SSD Test
 
I tried running the boot version of SeaTools, but was unable to get it to work (black screen after loading extensions). I ran the non-boot version of it and the Long Self Test did not turn up any issues. Crystal Disk also didn't seem to find anything.

The SRT file from the old SSD is below:

Code: 
Startup Repair diagnosis and repair log
---------------------------
Number of repair attempts: 1

Session details
---------------------------
System Disk =
Windows directory = D:\WINDOWS
AutoChk Run = 0
Number of root causes = 1

Test Performed:
---------------------------
Name: Check for updates
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System disk test
Result: Completed successfully. Error code =  0x0
Time taken = 15 ms

Root cause found:
---------------------------
A hard disk could not be found. If a hard disk is installed, it is not responding.

---------------------------
---------------------------
 
Could you please boot into the Windows RE command prompt and then enter the following commands:

Rich (BB code): 
bootrec /rebuildbcd
bootrec /fixmbr
bootrec /fixboot
 
Apologies for the long delay in responding. In between your reply and this post, I had the Windows installation on the new drive fail as well when booting up one day, in much the same way as the original failure, except it wouldn't even load into the WRE this time - and using a USB installation to run the WRE had the same errors as the original issue. I'm starting to suspect that there may be a larger issue like a motherboard or power supply failure that caused the original crash.

Regardless, I ran the above commands - or tried to at least. Rebuildbcd identifies the installation on the original drive, but when I try to add it to the boot list I get "the system cannot find the path specified". Fixmbr "completed successfully" and fixboot returned "access is denied" although I'm not sure it's actually doing anything if it couldn't add the installation to the list.

Interestingly when I try to boot into the old drive after trying the above, I get briefly "An unexpected I/O error has occurred...

/windows/system32/winload.efi
Error code: 0xc00000e9"

Before it shuts down automatically.
 
It certainly seems odd that both drives appear to have now failed, especially when one of the drives was new. Do you have another motherboard you can use or know anyone which may be able to provide you with one to borrow? I'm just thinking, if you use Hiren's Boot CD to get any important files from one of the drives, perform a clean install on it and then use if the installation becomes corrupt again?

There is a guide which proposes recreating the EFI partition again - FIX bootrec /FixBoot Access is denied error on Windows 11/10
 
bobmanzoidzo said:
Interestingly when I try to boot into the old drive after trying the above, I get briefly "An unexpected I/O error has occurred...

/windows/system32/winload.efi
Error code: 0xc00000e9"

Before it shuts down automatically.
Click to expand...
That appears to be a generic I/O exception thrown by the file system filter driver to allow the operating system to shut down gracefully. The installation is certainly corrupt and I suspect that there is an underlying hardware fault somewhere.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top