[SOLVED] W10pro sfc, dism, sfcfix all failing

T

tns1

Active member
Joined
Jan 5, 2018
Posts
44
W10Pro x64 1803 17134.1

Attempts to install KB4103721 cumulative update has failed over 10 times both as an automatic install and a manual (msu) install. 'Some update files are missing or have problems. We'll try to download the update again later. Error 0x80073712'.

A 2nd cumulative update KB4284835 is also failing too, but other updates continue to install fine.

To diagnose I ran sfc /scannow a few times, and it finds problems and can not fix or complete.
Next I ran DISM with the /scanhealth and /checkhealth options, and it reported that the system should be repairable.
Next I ran DISM /Online /Cleanup-Image /RestoreHealth, but it could not find the necessary source files for the repair.
I then used the media creator to download a new W10x64 17134 ISO file, and copied that install.esd to c:\.
I also converted this esd to an install.wim to try that too, since some have reported problems with the esd format.

I have tried /restorehealth with both of these install file formats. They both fail around 87%,'The source files could not be found':

C:\>dism /Get-WimInfo /WimFile:C:\install.esd

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Details for image : C:\install.esd

Size : 14,571,793,777 bytes

Index : 6
Name : Windows 10 Pro
Description : Windows 10 Pro
Size : 15,644,048,998 bytes

The operation completed successfully.

C:\>DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\install.wim

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.1

[===========================87.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 Configure a Windows Repair Source | Microsoft Docs.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

I tried SFCFix, but it fails to run "something has gone horribly wrong..."
See attached logs:
 

Attachments

Hello and welcome!

Please start with the following:

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.


  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. 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.


Dropbox - SFCFix.zip

SFC Scan


  1. Click on the Start button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. 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
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
 
Thanks, this seems to have fixed it.


SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-06-14 17:27:52.066
Microsoft Windows 10 Build 17134 - amd64
Using .zip script file at C:\Users\Ann\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_windows-defender-am-sigs_31bf3856ad364e35_10.0.17134.1_none_a2054a6384cba550\MpAvBase.vdm
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_netfx4-microsoft.build.tasks.v4.0_b03f5f7f11d50a3a_4.0.15671.0_none_70de81e29a227660\Microsoft.Build.Tasks.v4.0.dll

Successfully copied file C:\Users\Ann\AppData\Local\niemiro\Archive\winsxs\amd64_windows-defender-am-sigs_31bf3856ad364e35_10.0.17134.1_none_a2054a6384cba550\MpAvBase.vdm to C:\WINDOWS\winsxs\amd64_windows-defender-am-sigs_31bf3856ad364e35_10.0.17134.1_none_a2054a6384cba550\MpAvBase.vdm.
Successfully copied file C:\Users\Ann\AppData\Local\niemiro\Archive\winsxs\amd64_netfx4-microsoft.build.tasks.v4.0_b03f5f7f11d50a3a_4.0.15671.0_none_70de81e29a227660\Microsoft.Build.Tasks.v4.0.dll to C:\WINDOWS\winsxs\amd64_netfx4-microsoft.build.tasks.v4.0_b03f5f7f11d50a3a_4.0.15671.0_none_70de81e29a227660\Microsoft.Build.Tasks.v4.0.dll.

Successfully restored ownership for C:\WINDOWS\winsxs\amd64_windows-defender-am-sigs_31bf3856ad364e35_10.0.17134.1_none_a2054a6384cba550\MpAvBase.vdm
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_windows-defender-am-sigs_31bf3856ad364e35_10.0.17134.1_none_a2054a6384cba550\MpAvBase.vdm
Successfully restored ownership for C:\WINDOWS\winsxs\amd64_netfx4-microsoft.build.tasks.v4.0_b03f5f7f11d50a3a_4.0.15671.0_none_70de81e29a227660\Microsoft.Build.Tasks.v4.0.dll
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_netfx4-microsoft.build.tasks.v4.0_b03f5f7f11d50a3a_4.0.15671.0_none_70de81e29a227660\Microsoft.Build.Tasks.v4.0.dll
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2018-06-14 17:27:57.131
Script hash: h3UJBsM+ty++vT3KPfRbnRnKIddkjcME+NH7qFgKrE4=
----------------------EOF-----------------------
 

Attachments

Great, please do the following:

Step#1 - 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.


  1. Right-click on the Start button and select Command Prompt (Admin)
  2. 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
  3. 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"
  4. 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 and just provide the link.
 
No, DISM still reports that it could not find the needed source files, even when specifying a matching ISO image as source.
BTW, the same cumulative update failed again.
 

Attachments

Don't attempt to install anything until I tell you to. You have 600 files to be replaced and since it is 4.30 A.M. here, I'm calling it a day and going to sleep.

I'll start preparing a fix some time tomorrow and post back.

Have a good night.
 
softwaremaniac said:
Don't attempt to install anything until I tell you to. You have 600 files to be replaced and since it is 4.30 A.M. here, I'm calling it a day and going to sleep.

I'll start preparing a fix some time tomorrow and post back.

Have a good night.
Click to expand...

Thanks. 600 files sounds like a lot for a system that is otherwise working fine. I am not against doing a windows reset or clean install if it makes more sense.
 
softwaremaniac said:
Has your hardware been tested?
Click to expand...

When I first purchased this used PC, I had a few occasions where it would go to the automatic repair black screen. I eventually put in a new HD and SATA cable, and did a clean install of w10p about a year ago. I have done several memory and disk tests. Crystaldisk shows this HD to be clean (all green), and chkdsk /r showed no bad sectors. Yesterday I had a bluescreen Stopcode (ntfs error) which recovered automatically, so I can believe it is possible the HD is fine but maybe the MB or disk controller has an intermittent issue. If so, it would be nice to have a diagnostic that could pinpoint the problem. I did have to remove a virus a few months ago using the BleepingComputer site, but quick scans show the PC to be clean.

I can perform a more in depth virus scan or HW inspection, or just apply the file repairs you provide. Just let me know. I had not done the DISM repair before on any PC, and had just relied on sfc. I am not clear on what repositories are used by each, and why they would disagree.
 
GSmartControl
Follow the instructions below to test your hard drive health with GSmartControl:


  • Download GSmartControl and save it on your Desktop;
  • Execute gsmartcontrol.exe; Let the install complete and launch the programme.
  • Identify your drive in the list, and double-click on it to bring up it's window (usually you'll find your drive by it's size or it's brand name);
  • Go in the Perform 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;
  • 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;
    info_failing.png

