[SOLVED] Windows update failed going back via multiple issues...

Spodster

Active member
Joined
Jun 16, 2020
Posts
31
First time poster but wondering if I can call upon your help as every other place/thread I read/do I end up making no progress :(

A brief history...
Some time ago (6 months+) an update came out for my Win10 that didn't go so well, it thumbled through and carried on but strange things started to happen after.
The strange things culminated in me one day having to 'reset' Win10 from a recovery install as it wouldn't even boot to the OS, this was in Feb, I know it's Feb as I still have the "Apps removed wile resetting" shortcut on my desktop.
From that point on the App store didn't work, calculator and other apps no longer exist but it didn't really matter I could still use and work on it.
For the past two M$ patch cycles it's complained about installing the cumulative update so I went about trying to fix things once and for all.
Although as mentioned in the first line I'm now in the internal triangle that is:-

DISM.exe /Online /Cleanup-image /Scanhealth
DISM.exe /Online /Cleanup-image /Restorehealth
DISM.exe /online /cleanup-image /startcomponentcleanup
sfc /scannow

None of which want to work or complete.

I ran a "chkdsk C: /R" which runs and does stuff but I'm not sure it's actually found a problem and repairing it or just running through the motions and then finding nothing to repair. It takes approx 5-10 min and then kicks me into the OS but ran it twice and it does the same thing.

I've downloaded GsmartControl and run it, looks to have no issues with my OS SSD

1592307315772.png

1592307402366.png

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

=== START OF INFORMATION SECTION ===
Model Family:     Samsung based SSDs
Device Model:     Samsung SSD 840 PRO Series
Serial Number:    S12PNEAD201168B
LU WWN Device Id: 5 002538 5501c8d5a
Firmware Version: DXM04B0Q
User Capacity:    128,035,676,160 bytes [128 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ATA8-ACS T13/1699-D revision 4c
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Tue Jun 16 12:14:11 2020 GMTST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM feature is:   Unavailable
Rd look-ahead is: Enabled
Write cache is:   Enabled
DSN feature is:   Unavailable
ATA Security is:  Disabled, frozen [SEC2]

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

General SMART Values:
Offline data collection status:  (0x00)    Offline data collection activity
                    was never started.
                    Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)    The previous self-test routine completed
                    without error or no self-test has ever
                    been run.
Total time to complete Offline
data collection:         (65476) seconds.
Offline data collection
capabilities:              (0x53) SMART execute Offline immediate.
                    Auto Offline data collection on/off support.
                    Suspend Offline collection upon new
                    command.
                    No Offline surface scan supported.
                    Self-test supported.
                    No Conveyance Self-test supported.
                    Selective Self-test supported.
SMART capabilities:            (0x0003)    Saves SMART data before entering
                    power-saving mode.
                    Supports SMART auto save timer.
Error logging capability:        (0x01)    Error logging supported.
                    General Purpose Logging supported.
Short self-test routine
recommended polling time:      (   2) minutes.
Extended self-test routine
recommended polling time:      (  15) minutes.
SCT capabilities:            (0x003d)    SCT Status supported.
                    SCT Error Recovery Control supported.
                    SCT Feature Control supported.
                    SCT Data Table supported.

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  5 Reallocated_Sector_Ct   PO--CK   100   100   010    -    0
  9 Power_On_Hours          -O--CK   096   096   000    -    18649
 12 Power_Cycle_Count       -O--CK   097   097   000    -    2764
177 Wear_Leveling_Count     PO--C-   086   086   000    -    486
179 Used_Rsvd_Blk_Cnt_Tot   PO--C-   100   100   010    -    0
181 Program_Fail_Cnt_Total  -O--CK   100   100   010    -    0
182 Erase_Fail_Count_Total  -O--CK   100   100   010    -    0
183 Runtime_Bad_Block       PO--C-   100   100   010    -    0
187 Uncorrectable_Error_Cnt -O--CK   100   100   000    -    0
190 Airflow_Temperature_Cel -O--CK   060   052   000    -    40
195 ECC_Error_Rate          -O-RC-   200   200   000    -    0
199 CRC_Error_Count         -OSRCK   099   099   000    -    2
235 POR_Recovery_Count      -O--C-   099   099   000    -    48
241 Total_LBAs_Written      -O--CK   099   099   000    -    32559664806
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

General Purpose Log Directory Version 1
SMART           Log Directory Version 1 [multi-sector log support]
Address    Access  R/W   Size  Description
0x00       GPL,SL  R/O      1  Log Directory
0x01       GPL,SL  R/O      1  Summary SMART error log
0x02       GPL,SL  R/O      1  Comprehensive SMART error log
0x03       GPL,SL  R/O      1  Ext. Comprehensive SMART error log
0x06       GPL,SL  R/O      1  SMART self-test log
0x07       GPL,SL  R/O      1  Extended self-test log
0x09       GPL,SL  R/W      1  Selective self-test log
0x10       GPL,SL  R/O      1  NCQ Command Error log
0x11       GPL,SL  R/O      1  SATA Phy Event Counters log
0x30       GPL,SL  R/O      1  IDENTIFY DEVICE data log
0x80-0x9f  GPL,SL  R/W     16  Host vendor specific log
0xa0       GPL,SL  VS      16  Device vendor specific log

SMART Extended Comprehensive Error Log Version: 1 (1 sectors)
No Errors Logged

Warning! SMART Extended Self-test Log Structure error: invalid SMART checksum.
SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Offline             Completed without error       00%         3         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
  255        0    65535  Read_scanning was never started
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

SCT Status Version:                  3
SCT Version (vendor specific):       256 (0x0100)
SCT Support Level:                   1
Device State:                        Active (0)
Current Temperature:                    41 Celsius
Power Cycle Min/Max Temperature:     36/43 Celsius
Lifetime    Min/Max Temperature:      0/70 Celsius
Under/Over Temperature Limit Count:   0/0

SCT Temperature History Version:     3 (Unknown, should be 2)
Temperature Sampling Period:         1 minute
Temperature Logging Interval:        1 minute
Min/Max recommended Temperature:      0/70 Celsius
Min/Max Temperature Limit:            0/70 Celsius
Temperature History Size (Index):    128 (20)

Index    Estimated Time   Temperature Celsius
  21    2020-06-16 10:07     ?  -
 ...    ..(105 skipped).    ..  -
 127    2020-06-16 11:53     ?  -
   0    2020-06-16 11:54    40  *********************
   1    2020-06-16 11:55    37  ******************
   2    2020-06-16 11:56    37  ******************
   3    2020-06-16 11:57    38  *******************
   4    2020-06-16 11:58    39  ********************
 ...    ..(  2 skipped).    ..  ********************
   7    2020-06-16 12:01    39  ********************
   8    2020-06-16 12:02    40  *********************
   9    2020-06-16 12:03    40  *********************
  10    2020-06-16 12:04    41  **********************
  11    2020-06-16 12:05    39  ********************
  12    2020-06-16 12:06    40  *********************
  13    2020-06-16 12:07    43  ************************
  14    2020-06-16 12:08    39  ********************
  15    2020-06-16 12:09    37  ******************
  16    2020-06-16 12:10    36  *****************
  17    2020-06-16 12:11    36  *****************
  18    2020-06-16 12:12    40  *********************
  19    2020-06-16 12:13    39  ********************
  20    2020-06-16 12:14    41  **********************

SCT Error Recovery Control:
           Read: Disabled
          Write: Disabled

Device Statistics (GP/SMART Log 0x04) not supported

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  2            0  Command failed due to ICRC error
0x0002  2            0  R_ERR response for data FIS
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2            0  R_ERR response for host-to-device data FIS
0x0005  2            0  R_ERR response for non-data FIS
0x0006  2            0  R_ERR response for device-to-host non-data FIS
0x0007  2            0  R_ERR response for host-to-device non-data FIS
0x0008  2            0  Device-to-host non-data FIS retries
0x0009  2           20  Transition from drive PhyRdy to drive PhyNRdy
0x000a  2           20  Device-to-host register FISes sent due to a COMRESET
0x000b  2            0  CRC errors within host-to-device FIS
0x000d  2            0  Non-CRC errors within host-to-device FIS
0x000f  2            0  R_ERR response for host-to-device data FIS, CRC
0x0010  2            0  R_ERR response for host-to-device data FIS, non-CRC
0x0012  2            0  R_ERR response for host-to-device non-data FIS, CRC
0x0013  2            0  R_ERR response for host-to-device non-data FIS, non-CRC



I ran sfc /scannow output of CBS log as attached
I ran Dism /Online /Cleanup-Image /ScanHealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.720

[=== 6.8% ]
Error: 4448

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

DISM log as attached


Hoping that I can get it all working :-)
 

