Windows 8.1 - Corrupt WinSxS Files prevent Windows Updates

These seem to be the same four files as last time.
Click to expand...
Weird, the first 2 files should have been replaced.

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.
  • Download the attachment SFCFixScript.txt and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
    1p8eDnI.gif
  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Open the file, then copy and paste its content in your next reply.
 

Attachments

Close Windows and shutdown the machine completely.
Wait 10 seconds and restart.

Double-click
myjIXnC.png
SFCFix.exe to run the tool. A dialog may come up asking for approval. If it does go ahead and allow.
On completion a log file (SFCFix.txt) will be opened. Copy and Paste its content into your next reply.
 
I ran SFCFix immediately after restarting. It claimed my computer was clean:
SFCFix version 3.0.2.1 by niemiro.
Start time: 2019-07-02 16:41:56.118
Microsoft Windows 8.1 Update 3 - 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 446 datablocks.
Finish time: 2019-07-02 16:45:23.372
----------------------EOF-----------------------
Click to expand...

However, sfc /scannow detected some corruptions. Here is the SFCFix log file after running it again:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2019-07-02 20:55:18.107
Microsoft Windows 8.1 Update 3 - amd64
Not using a script file.




AutoAnalysis::
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-ie-ratings_31bf3856ad364e35_11.0.9600.19130_none_cb689f993fa3a910\icrav03.rat
CORRUPT: C:\Windows\winsxs\x86_microsoft-windows-ie-ratings_31bf3856ad364e35_11.0.9600.19130_none_6f4a0415874637da\icrav03.rat
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-rasbase_31bf3856ad364e35_6.3.9600.18895_none_fe94d4384e6da5da\kmddsp.tsp
CORRUPT: C:\Windows\winsxs\wow64_microsoft-windows-rasbase_31bf3856ad364e35_6.3.9600.18895_none_08e97e8a82ce67d5\kmddsp.tsp


SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 4
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 0
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 446 datablocks.
Finish time: 2019-07-02 21:22:02.287
----------------------EOF-----------------------
Click to expand...

SFC then wants me to reboot my computer again in order to apply a fix.

These are again the same four files - maybe this is some sort of registry mismatch or something along those lines?
 
Please zip the file C:\Windows\Logs\CBS\cbs.log and attach it to your next reply.
Note: if the file is too big to upload to your next post please upload via a service such as Filedropper or One Drive or SendSpace and provide the download link.
 
Remove Update Manually
  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, then press enter.
    wusa /uninstall /KB:4457129
  4. Let me know if it says it was successful or if there are any errors.
 
After waiting for quite some time, it would seem that the installer is stuck on this screen. Hitting "Cancel" does nothing.

48469
 
Just wait for several hours. If still no progress, shutdown/restart Windows and try the uninstall again.
 
After waiting for several hours, I had to restart my computer and try again. Doing so gave me the following error:

48477
 
Please zip the file C:\Windows\Logs\CBS\cbs.log and attach it to your next reply.
Note: if the file is too big to upload to your next post please upload via a service such as Filedropper or One Drive or SendSpace and provide the download link.
 
The log file is too old.

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.

    Code: 
    sfc /scannow
    Wait for this to finish before you continue

    Code: 
    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.
    Note: if the file is too big to upload to your next post please upload via a service such as Filedropper or One Drive or SendSpace and just provide the download link.
 
Has been about two months, and I'm still having issues. SFC keeps wanting to restart my computer to apply fixes, but such fixes never seem to do anything about the issue. I believe the issue hasn't changed since my last log upload, but just in case, I'll upload a fresh CBS.log file:
 

Attachments

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.
  • Download the attachment SFCFix.zip and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
    1p8eDnI.gif
  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Open the file, then copy and paste its content in your next reply.
 

Attachments

All directives were processed successfully, although there still seem to be some issues.
 

Attachments

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.
  • Download the attachment SFCFix.zip and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
    1p8eDnI.gif
  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Open the file, then copy and paste its content in your next reply.
 

Attachments

All directives were processed successfully. I believe the issues might still remain, but as with last time, nothing is able to detect them unless I reboot (which I haven't done yet):

1564882793661.png

SFCFix attempts a repair, but uses DISM to do so; this brings up Error 3017 again, and then SFCFix says that it doesn't detect any errors.
 

Attachments

Please provide a fresh copy on the file cbs.log.
 
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