SFC stopped at 15% now at 18%...

Status
Not open for further replies.
Hello again!

First the result of the SFCfix script operation:

----------------
SFCFix version 3.0.1.0 by niemiro.
Start time: 2019-01-28 20:48:33.781
Microsoft Windows 10 Build 17763 - amd64
Using .zip script file at C:\Users\Robert\Desktop\SFCFix.zip [0]

PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.17763.1_none_0a18eccab82c677e\MSDTC.LOG

Successfully copied file C:\Users\Robert\AppData\Local\niemiro\Archive\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.17763.1_none_0a18eccab82c677e\MSDTC.LOG to C:\WINDOWS\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.17763.1_none_0a18eccab82c677e\MSDTC.LOG.

Successfully restored ownership for C:\WINDOWS\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.17763.1_none_0a18eccab82c677e\MSDTC.LOG
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.17763.1_none_0a18eccab82c677e\MSDTC.LOG
PowerCopy:: directive completed successfully.

Successfully processed all directives.
SFCFix version 3.0.1.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2019-01-28 20:48:34.056
Script hash: YF4Iwq4ZzUPpjgxO1qjFJIrYZnRoCIIkiIwy/Csf+ao=
----------------------EOF-----------------------

However, the next steps failed:

----------------------------
PS C:\Users\Robert> sfc /scannow

Beginning system scan. This process will take some time.

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

Windows Resource Protection could not perform the requested operation.
PS C:\Users\Robert>

The at the prompt I copied in: %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"

