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

Status
Not open for further replies.
D

dorcom

Banned
Joined
Nov 4, 2018
Posts
34
A few months ago I noticed a sluggish performance as if the system is searching for something.
So I ran DISM followed by SFC.
While DISM apparently completed, SFC however, produced the following error message:

--------------------------------------------
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.

C:\WINDOWS\system32>
--------------------------------------------

I tried Image Health SFCFix but that too apparently found nothing wrong. (Maybe I am using it wrong).

The CBS.log file shows besides several overlap/duplicate ownership errors the following that causes in my opinion the stop :

2019-01-13 22:10:11, Info CSI 00000d2b [SR] Beginning Verify and Repair transaction
2019-01-13 22:10:12, Error CSI 00000d2c@2019/1/14:06:10:12.067 (F) onecore\base\wcp\componentstore\deltastore.cpp(3065): Error STATUS_INVALID_PARAMETER originated in function ComponentStore::CRawStoreLayout::ecompressFile expression: Parameter check failed
[gle=0x80004005]
2019-01-13 22:10:12, Info CBS Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]
2019-01-13 22:10:12, Info CBS Could not get file name for current session file logging [HRESULT = 0x80004003 - E_POINTER]
2019-01-13 22:10:12, Info CBS Added C:\WINDOWS\Logs\CBS\CBS.log to WER report.
2019-01-13 22:10:12, Info CBS Added C:\WINDOWS\Logs\CBS\CbsPersist_20190110123421.cab to WER report.
2019-01-13 22:10:12, Info CBS Added C:\WINDOWS\Logs\CBS\CbsPersist_20190110025554.cab to WER report.
2019-01-13 22:10:12, Info CBS Added C:\WINDOWS\Logs\CBS\CbsPersist_20190105212559.cab to WER report.
2019-01-13 22:10:12, Info CBS Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2019-01-13 22:10:12, Info CBS Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2019-01-13 22:10:12, Info CBS Not able to add poqexec.log to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2019-01-13 22:10:12, Info CBS Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2019-01-13 22:12:12, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP

(There is more towards the very end as well [excerpt]:

2019-01-13 22:37:55, Info CBS Universal Time is: 2019-01-14 06:37:55.000
2019-01-13 22:37:55, Info CBS Loaded Servicing Stack v10.0.17763.164 with Core: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17763.164_none_7e114a3d4d0589d4\cbscore.dll
2019-01-13 22:37:55, Info CBS Build: 17763.1.amd64fre.rs5_release.180914-1434
2019-01-13 22:37:55, Info CSI 00000001@2019/1/14:06:37:55.03 WcpInitialize: wcp.dll version 10.0.17763.164 (WinBuild.160101.0800)
2019-01-13 22:37:55, Info CBS Lock: New lock added: CCbsSessionManager, level: 11, total lock:8
2019-01-13 22:37:55, Info CBS Lock: New lock added: CSIInventoryCriticalSection, level: 64, total lock:9
2019-01-13 22:37:55, Info CBS NonStart: Set pending store consistency check.
2019-01-13 22:37:55, Info CBS Session: 30714835_2923043944 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
2019-01-13 22:37:55, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2019-01-13 22:37:55, Info CBS Failed to create open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2019-01-13 22:37:55, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2019-01-13 22:37:55, Info CBS Session: 30714835_2923064009 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
2019-01-13 22:37:55, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2019-01-13 22:37:55, Info CBS Failed to create open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2019-01-13 22:37:55, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]

How can I fix that and resolve the SFC stop issue?

You help is very much appreciated nd I thank in advance for help.
(The relevant files (..\Logs\CBS\WER report) are here: Log Files)

Rob

OS: Win10Pro V. 1909 Build 17763.253
 
Hello and welcome!

Due to the precise nature of your corruption, you will receive help from a user named Bruce1270. He's one of our senior trainees here who's in his final phase of his studies and needs to gain some real world experience in specific areas of Windows Update. This means that he'll be assisting you, but that I will first need to double check and approve his fixes before he posts them to you. If anything this is a good thing for you because it means that you've got at least two of us watching over your thread, but it will unfortunately add a slight delay between each reply. I hope that you understand and can accept the need for us to train up new members in this way in order to carry on doing what we do here, however, if for any reason you object to this setup, I will happily take on your thread myself.

Thank you very much for your understanding. We'll be with you very shortly.
 
softwaremaniac said:
Hello and welcome!

Due to the precise nature of your corruption, you will receive help from a user named Bruce1270. He's one of our senior trainees here who's in his final phase of his studies and needs to gain some real world experience in specific areas of Windows Update. This means that he'll be assisting you, but that I will first need to double check and approve his fixes before he posts them to you. If anything this is a good thing for you because it means that you've got at least two of us watching over your thread, but it will unfortunately add a slight delay between each reply. I hope that you understand and can accept the need for us to train up new members in this way in order to carry on doing what we do here, however, if for any reason you object to this setup, I will happily take on your thread myself.

Thank you very much for your understanding. We'll be with you very shortly.
Click to expand...

Thank you for your reply.
Sure! Either way, if I can be helped resolving the issue!

Do
 
Hello, my name is Bruce1270 and I shall be assisting you.

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.
 
bruce1270 said:
Hello, my name is Bruce1270 and I shall be assisting you.

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.
Click to expand...

Hello there!
Thanks for your reply.
The PM link has a 404 but I had a current copy (V 3.5) of the app.
As per your request file (CBS & PML log.zip) attached. (Huge!)
Let me know you got it all.

Do
 
Hi

I don't seem to have got it.

Please upload to Sendspace, a free file sharing service and post the link.
 
Hi Dorcom

I haven't heard from you for a while. Are you still needing assistance?
 