Attachments

BTW if I run SFCFix it kind of gets stuck at running a DISM command, 6% error 4448 check log, much like when I run it.

Even though it go stuck I pressed enter within and got a few more prompts then the output.

Code:
SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-06-16 12:53:35.413
Microsoft Windows 10 Build 18363 - amd64
Not using a script file.




AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2020-06-16 13:26:34.143
----------------------EOF-----------------------
 
Hi!


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.



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.
 

Attachments

Thanks.


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.



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.
 

Attachments

Ok it got to 100% now rather than the usual 6% :-) but says

Windows Resource Protection found corrupt files but was unable to fix some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

CBS log as attached
 

Attachments

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.



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.
 

Attachments

Updated, realised I'd been uploading .log not rename .txt file as well.
Do you want me to delete and clean down the CBS log as well each time?
 

Attachments

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.



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.
 

Attachments

I guess we're making progress here :-)

Code:
SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-06-17 13:46:43.147
Microsoft Windows 10 Build 18363 - amd64
Using .zip script file at C:\Users\calzo\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\Winsxs\amd64_microsoft-windows-t..etpc-mathrecognizer_31bf3856ad364e35_10.0.18362.1_none_8aa9e79dccdc6d02

Failed to copy file C:\Users\calzo\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-t..etpc-mathrecognizer_31bf3856ad364e35_10.0.18362.1_none_8aa9e79dccdc6d02\mraut.dll to C:\WINDOWS\Winsxs\amd64_microsoft-windows-t..etpc-mathrecognizer_31bf3856ad364e35_10.0.18362.1_none_8aa9e79dccdc6d02\mraut.dll with error code ERROR_ACCESS_DENIED.

