DISM Source Files not found/SFC corruption

forceroast · Nov 12, 2019

I'm unable to apply Windows Updates. Anything that requires the Windows Module Installer fails. Tried an in place repair that also failed.

SFC /scannow fails at 83% with an error of "Windows Resource Protection could not perform the requested operation."

Dism /Online /Cleanup-Image /RestoreHealth fails "The source files could not be found."

SFCFIX gets a DISM error of Error: 0x800f081f

Windows 10
Ver 1607

CBS logs are attached. Any insight is appreciated.

Thanks!

Sysnative Windows Update · Nov 12, 2019

Hello and welcome!

GSmartControl
Follow the instructions below to check your SMART status with GSmartControl:

Download the portable version of GSmartControl and save it on your Desktop;
Extract the zip file to your Desktop. Open the folder gsmartcontrol-1.1.3-win64 which should be located on your Desktop and double-click gsmartcontrol.exe to launch the program.
Identify your drive in the list (if recognized by the tool), and hover your mouse over it.
You should see something called: SMART status. It will either read: Enabled, in which case you should do the following:
Double-click on it to bring up its window (usually you'll find your drive by its size or its brand name);
Go to the Self-Tests tab, then select Extended Self-test in the Test type drop-down list and click on Execute (this test can take a few hours to complete);
Once the test is over, the results will be displayed at the bottom of the window. Please copy and paste these results in your next reply or take a screenshot;
Also, go in the Attributes tab and if you have any entries highlighted in red or pink, take a screenshot of the GSmartControl window and attach it in your next reply;
Please note: If the SMART Status reads: Unsupported, stop and let me know.

forceroast · Nov 12, 2019

Nothing in red on the attributes.

Extended offline and short offline tests completed with no errors

Sysnative Windows Update · Nov 12, 2019

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a file should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

Step#2 - DISM /RestoreHealth Scan
Warning:this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

Right-click on the Start button and select Command Prompt (Admin)
When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
Dism /Online /Cleanup-Image /RestoreHealth
Once it finishes, copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead.
copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread.
Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.

forceroast · Nov 12, 2019

SFCFIX logs below. DISM failed again at 92.9% with "The source files could not be found." CBS log is attached

Code:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2019-11-12 21:24:05.000
Microsoft Windows 10 Build 14393 (Updates Deferred) - amd64
Using .zip script file at C:\Users\user\Downloads\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\windows\WinSxS\x86_wcf-m_svc_mon_sup_dll_31bf3856ad364e35_10.0.14393.953_none_838aa3ac31353fb3\ServiceMonikerSupport.dll
Successfully took permissions for file or folder C:\windows\WinSxS\amd64_wcf-m_svc_mon_sup_dll_31bf3856ad364e35_10.0.14393.953_none_dfa93f2fe992b0e9\ServiceMonikerSupport.dll

Successfully copied file C:\Users\user\AppData\Local\niemiro\Archive\WinSxS\x86_wcf-m_svc_mon_sup_dll_31bf3856ad364e35_10.0.14393.953_none_838aa3ac31353fb3\ServiceMonikerSupport.dll to C:\windows\WinSxS\x86_wcf-m_svc_mon_sup_dll_31bf3856ad364e35_10.0.14393.953_none_838aa3ac31353fb3\ServiceMonikerSupport.dll.
Successfully copied file C:\Users\user\AppData\Local\niemiro\Archive\WinSxS\amd64_wcf-m_svc_mon_sup_dll_31bf3856ad364e35_10.0.14393.953_none_dfa93f2fe992b0e9\ServiceMonikerSupport.dll to C:\windows\WinSxS\amd64_wcf-m_svc_mon_sup_dll_31bf3856ad364e35_10.0.14393.953_none_dfa93f2fe992b0e9\ServiceMonikerSupport.dll.

Successfully restored ownership for C:\windows\WinSxS\x86_wcf-m_svc_mon_sup_dll_31bf3856ad364e35_10.0.14393.953_none_838aa3ac31353fb3\ServiceMonikerSupport.dll
Successfully restored permissions on C:\windows\WinSxS\x86_wcf-m_svc_mon_sup_dll_31bf3856ad364e35_10.0.14393.953_none_838aa3ac31353fb3\ServiceMonikerSupport.dll
Successfully restored ownership for C:\windows\WinSxS\amd64_wcf-m_svc_mon_sup_dll_31bf3856ad364e35_10.0.14393.953_none_dfa93f2fe992b0e9\ServiceMonikerSupport.dll
Successfully restored permissions on C:\windows\WinSxS\amd64_wcf-m_svc_mon_sup_dll_31bf3856ad364e35_10.0.14393.953_none_dfa93f2fe992b0e9\ServiceMonikerSupport.dll
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2019-11-12 21:24:05.465
Script hash: WjWsDu85sq8o7c7lEg6RUpiSGGOBcIFO+ziaRKsbHe0=
----------------------EOF-----------------------

Sysnative Windows Update · Nov 12, 2019

Please do the following:

Step#1 - ChkDsk Scan/Repair
1. Right-click your Start button and select Command Prompt (Admin). Answer Yes to allow if the User Account Control dialog comes up.
2. You should now have a black window open that you can type in to.
3. Please type chkdsk /r and then press enter. Note: There is a space after the command chkdsk and before the forward slash
4. You will get a prompt telling you chkdsk cannot run because the volume is in use. Answer Y and hit enter to schedule the run at next boot. Reboot your machine.
5. Chkdsk will start to run. Please allow it to finish. You will know it is running when you see text as follows.
View attachment 46285

6. Download ListChkdskResult.exe by SleepyDude and save it on your desktop. If it's already downloaded to your desktop, just skip this step.
7. Right-click this file and select Run as administrator (Allow if prompted) and a text file will open (and also be saved on the desktop as ListChkdskResult.txt).
Please copy the contents of this file and paste into your next post.

forceroast · Nov 13, 2019

Done.

Code:

ListChkdskResult by SleepyDude v0.1.7 Beta | 21-09-2013

------< Log generate on 11/12/2019 11:03:54 PM >------
Category: 0
Computer Name: PC
Event Code: 1001
Record Number: 585709
Source Name: Microsoft-Windows-Wininit
Time Written: 11-13-2019 @ 04:58:18
Event Type: Information
User:
Message:

Checking file system on C:
The type of the file system is NTFS.
Volume label is Windows8_OS.

A disk check has been scheduled.
Windows will now check the disk.                         

Stage 1: Examining basic file system structure ...
  617984 file records processed.                                                       

File verification completed.
  22453 large file records processed.                                   

  0 bad file records processed.                                     


Stage 2: Examining file name linkage ...
  779822 index entries processed.                                                       

Index verification completed.
  0 unindexed files scanned.                                       

  0 unindexed files recovered to lost and found.                   


Stage 3: Examining security descriptors ...
Cleaning up 377 unused index entries from index $SII of file 0x9.
Cleaning up 377 unused index entries from index $SDH of file 0x9.
Cleaning up 377 unused security descriptors.
Security descriptor verification completed.
  80920 data files processed.                                           

CHKDSK is verifying Usn Journal...
  35461032 USN bytes processed.                                                           

Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
  617968 files processed.                                                               

File data verification completed.

Stage 5: Looking for bad, free clusters ...
  3238857 free clusters processed.                                                       

Free space verification is complete.

Windows has scanned the file system and found no problems.
No further action is required.

 235113471 KB total disk space.
 221135564 KB in 455220 files.
    289024 KB in 80921 indexes.
         0 KB in bad sectors.
    733451 KB in use by the system.
     65536 KB occupied by the log file.
  12955432 KB available on disk.

      4096 bytes in each allocation unit.
  58778367 total allocation units on disk.
   3238858 allocation units available on disk.

Internal Info:
00 6e 09 00 95 2d 08 00 21 ee 0e 00 00 00 00 00  .n...-..!.......
d3 1a 00 00 ab 42 00 00 00 00 00 00 00 00 00 00  .....B..........

Windows has finished checking your disk.
Please wait while your computer restarts.

Sysnative Windows Update · Nov 13, 2019

Let's see what SFC has to say:

SFC Scan

Click on the Start button and in the search box, type Command Prompt
When you see Command Prompt on the list, right-click on it and select Run as administrator
When command prompt opens, copy and paste the following commands into it, press enter after each

sfc /scannow

Wait for this to finish before you continue

copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

forceroast · Nov 13, 2019

CBS log attached. SFC failed at 83% again

Code:

C:\windows\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 83% complete.

Windows Resource Protection could not perform the requested operation.

Sysnative Windows Update · Nov 13, 2019

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try running SFC just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.

4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or SendSpace.

forceroast · Nov 13, 2019

The process monitor log is 2.5GB. Not sure I have the bandwidth to upload that somewhere currently. Are there any alternatives?

Sysnative Windows Update · Nov 13, 2019

Zipping it up should reduce the size significantly.

Search

Search

DISM Source Files not found/SFC corruption

forceroast

Member

Attachments

Sysnative Windows Update

Inactive

forceroast

Member

Sysnative Windows Update

Inactive

Attachments

forceroast

Member

Attachments

Sysnative Windows Update

Inactive

forceroast

Member

Sysnative Windows Update

Inactive

forceroast

Member

Attachments

Sysnative Windows Update

Inactive

forceroast

Member

Sysnative Windows Update

Inactive