Hello again!
I had to find the message link. Realized that I can see this in the sysnative control panel. Will upload in a minute to send space but need an email address sent to.

Do
 
Let's start by checking disk health.

JcJ91sx.png
GSmartControl

Follow the instructions below to test your hard drive health with GSmartControl:



  • Download GSmartControl and save it on your Desktop;
  • Extract the content of the GSmartControl .zip archive and execute gsmartcontrol.exe; To extract you can right-click your mouse on the GSmartControl.zip file and select Extract.
  • 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, copy and paste their name in your next reply (or take a screenshot of the GSmartControl window and attach it in your next reply);
    info_failing.png
 
Prior to contacting you I did a thorough chkdsk /f /r of c:
sfc seemed not affected, stopped again @ 18%

GsmartControl: (tried with updated driver dB)
Drive C: [does not] show. "Unknown Model"
Dbl click = "Non additional information is available for this device"

Show output is:

smartctl 6.6 2017-11-05 r4594 [i686-w64-mingw32-w10(64)-b17763] (sf-6.6-1)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, smartmontools

=== START OF INFORMATION SECTION ===
Model Number: Samsung SSD 960 EVO 500GB
Serial Number: S3EUNX0HC01205J
Firmware Version: 3B7QCXE7
PCI Vendor/Subsystem ID: 0x144d
IEEE OUI Identifier: 0x002538
Total NVM Capacity: 500,107,862,016 [500 GB]
Unallocated NVM Capacity: 0
Controller ID: 2
Number of Namespaces: 1
Namespace 1 Size/Capacity: 500,107,862,016 [500 GB]
Namespace 1 Utilization: 182,946,406,400 [182 GB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: 002538 5c61b01126
Local Time is: Fri Jan 25 13:01:26 2019 PST
Firmware Updates (0x16): 3 Slots, no Reset required
Optional Admin Commands (0x0007): Security Format Frmw_DL
Optional NVM Commands (0x001f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat
Maximum Data Transfer Size: 512 Pages
Warning Comp. Temp. Threshold: 77 Celsius
Critical Comp. Temp. Threshold: 79 Celsius

Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 6.04W - - 0 0 0 0 0 0
1 + 5.09W - - 1 1 1 1 0 0
2 + 4.08W - - 2 2 2 2 0 0
3 - 0.0400W - - 3 3 3 3 210 1500
4 - 0.0050W - - 4 4 4 4 2200 6000

Supported LBA Sizes (NSID 0x1)
Id Fmt Data Metadt Rel_Perf
0 + 512 0 0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

Another app I have, HD Sentinel, shows this:
HD Sentinel.jpg
 
FYI Bruce1270
Update reply from author of GSmartControl:


Hi Rob,


GSmartControl doesn't support NVMe and PCI-express devices yet.
They behave completely different from (S)ATA devices, so it will
be a while until such support is implemented. It also depends on
smartctl's full JSON support for NVMe which is still in works
(smartctl is developed by smartmontools.org people).


Note that NVMe drives can support self-testing if they implement
NVMe 1.3 specification, but 960 is NVMe 1.2 I think.
There may be a proprietary way to run the tests though (does Samsung
Magician not have them?)
I also don't believe smartctl supports self-testing on NVMe yet.


Cheers,
Alexander


P.S. I myself have 970 EVO so I'm motivated to support it, but
stuff needs to happen before I'm able to.






On Fri, 2019-01-25 at 13:40 -0800, ROB wrote:

Hello Alexander

Sysnative is currently helping me to find an issue I have with SFC stopping at 18% and Windows 10.
Although it has worked the last few months this problem crept up.

Sysnative support "Bruce1270" instructed me to download GSmartcontrol and run an extended self-test.
However, my boot drive C a Samsung SSD 960 EVO does not show in GSmartcontrol. "Unknown model"
I updated the driver database, same result.
A double-click on the icon results in "non-additional information is available for this device"

Another app I have hard disk sentinel V. 5.3 Pro does show some smart information.
For your convenience attached are a few screenshots.

Rob

"show output" I get is this:

smartctl 6.6 2017-11-05 r4594 [i686-w64-mingw32-w10(64)-b17763] (sf-6.6-1)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number: Samsung SSD 960 EVO 500GB
Serial Number: S3EUNX0HC01205J
Firmware Version: 3B7QCXE7
etc...
 
Hi DorCom

At the time of posting the GSmart instructions we weren't aware that your drive was a NVME SSD but thank you for the information. Also please don't double post and await for my reply just in case posts get crossed or something is missed. Thank you. :smile:

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.
 

Attachments

Done
SFC /scannow same old @18% stop.
-------------------------------------------------




SFCFix version 3.0.1.0 by niemiro.
Start time: 2019-01-26 08:24:26.230
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

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

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

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




Successfully processed all directives.
SFCFix version 3.0.1.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2019-01-26 08:24:29.847
Script hash: z7mBGVXThi7heVWn1l/zwgXFj+xSFaJ5tREBVHeqfZo=
----------------------EOF-----------------------
 
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.
 

Attachments

Hello Bruce1270

Did so as per instructions. Here it is:

Fix result of Farbar Recovery Scan Tool (x64) Version: 26.01.2019
Ran by Robert (26-01-2019 18:36:23) Run:1
Running from C:\Users\Robert\Desktop
Loaded Profiles: Robert (Available Profiles: Robert & Administrator)
Boot Mode: Normal
==============================================

fixlist content:
*****************
CreateRestorePoint:
C:\WINDOWS\winsxs\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.17763.1_none_0a18eccab82c677e
*****************

Restore point was successfully created.
C:\WINDOWS\winsxs\winsxs\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.17763.1_none_0a18eccab82c677e => moved successfully

==== End of Fixlog 18:36:35 ====
 
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

Status
Not open for further replies.

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

Back
Top