PS C:\Users\Robert> %windir%\logs\cbs\cbs.log : The module '%windir%' could not be loaded. For more information, run 'Import-Module
%windir%'.
At line:1 char:1
+ %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
+ ~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (%windir%\logs\cbs\cbs.log:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CouldNotAutoLoadModule

PS C:\Users\Robert>
----------------------------

So I uploaded via sendspace the CBS.log file: Download CBS.log from Sendspace.com - send big files the easy way
 
Hi Dorcom

I have a question - Please confirm if this is a cloned system.

Also please do another process monitor trace

Step#1 - Capture Process Monitor Trace
 1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Open an elevated Command Prompt and run sfc /scannow just like you have in the past.
3. Stop Process Monitor as soon as SFC fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
11908d1430506241-windows-updates-fail-repeatedly-stop-jpg


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 the LogFile.PML file as well as your CBS.log and upload to SendSpace and post the link.
 
Hello Bruce 1270

nope, I installed this via a USB3 on a freshly delivered blnk bare-bones two years ago.
All worked well and SFC never had an issue running.
It found now and then some errors corrected them and everything was hunky-dory.

The problem started somewhere in September or October.
No to odd though, when you Google "SFC stops at 18%" you get a gazillion returns!
It appears to be a fairly common problem and as usual M$ not caring much about it Or you get some irrelevant blah answer "support" on their forum..

There is one thing that I changed/upgraded around in late September early October Up to then I was running on the Intel integrated graphics 530. I then upgraded to Nvidia GTX 1070 Ti.
Prior to that the only hardware change was replacing a 2 TB Seagate HDD, which is my drive Z: "Media server" containing video clips, music etc., whose reliability suddenly dropped to 13%. That was around mid to late August.
Other than that the only hardware added was a Inateck Superspeed 7 Ports PCI-E to USB 3.0 Expansion Card and they USB3 pluggable Bluetooth 4.0 device transmitter.

The Samsung EVO 960 is my original boot and apps drive C:.
Hard disk sentinel reports its health at 90% after two years (426 days) of operation. It is regularly and automatically trimmed and once in a while I do with throughput performance test which shows more or less the same results as when I got it.

I don't know if this is the cause but recently I was thinking why do I not eliminate all the variables and take this video and USB3 card out and run it off the integrated one again and then run SFC and see what happens.
The only other upgrade and change to the system hardware I did was a couple weeks ago doubling my RAM from 16 GB to 32 GB. But at that time the SFC issue was already present.

I will perform your suggested process monitor step later on and send you by a sense space the requested files. (Would you like to have a fresh and smaller CBS.log?)
I also like to add that I booted the system once in safe mode and ran system file check but encountered the same issue.

D
 
Please do the following

FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.

Then

Retrieve Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
4. The file will likely be too large to upload here so please upload to sendspace and just provide the link here.

Also thank you for the information regarding your hardware. The issue is not due to the amount of RAM installed.
 

Attachments

Please run the followng script.

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.



  1. Please download the file SFCFix.zip to your desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  2. Save any open documents and close all open windows.
  3. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  4. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  5. SFCFix will now process the script.
  6. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  7. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put tags around the log to break up the text.



Then do the following

SFC Scan

1. To open an elevated command prompt, use the Windows+X keyboard combination.
2. From the menu returned, click on Command Prompt (Admin). Accept any UAC prompts.
3. When command prompt opens, copy and paste the following command into it, press enter

sfc /scannow

Wait for this to finish before you continue

4. copy and paste %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
5. 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 to SendSpace and just provide the link here.

If the SFC scan does not complete successfully zip up and post the CBS log.
 

Attachments

SFCFix version 3.0.1.0 by niemiro.
Start time: 2019-02-02 14:05:28.735
Microsoft Windows 10 Build 17763 - amd64
Using .zip script file at C:\Users\Robert\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\winsxs\Temp\InFlight

Successfully created directory tree \\?\C:\WINDOWS\winsxs\Temp\InFlight\b944cefd12afd401381d0000980edc32\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.17763.1_none_0a18eccab82c677e.

Successfully copied file C:\Users\Robert\AppData\Local\niemiro\Archive\Temp\InFlight\b944cefd12afd401381d0000980edc32\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.17763.1_none_0a18eccab82c677e\MSDTC.LOG to C:\WINDOWS\winsxs\Temp\InFlight\b944cefd12afd401381d0000980edc32\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.17763.1_none_0a18eccab82c677e\MSDTC.LOG.

Successfully restored ownership for C:\WINDOWS\winsxs\Temp\InFlight
Successfully restored permissions on C:\WINDOWS\winsxs\Temp\InFlight
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.1.0 by niemiro has completed.
Currently storing 3 datablocks.
Finish time: 2019-02-02 14:05:29.892
Script hash: /4kdywVVWQX00/boNslzfi/Fc6pF9ICSXxHYvKJbwtM=
----------------------EOF-----------------------

SOS.... ;-(
CBS.log https://www.sendspace.com/file/ox5p1s
 
Please do 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.

Download SFCFix.exe (by niemiro) and save this to your Desktop.



  1. Please download the file SFCFix.zip to your desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  2. Save any open documents and close all open windows.
  3. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  4. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  5. SFCFix will now process the script.
  6. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  7. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put tags around the log to break up the text.
 

Attachments

As per your directions, here it is:
Code: 
SFCFix version 3.0.1.0 by niemiro.
Start time: 2019-02-04 12:35:30.586
Microsoft Windows 10 Build 17763 - amd64
Using .zip script file at C:\Users\Robert\Desktop\SFCFix.zip [1]




FileScan::
[0: 1] C:\FRST\Quarantine\C\WINDOWS\winsxs\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.17763.1_none_0a18eccab82c677e\MSDTC.LOG
File is untraceable.
 Found: Q4htnI+yK+Jo0DJugTfqjq40IHkXFkIWyyAaDjFGEvo=
 Version number not available.
Trace not available.



[1: 1] C:\Windows\WinSxS\Temp\InFlight\b944cefd12afd401381d0000980edc32\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.17763.1_none_0a18eccab82c677e\MSDTC.LOG
File is untraceable.
 Found: Q4htnI+yK+Jo0DJugTfqjq40IHkXFkIWyyAaDjFGEvo=
 Version number not available.
Trace not available.



[2: 1] C:\SFCFix\Backups\C\WINDOWS\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.17763.1_none_0a18eccab82c677e\MSDTC.LOG
File is untraceable.
 Found: Q4htnI+yK+Jo0DJugTfqjq40IHkXFkIWyyAaDjFGEvo=
 Version number not available.
Trace not available.



[3: 1] C:\Windows\WinSxS\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.17763.1_none_0a18eccab82c677e\MSDTC.LOG
File is untraceable.
 Found: Q4htnI+yK+Jo0DJugTfqjq40IHkXFkIWyyAaDjFGEvo=
 Version number not available.
Trace not available.
FileScan:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.1.0 by niemiro has completed.
Currently storing 3 datablocks.
Finish time: 2019-02-04 12:35:33.600
Script hash: TdRs5Q7zrBJu7oV05xMCtYsDjHgxuMHHR+qdplcopMc=
----------------------EOF-----------------------
 
Hi

Please do the following

Export Manifest file

1. Please navigate to C:\WINDOWS\winsxs\Manifests
 2. Locate the manifest file called amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.17763.1_none_0a18eccab82c677e.manifest
3. Right Click on this file and Select Send To... Compressed (Zipped) folder
4. Click on Yes to the message to save to Desktop
5. Attach the file to your next post
 
Please do the following

Step#1 - Capture Process Monitor Trace
 1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Open an elevated Command Prompt and run sfc /scannow just like you have in the past.
3. Stop Process Monitor as soon as SFC fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
11908d1430506241-windows-updates-fail-repeatedly-stop-jpg


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 attach the LogFile.PML file as well as your CBS.log.
 
As per your instructions here are the two files zipped up in one:
Download LOG & CBS.zip from Sendspace.com - send big files the easy way

PS: I'm curious would you mind to share what your findings and insights are so far trying to conquer and solve this problem?

PPS: My join date to this forum in November 2018 is kinda suggestive to the fact that the problem started to occur likely after the October update with which I was lucky having used the first edition that became known to delete files. Fortunately I was not affected by this as I store all my data on a partition D:

I also observed a phenomenon since then which I somewhere describe as a "hangy" behavior. Don't know if it's related to the issue but if the machine idles away for a couple of days it shows a very sluggish kind of "gummy" behavior with some disk I/O as if it is looking for something. Suddenly opening just about any app or closing documents or app has some additional disk I/O and takes longer.

I also want to note that the system is protected by ESET and is virus/malware free.
 
Hi Dorcom

Since the upgrade to the website we are having a few technical issues and at present I am unable to access my training thread with my instructor. This should hopefully be resolved very soon and I apologise for the delay.
 
Hi Dorcom


PS : I'm curious would you mind to share what your findings and insights are so far trying to conquer and solve this problem?
Click to expand...

Absolutely. Were at the moment checking disk health and integrity to rule out any hardware/system integrity issues. When SFC fails it can also be that store directories are missing so it's then a case of tracking down the issue.

I would like you to run a CHKDSK

Run CHKDSK


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 command into it, press enter

Chkdsk /r C:

4.A prompt that asks whether you want to schedule the disk to be checked the next time you restart the system. Click Yes to schedule this check.
5.Reboot your system to let CHKDSK run.

Once CHKDSK completes you can post the log using the following tool.

Scan with ListChkDskResult

Please download ListChkDskResult by SleepyDude and save it to your desktop.
Right-click on
ListChkdskResult.png
icon and select Run as Administrator to start the tool.
A message about checking Windows Event Log will pop-up. Click OK.
Wait patiently until a notepad window will open. This won't take long.
The displayed logfile will be also saved to your desktop as ListChkDskResult.txt.
Please include the content of this file in your next reply.
 
FYI: Email notification for new posts received seems to not be working any longer after recent maintenance/upgrade of Sysnative forum server.
The preceding message I only found since I logged in wondering why I heard not back from you for a while. No email notification was received unlike previously.
 
The email notifications stopping has been a recurring issue at times. I've had the same issue, best to keep logging in to check. You should also see new notifications in the top right corner if there has been a reply.

Please run an FRST check and post the logs

Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: Download the 64 bit version.
  1. Right click on the file and select run as administrator (if you don't have this option just double click the file to run it). When the tool opens click Yes to disclaimer.
  2. Press Scan button.
  3. It will produce a log called FRST.txt in the same directory the tool is run from (this should be your desktop).
  4. Please copy (CTRL + C) and paste (CTRL + V) the FRST.txt log back here.
  5. The first time the tool is run it generates another log Addition.txt - also located in the same directory as FRST64.exe.
  6. Please also paste that along with the FRST.txt into your reply.
Note: Please do not attach any logs unless specifically requested. It's easier if you simply copy and paste them into your reply. It's OK if you have to use more than one post to do so.
 
Status
Not open for further replies.

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

Back
Top