Successfully restored ownership for C:\WINDOWS\Winsxs\amd64_microsoft-windows-t..etpc-mathrecognizer_31bf3856ad364e35_10.0.18362.1_none_8aa9e79dccdc6d02
Successfully restored permissions on C:\WINDOWS\Winsxs\amd64_microsoft-windows-t..etpc-mathrecognizer_31bf3856ad364e35_10.0.18362.1_none_8aa9e79dccdc6d02
PowerCopy:: directive failed to complete successfully.




Failed to process all directives successfully.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 12 datablocks.
Finish time: 2020-06-17 13:46:43.502
Script hash: RKVIWrGwFRCCZv96bQ0I/B98Sa3ch4Ii47H7PENiiN4=
----------------------EOF-----------------------
 

Attachments

Can you please run another Check Didk scan? I fixed all the corruption except one which refuses to get fixed due to access denied errors which is indicative of a hard drive failure.
 
Ran from the GUI and got as below, ran from command line with a reboot, not sure where log is for that.

Also re ran last SFCfix again and that as below with same access denied message.

Code:
Chkdsk was executed in scan mode on a volume snapshot. 

Checking file system on C:

Stage 1: Examining basic file system structure ...
  723968 file records processed.                                                         File verification completed.
  31677 large file records processed.                                      0 bad file records processed.                                     
Stage 2: Examining file name linkage ...
  44398 reparse records processed.                                         835304 index entries processed.                                                        Index verification completed.


  44398 reparse records processed.                                       
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
  55669 data files processed.                                            CHKDSK is verifying Usn Journal...
  35695104 USN bytes processed.                                                            Usn Journal verification completed.

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

 123976445 KB total disk space.
  62283036 KB in 284906 files.
    168336 KB in 55670 indexes.
    853085 KB in use by the system.
     65536 KB occupied by the log file.
  60671988 KB available on disk.

      4096 bytes in each allocation unit.
  30994111 total allocation units on disk.
  15167997 allocation units available on disk.

----------------------------------------------------------------------


Stage 1: Examining basic file system structure ...

Stage 2: Examining file name linkage ...

Stage 3: Examining security descriptors ...
 

Attachments

Step#1 - FRST Scan

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. Right-click FRST64.exe and click Run as Administrator to run it as administrator. When the tool opens, click Yes to disclaimer.
3. Please ensure you place a check mark in the Addition.txt check box at the bottom of the form before running (if not already checked).
4. Press Scan button.
5. It will produce a log called FRST.txt in the same directory the tool is run from (which should now be the desktop)
6. Please attach the log back here.
7. Another log (Addition.txt - also located in the same directory as FRST64.exe) will be generated Please also attach that along with the FRST.txt in your reply.
 
Ok there's a lot of personal information held in those files I'm not happy about placing on a public forum.
Is there a way to send it directly or specific information in them you're after?
 
I need to see the logs in order to be able to assess any potential compatibility issues which may arise in running or using our tools.

I'm not sure what exactly are you concerned about, but thousands of people have done so with no issues or privacy issues at all. We have been here a long time and can be trusted as witnessed by countless number of people.
 

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

Back
Top