​
 
The extended test aborted part way though. The attribute screen shows no failures, but there were several uncorrectable data errors.
I'll change the PC power settings to make sure it doesn't sleep and try again.
 

Attachments

  • GSC1b.jpg
    GSC1b.jpg
    184.7 KB · Views: 1
  • GSC1c.jpg
    GSC1c.jpg
    194.1 KB · Views: 4
OK, now that I prevented the PC from going to sleep, the extended test completed without error.
The uncorrectable data errors are still present in the log, but I suspect that just means that one area of the disk has or had scrambled data. It isn't saying the sector is bad.
 

Attachments

  • GSC2b.jpg
    GSC2b.jpg
    184.2 KB · Views: 6
softwaremaniac said:
No, it is saying that many sectors are bad. Your HDD is likely bad. Please also test with SeaTools.
Click to expand...

Seatools tests (all of them) found nothing wrong, but I did an extended memory test and found a consistently bad RAM address even after cleaning and trying different slots. I'll be fixing that before I pursue the disk issue further.
 
Once I fix the memory, I plan on erasing (zero fill) the drive to force it to allocate spare sectors for any questionable ones, and to update the reallocated sector count. Right now it still says 0 reallocated sectors, but 80 have uncorrectable data. Apparently bad sectors are only identified/reassigned during writes.

The HD I replaced didn't show bad sectors either, but every month or two the system would need to do an automatic repair as if the drive was failing. Since the behavior continues with this almost new HD, I suspect something other than the HD as the main issue. The bad memory stick is an easy fix. I may also pull the MB to make sure the SATA pins are soldered well, and put a scope on the power to make sure it is clean.
 
Electrical checks show power rail noise to be similar to another (same model) PC. After fixing the memory, I did a clean install on a new (same model) HD and ran the SMART tests. I then erased the suspect HD and did the same. I did several check/fixes including sfc, dism, chkdsk, and HD scans from different tools. No bad or reallocated sectors were found. The other SMART items that seem high (read error rate, seek error rate), were also high on the new HD.

Uncorrectable Errors (code 187) is still showing the same raw count of 80, even after all this activity. This article suggests that a code 187 value this high is usually very predictive of HD failure: Using SMART to accurately predict when a hard drive is about to die - ExtremeTech.

Everything still points to the platters being fine, but there is some other issue such as the SATA connections, or possibly there was a one-time power or shock event. Nothing critical going on with this PC, so I will replace the SATA cable and keep the HD in service for now.
 
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