[SOLVED] SFC Fails | DISM Fails | SFCFix Crashes | What Now?

dvhirst865 · Feb 21, 2019

An SSD crash in early February 2019 resulted in an unloadable Windows 10.1809 Home x64 instance. Running chkdsk c: /f seemed to fix the errors (and at that time, I hadn't read about the /r and /b options for chkdsk, perhaps they would have recovered more data); in any case, Windows 10 still wouldn't load. Recovering the c: drive from a 2 February 2019 backup using Easeus Backup Home resulted in a working system, however sfc /scannow and dism /restore-health both failed to run. I searched for solutions and tried a number of fixes with little to no success. In the search process I found sysnative.com and read through several fix topics to see how the process works. I'm all in (with much gratitude) and now following the process, having registered and provided my RYO system specs. In step 4, SFCFix terminated on an unhandled exception. I ok'd sending a crash dump, and continued to step 5. The zipped CBS log is attached. This is step 6, open a thread topic; I trust this explanation is sufficient. The SFCFix log is copied in below. Thanks for your help.

Update: while preparing the above, I also ran a Malwarebytes stand-alone scan. Despite having Norton installed and operation with no flags, Malwarebytes found two items:

1. malware:yontoo
2. pup:BrowserProtect

I removed both, ran another (clean) Malwarebytes scan, and then re-ran SFCFix. It crashed again, so I OK'd another crash dump and downloaded a fresh copy of SFCFix and ran it a third time. It crashed again, so I OK'd a third crash dump, moved the executable file to the Desktop and ran it a fourth time. It crashed a fourth time, so I OK'd a fourth crash dump and said "enough...". I zipped up a copy of the CBS log folder after the 4th run (CBS.4.zip), copied the original CBS.0 folder into the zip file. It is attached. Also, the SFCFix logs from each run are copied in below. I hope this is sufficient to get started and I'm eager to hear about possible next steps. Thanks.

DVHirst

----SFCFix Log---- Run 1
SFCFix version 3.0.1.0 by niemiro.
Start time: 2019-02-20 21:55:38.112
Microsoft Windows 10 Build 17763 - amd64
Not using a script file.

SFCFix version 3.0.1.0 by niemiro has encountered an unhandled exception.
Currently storing 0 datablocks.
Finish time: 2019-02-20 22:01:26.457
----------------------EOF-----------------------

----SFCFix Log---- Run 2
SFCFix version 3.0.1.0 by niemiro.
Start time: 2019-02-20 22:51:04.743
Microsoft Windows 10 Build 17763 - amd64
Not using a script file.

SFCFix version 3.0.1.0 by niemiro has encountered an unhandled exception.
Currently storing 0 datablocks.
Finish time: 2019-02-20 22:51:22.502
----------------------EOF-----------------------

----SFCFix Log---- Run 3
SFCFix version 3.0.1.0 by niemiro.
Start time: 2019-02-20 22:54:30.371
Microsoft Windows 10 Build 17763 - amd64
Not using a script file.

SFCFix version 3.0.1.0 by niemiro has encountered an unhandled exception.
Currently storing 0 datablocks.
Finish time: 2019-02-20 22:54:39.627
----------------------EOF-----------------------

----SFCFix Log---- Run 4
SFCFix version 3.0.1.0 by niemiro.
Start time: 2019-02-20 22:56:38.872
Microsoft Windows 10 Build 17763 - amd64
Not using a script file.

SFCFix version 3.0.1.0 by niemiro has encountered an unhandled exception.
Currently storing 0 datablocks.
Finish time: 2019-02-20 22:56:46.931
----------------------EOF-----------------------

END copied in material...

Sysnative Windows Update · Feb 22, 2019

Hello and welcome!

Just to clarify, you are now running on the same SSD or on a new one?

dvhirst865 · Feb 22, 2019

Hi, thanks for your response. I have a new SSD which remains in its box, along with two new 2TB SSHDs, also in their boxes. I'd like to get to a clean system, if possible, before implementing new equipment. That, hopefully, leads to fewer potential new issues to sort out.

Additional information from previous activities:

Error code from inplace upgrade using Windows 10.1809 Home .iso:
0x8007001f-0x20006 The installation failed in the SAFE_OS phase with an error during REPLICATE_OC operation
Error report from DISM /Online /Cleanup-Image /RestoreHealth /Source:esd:W:\sources\install.esd:1 /LimitAccess:

Code:

Deployment Image Servicing and Management tool
Version: 10.0.17763.1

Image Version: 10.0.17763.316

[===                        6.4%                           ]
Error: 4448

The WOF driver encountered a corruption in the compressed file's Resource Table.

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

Looking forward to more conversation.

DVH

Sysnative Windows Update · Feb 22, 2019

Hi!

Thanks for additional info. That was a smart move. Now, let me explain what is going on here:

From the CBS.log you have provided, I can see that there are issues with some packages.

Code:

2019-02-16 09:42:51, Info                  CBS    Failed to read in xml content [HRESULT = 0x80071160 - Unknown Error]
2019-02-16 09:42:51, Error                 CBS    Failed to parse package manifest: \\?\C:\WINDOWS\Servicing\Packages\Microsoft-Windows-IIS-WebServer-AddOn-ServerCommon-Package~31bf3856ad364e35~amd64~~10.0.17763.1.mum [HRESULT = 0x80071160 - Unknown Error]
2019-02-16 09:42:51, Info                  CBS    Failed to initialize package: Microsoft-Windows-IIS-WebServer-AddOn-ServerCommon-Package~31bf3856ad364e35~amd64~~10.0.17763.1, from path: \\?\C:\WINDOWS\Servicing\Packages\Microsoft-Windows-IIS-WebServer-AddOn-ServerCommon-Package~31bf3856ad364e35~amd64~~10.0.17763.1.mum, existing package: 1 [HRESULT = 0x80071160 - Unknown Error]
2019-02-16 09:42:51, Info                  CBS    Failed to resolve package [HRESULT = 0x80071160 - Unknown Error]
2019-02-16 09:42:51, Info                  CBS    Failed to check whether this is the real child: Microsoft-Windows-IIS-WebServer-AddOn-ServerCommon-Package~31bf3856ad364e35~amd64~~10.0.17763.1 [HRESULT = 0x80071160 - Unknown Error]
2019-02-16 09:42:51, Info                  CBS    Failed to enumerate updates from child package [HRESULT = 0x80071160 - Unknown Error]
2019-02-16 09:42:51, Info                  CBS    Failed to enumerate updates from child package [HRESULT = 0x80071160 - Unknown Error]
2019-02-16 09:42:51, Info                  CBS    Failed to enumerate updates from child package [HRESULT = 0x80071160 - Unknown Error]
2019-02-16 09:42:51, Error                 CBS    Failed to enumerate all updates. [HRESULT = 0x80071160 - Unknown Error]

In order to fix them, I am going to need to run DISM just as you did before and attach a new CBS.log after it errors out (each new tool run overwrites the log entries of the old one).

From there, I will hopefully be able to provide you with a fix for the packages and go from there.

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.

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.

Please let me know if further clarification is required or if you have additional questions.

dvhirst865 · Feb 22, 2019

That's clear; on it now. And A GREAT BIG THANK YOU for your help.

dvhirst865 · Feb 22, 2019

That's clear; on it now. And A GREAT BIG THANK YOU for your help.

cbs.zip is attached.

Sysnative Windows Update · Feb 22, 2019

Excellent!

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

dvhirst865 · Feb 22, 2019

Here is the result:

Code:

SFCFix version 3.0.1.0 by niemiro.
Start time: 2019-02-22 15:09:29.328
Microsoft Windows 10 Build 17763 - amd64
Using .zip script file at C:\Users\Donald Hirst\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\Servicing\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1.cat
Successfully took permissions for file or folder C:\WINDOWS\Servicing\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1.mum
Successfully took permissions for file or folder C:\WINDOWS\Servicing\Packages\Microsoft-Windows-IIS-WebServer-AddOn-ServerCommon-Package~31bf3856ad364e35~amd64~~10.0.17763.1.cat
Successfully took permissions for file or folder C:\WINDOWS\Servicing\Packages\Microsoft-Windows-IIS-WebServer-AddOn-ServerCommon-Package~31bf3856ad364e35~amd64~~10.0.17763.1.mum
Successfully took permissions for file or folder C:\WINDOWS\Servicing\Packages\Microsoft-Windows-IIS-WebServer-ServerCommon-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1.cat
Successfully took permissions for file or folder C:\WINDOWS\Servicing\Packages\Microsoft-Windows-IIS-WebServer-ServerCommon-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1.mum
Successfully took permissions for file or folder C:\WINDOWS\Servicing\Packages
Successfully took permissions for file or folder C:\WINDOWS\Servicing\Packages\Package_508_for_KB4480116~31bf3856ad364e35~amd64~~10.0.1.4.mum

Successfully copied file C:\Users\Donald Hirst\AppData\Local\niemiro\Archive\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1.cat to C:\WINDOWS\Servicing\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1.cat.
Failed to backup file C:\WINDOWS\Servicing\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1.mum with error code 0x25D.

Successfully copied file C:\Users\Donald Hirst\AppData\Local\niemiro\Archive\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1.mum to C:\WINDOWS\Servicing\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1.mum.
Successfully copied file C:\Users\Donald Hirst\AppData\Local\niemiro\Archive\Packages\Microsoft-Windows-IIS-WebServer-AddOn-ServerCommon-Package~31bf3856ad364e35~amd64~~10.0.17763.1.cat to C:\WINDOWS\Servicing\Packages\Microsoft-Windows-IIS-WebServer-AddOn-ServerCommon-Package~31bf3856ad364e35~amd64~~10.0.17763.1.cat.
Failed to backup file C:\WINDOWS\Servicing\Packages\Microsoft-Windows-IIS-WebServer-AddOn-ServerCommon-Package~31bf3856ad364e35~amd64~~10.0.17763.1.mum with error code 0x1160.

Successfully copied file C:\Users\Donald Hirst\AppData\Local\niemiro\Archive\Packages\Microsoft-Windows-IIS-WebServer-AddOn-ServerCommon-Package~31bf3856ad364e35~amd64~~10.0.17763.1.mum to C:\WINDOWS\Servicing\Packages\Microsoft-Windows-IIS-WebServer-AddOn-ServerCommon-Package~31bf3856ad364e35~amd64~~10.0.17763.1.mum.
Successfully copied file C:\Users\Donald Hirst\AppData\Local\niemiro\Archive\Packages\Microsoft-Windows-IIS-WebServer-ServerCommon-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1.cat to C:\WINDOWS\Servicing\Packages\Microsoft-Windows-IIS-WebServer-ServerCommon-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1.cat.
Failed to backup file C:\WINDOWS\Servicing\Packages\Microsoft-Windows-IIS-WebServer-ServerCommon-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1.mum with error code 0x1160.

Successfully copied file C:\Users\Donald Hirst\AppData\Local\niemiro\Archive\Packages\Microsoft-Windows-IIS-WebServer-ServerCommon-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1.mum to C:\WINDOWS\Servicing\Packages\Microsoft-Windows-IIS-WebServer-ServerCommon-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1.mum.
Failed to copy file C:\Users\Donald Hirst\AppData\Local\niemiro\Archive\Packages\Package_508_for_KB4480116~31bf3856ad364e35~amd64~~10.0.1.4.cat to C:\WINDOWS\Servicing\Packages\Package_508_for_KB4480116~31bf3856ad364e35~amd64~~10.0.1.4.cat with error code ERROR_ACCESS_DENIED.
Successfully copied file C:\Users\Donald Hirst\AppData\Local\niemiro\Archive\Packages\Package_508_for_KB4480116~31bf3856ad364e35~amd64~~10.0.1.4.mum to C:\WINDOWS\Servicing\Packages\Package_508_for_KB4480116~31bf3856ad364e35~amd64~~10.0.1.4.mum.

Successfully restored ownership for C:\WINDOWS\Servicing\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1.cat
Successfully restored permissions on C:\WINDOWS\Servicing\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1.cat
Successfully restored ownership for C:\WINDOWS\Servicing\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1.mum
Successfully restored permissions on C:\WINDOWS\Servicing\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1.mum
Successfully restored ownership for C:\WINDOWS\Servicing\Packages\Microsoft-Windows-IIS-WebServer-AddOn-ServerCommon-Package~31bf3856ad364e35~amd64~~10.0.17763.1.cat
Successfully restored permissions on C:\WINDOWS\Servicing\Packages\Microsoft-Windows-IIS-WebServer-AddOn-ServerCommon-Package~31bf3856ad364e35~amd64~~10.0.17763.1.cat
Successfully restored ownership for C:\WINDOWS\Servicing\Packages\Microsoft-Windows-IIS-WebServer-AddOn-ServerCommon-Package~31bf3856ad364e35~amd64~~10.0.17763.1.mum
Successfully restored permissions on C:\WINDOWS\Servicing\Packages\Microsoft-Windows-IIS-WebServer-AddOn-ServerCommon-Package~31bf3856ad364e35~amd64~~10.0.17763.1.mum
Successfully restored ownership for C:\WINDOWS\Servicing\Packages\Microsoft-Windows-IIS-WebServer-ServerCommon-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1.cat
Successfully restored permissions on C:\WINDOWS\Servicing\Packages\Microsoft-Windows-IIS-WebServer-ServerCommon-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1.cat
Successfully restored ownership for C:\WINDOWS\Servicing\Packages\Microsoft-Windows-IIS-WebServer-ServerCommon-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1.mum
Successfully restored permissions on C:\WINDOWS\Servicing\Packages\Microsoft-Windows-IIS-WebServer-ServerCommon-Package~31bf3856ad364e35~amd64~en-US~10.0.17763.1.mum
Successfully restored ownership for C:\WINDOWS\Servicing\Packages
Successfully restored permissions on C:\WINDOWS\Servicing\Packages
Successfully restored ownership for C:\WINDOWS\Servicing\Packages\Package_508_for_KB4480116~31bf3856ad364e35~amd64~~10.0.1.4.mum
Successfully restored permissions on C:\WINDOWS\Servicing\Packages\Package_508_for_KB4480116~31bf3856ad364e35~amd64~~10.0.1.4.mum
PowerCopy:: directive failed to complete successfully.




Failed to process all directives successfully.
SFCFix version 3.0.1.0 by niemiro has completed.
Currently storing 8 datablocks.
Finish time: 2019-02-22 15:09:32.336
Script hash: JAcxRSprxHYFDVVT029TMA1WpS/Oe3FDd5WC1QOE4yQ=
----------------------EOF-----------------------

Sysnative Windows Update · Feb 22, 2019

This is interesting. It appears that the fix was partially unsuccessful. Please run DISM again so I could see which files are yet to be fixed. Thank you.

In case you require steps again, they have been outlined in Post#4.

Thank you.

dvhirst865 · Feb 22, 2019

OK, steps are clear. Rerunning DISM...
The next version of cbs.zip is attached.

Sysnative Windows Update · Feb 22, 2019

Thank you. Let's see if this will be successful:

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.

dvhirst865 · Feb 22, 2019

No joy. Here are the results.

Code:

SFCFix version 3.0.1.0 by niemiro.
Start time: 2019-02-22 16:04:19.279
Microsoft Windows 10 Build 17763 - amd64
Using .zip script file at C:\Users\Donald Hirst\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\Servicing\Packages
Successfully took permissions for file or folder C:\WINDOWS\Servicing\Packages\Package_508_for_KB4480116~31bf3856ad364e35~amd64~~10.0.1.4.mum
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_microsoft-windows-microsoftedge_31bf3856ad364e35_10.0.17763.316_none_8621bb6475b02ada\MicrosoftEdgePDF.targetsize-16.png
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_microsoft-windows-microsoftedge_31bf3856ad364e35_10.0.17763.316_none_8621bb6475b02ada\MicrosoftEdgeSplashScreen.scale-125_contrast-black.png
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_microsoft-windows-microsoftedge_31bf3856ad364e35_10.0.17763.316_none_8621bb6475b02ada\MicrosoftEdgeSquare44x44.scale-200_contrast-black.png
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_microsoft-windows-browser-brokers_31bf3856ad364e35_11.0.17763.253_none_eedf3ee8928a0fdb\browserexport.exe

Failed to copy file C:\Users\Donald Hirst\AppData\Local\niemiro\Archive\Packages\Package_508_for_KB4480116~31bf3856ad364e35~amd64~~10.0.1.4.cat to C:\WINDOWS\Servicing\Packages\Package_508_for_KB4480116~31bf3856ad364e35~amd64~~10.0.1.4.cat with error code ERROR_ACCESS_DENIED.
WARNING: File C:\WINDOWS\Servicing\Packages\Package_508_for_KB4480116~31bf3856ad364e35~amd64~~10.0.1.4.mum was not backed up as that would replace the current backup.
Successfully copied file C:\Users\Donald Hirst\AppData\Local\niemiro\Archive\Packages\Package_508_for_KB4480116~31bf3856ad364e35~amd64~~10.0.1.4.mum to C:\WINDOWS\Servicing\Packages\Package_508_for_KB4480116~31bf3856ad364e35~amd64~~10.0.1.4.mum.
Successfully copied file C:\Users\Donald Hirst\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-microsoftedge_31bf3856ad364e35_10.0.17763.316_none_8621bb6475b02ada\MicrosoftEdgePDF.targetsize-16.png to C:\WINDOWS\winsxs\amd64_microsoft-windows-microsoftedge_31bf3856ad364e35_10.0.17763.316_none_8621bb6475b02ada\MicrosoftEdgePDF.targetsize-16.png.
Successfully copied file C:\Users\Donald Hirst\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-microsoftedge_31bf3856ad364e35_10.0.17763.316_none_8621bb6475b02ada\MicrosoftEdgeSplashScreen.scale-125_contrast-black.png to C:\WINDOWS\winsxs\amd64_microsoft-windows-microsoftedge_31bf3856ad364e35_10.0.17763.316_none_8621bb6475b02ada\MicrosoftEdgeSplashScreen.scale-125_contrast-black.png.
Successfully copied file C:\Users\Donald Hirst\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-microsoftedge_31bf3856ad364e35_10.0.17763.316_none_8621bb6475b02ada\MicrosoftEdgeSquare44x44.scale-200_contrast-black.png to C:\WINDOWS\winsxs\amd64_microsoft-windows-microsoftedge_31bf3856ad364e35_10.0.17763.316_none_8621bb6475b02ada\MicrosoftEdgeSquare44x44.scale-200_contrast-black.png.
Failed to backup file C:\WINDOWS\winsxs\amd64_microsoft-windows-browser-brokers_31bf3856ad364e35_11.0.17763.253_none_eedf3ee8928a0fdb\browserexport.exe with error code 0x1160.

Successfully copied file C:\Users\Donald Hirst\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-browser-brokers_31bf3856ad364e35_11.0.17763.253_none_eedf3ee8928a0fdb\browserexport.exe to C:\WINDOWS\winsxs\amd64_microsoft-windows-browser-brokers_31bf3856ad364e35_11.0.17763.253_none_eedf3ee8928a0fdb\browserexport.exe.

Successfully restored ownership for C:\WINDOWS\Servicing\Packages
Successfully restored permissions on C:\WINDOWS\Servicing\Packages
Successfully restored ownership for C:\WINDOWS\Servicing\Packages\Package_508_for_KB4480116~31bf3856ad364e35~amd64~~10.0.1.4.mum
Successfully restored permissions on C:\WINDOWS\Servicing\Packages\Package_508_for_KB4480116~31bf3856ad364e35~amd64~~10.0.1.4.mum
Successfully restored ownership for C:\WINDOWS\winsxs\amd64_microsoft-windows-microsoftedge_31bf3856ad364e35_10.0.17763.316_none_8621bb6475b02ada\MicrosoftEdgePDF.targetsize-16.png
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_microsoft-windows-microsoftedge_31bf3856ad364e35_10.0.17763.316_none_8621bb6475b02ada\MicrosoftEdgePDF.targetsize-16.png
Successfully restored ownership for C:\WINDOWS\winsxs\amd64_microsoft-windows-microsoftedge_31bf3856ad364e35_10.0.17763.316_none_8621bb6475b02ada\MicrosoftEdgeSplashScreen.scale-125_contrast-black.png
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_microsoft-windows-microsoftedge_31bf3856ad364e35_10.0.17763.316_none_8621bb6475b02ada\MicrosoftEdgeSplashScreen.scale-125_contrast-black.png
Successfully restored ownership for C:\WINDOWS\winsxs\amd64_microsoft-windows-microsoftedge_31bf3856ad364e35_10.0.17763.316_none_8621bb6475b02ada\MicrosoftEdgeSquare44x44.scale-200_contrast-black.png
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_microsoft-windows-microsoftedge_31bf3856ad364e35_10.0.17763.316_none_8621bb6475b02ada\MicrosoftEdgeSquare44x44.scale-200_contrast-black.png
Successfully restored ownership for C:\WINDOWS\winsxs\amd64_microsoft-windows-browser-brokers_31bf3856ad364e35_11.0.17763.253_none_eedf3ee8928a0fdb\browserexport.exe
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_microsoft-windows-browser-brokers_31bf3856ad364e35_11.0.17763.253_none_eedf3ee8928a0fdb\browserexport.exe
PowerCopy:: directive failed to complete successfully.




Failed to process all directives successfully.
SFCFix version 3.0.1.0 by niemiro has completed.
Currently storing 12 datablocks.
Finish time: 2019-02-22 16:04:21.856
Script hash: jBKgKfOP3ndSLsyw2jhvnWSb7ehLQsQk+91rScm4KrE=
----------------------EOF-----------------------

dvhirst865 · Feb 22, 2019

For some reason, I'm not seeing immediate updates when you reply on the forum, strange. Suggestions welcome.

DVH

Sysnative Windows Update · Feb 22, 2019

Thank you.

I'd like to check something, but before I do that I need to verify that everything of importance has been backed up.

As for the issue with the updates on my replies, there might be an occasional delay between the time I post and you receive the notification. It happens to me as well sometimes.

dvhirst865 · Feb 22, 2019

I have an external backup drive that backs up my user level files hourly. The system back up, for now, is manual on another device, and the most recent one is the backup and recovery from 2 February 2019. That is the basis of the currently running instance, and going back to recover from that backup is acceptable. The system disk (C:) is on SSD, all actual data storage and backup is on multiple other devices.

Sysnative Windows Update · Feb 22, 2019

Okay, let's see if ChkDsk finds any corruption:

Step#1 - ChkDsk Scan

Click your Start Button in the lower left of your computer and type cmd in the search box.
Once the cmd program is found, right-click on it with your mouse and select Run as administrator as shown below.
Answer Yes when asked to allow.
You should now have a black window open that you can type into.
Please type chkdsk /f and then press enter. It will ask you to do it on reboot, please accept and do so.
Chkdsk will start to run. Please allow it to finish.
Download ListChkdskResult.exe by SleepyDude and save it on your desktop. If it's already downloaded to your desktop, just skip this step.
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.

dvhirst865 · Feb 22, 2019

That's a handy utility. I've been looking at Event Viewer. On it.

dvhirst865 · Feb 22, 2019

OK, here we go; chkdsk /f results. Nope, too large. Zipped file is available at:
ListChkdskResult.zip

Looking at the details, despite the clean report from my monitoring software, it looks like there is definitely a hardware problem somewhere.

Next?

Sysnative Windows Update · Feb 22, 2019

Please navigate to the S.M.A.R.T. tab and take a screenshot.

dvhirst865 · Feb 22, 2019

Unfortunately, I don't think OCZ provides much S.M.A.R.T. information, here it is:

[SOLVED] SFC Fails | DISM Fails | SFCFix Crashes | What Now?

Member

Attachments

Inactive

Member

Inactive

Member

Member

Attachments

Inactive

Attachments

Member

Inactive

Member

Attachments

Inactive

Attachments

Member

Member

Inactive

Member

Attachments

Inactive

Member

Member

Inactive

Member