[7SP1Pro x64] CheckSUR corruption found, Windows Update KB4048957 repeatedly fails

C

Cerber

Well-known member
Joined
Dec 11, 2017
Posts
103
Hello,

I have a Windows 7 Pro SP1 x64 system here which has 82 CheckSUR corruptions found, all of type "(f) CSI Missing Winning Component Key 0x00000000". Unfortunately, information online about resolving that particular error type appears to be near non-existent.

I was able to manually fix the one file corruption issue which was previously detected by copying the file from another system.

The Windows Update error I'm receiving is 0x80004005.

Please find my log files attached, and thanks in advance.

---
Cerber
 

Attachments

Hello,

Status update: as of this morning, KB4054518 (which supercedes KB4048957) installed cleanly without issue.

Please see attached for updated log files.
- SFC /scannow ran citing no issues found.
- Still the same 82 errors in CheckSUR
- CBS log file is 149MB in size
 

Attachments

Hello and welcome,

Follow the instructions below please.


Step 1:
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
    myjIXnC.png
    SFCFix and move the executable to your desktop.
  • 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.


Step 2:
Start the System Update Readiness Tool (SURT) again.
On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log in your next reply.
 
PeterJ,

My apologies, but I'm not seeing a link to download the SFCFixScript.txt file...

Thank you.

---
Cerber
 
Thank you very much. Please find attached the updated log files.

We're still at a total of 82 errors, but now it's 40 of the previous 'CSI Missing Winning Component Key' and 42 new 'CSI C Mark Deployment Missing'.
 

Attachments

Follow the instructions below please.


Step 1:
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.


Step 2:
Start the System Update Readiness Tool (SURT) again.
On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log in your next reply.
 

Attachments

PeterJ,

Thanks again. Please see attached.

Found 93 errors
Fixed 33 errors
CSI Catalog Missing Total count: 1
Fixed: CSI Catalog Missing. Total count: 1
CSI Missing Component Key Total count: 11
Fixed: CSI Missing Component Key. Total count: 11
CSI Missing C Mark Total count: 11
Fixed: CSI Missing C Mark. Total count: 11
CSI C Mark Deployment Missing Total count: 20
CSI Catalog Thumbprint Invalid Total count: 10
Fixed: CSI Catalog Thumbprint Invalid. Total count: 10
CSI Missing Winning Component Key Total count: 40
 

Attachments

Follow the instructions below please.


Step 1:
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.


Step 2:
Start the System Update Readiness Tool (SURT) again.
On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log in your next reply.
 

Attachments

PeterJ,

Thank you. Please see attached.

Found 81 errors
Fixed 41 errors
CSI Catalog Missing Total count: 3
Fixed: CSI Catalog Missing. Total count: 3
CSI Missing Component Key Total count: 10
Fixed: CSI Missing Component Key. Total count: 10
CSI Missing C Mark Total count: 10
Fixed: CSI Missing C Mark. Total count: 10
CSI Catalog Thumbprint Invalid Total count: 18
Fixed: CSI Catalog Thumbprint Invalid. Total count: 18
CSI Missing Winning Component Key Total count: 40
 

Attachments

Please do following:

FRST Registry Search
1. Click your Start button and choose Control Panel.
2. In the upper right corner ensure the View by: is set to Category.
3. Select the Programs group.
4. Click the Turn Windows features on or off link. This will bring up the Server Manager dialog.
Note: This loads your components hive which is what we want. Please keep this dialog open while you perform the remaining steps. You can minimize it if you wish but keep it open.
5. Download the Farbar Recovery Scan Tool and save it to your Desktop:
64-bit: Downloading Farbar Recovery Scan Tool

6. Right-click on the file FRST64.exe and choose Run as administrator.
7. Copy and paste 8.0.7601.18631 into the Search box and click the Search Registry button.
8. When the scan is complete, a message will display that 'SearchReg.txt' is saved in the same folder FRST was started from. Notepad will open this file also. Close Notepad and attach the file 'SearchReg.txt' to your next reply.
9. You may close any remaining open windows now.
 
Hi PeterJ,

Is accessing "Turn Windows features on or off" the only way to get Windows 7 to load the Components Hive for FRST? This is a shipping system provided by the courier, and they have access to that particular function blocked via policy.

Thank you.
 
Following instructions below to load the components hive first, then run the FRST search command.

1. Right-click the Start button and click Command prompt(Administrator).
2. If you get a popup about UserAccountControl, allow the program to run.
3. When command prompt opens, copy and paste the following commands into it, press enter after each.

Code: 
REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS
Wait for this to finish before you continue

4. Please download the Farbar Recovery Scan Tool and save it to your Desktop:
64-bit: Downloading Farbar Recovery Scan Tool

5. Right-click on the file FRST64.exe and choose Run as administrator.
6. Copy and paste 8.0.7601.18631 into the Search box and click the Search Registry button.
7. When the scan is complete, a message will display that 'SearchReg.txt' is saved in the same folder FRST was started from. Notepad will open this file also. Close Notepad and attach the file 'SearchReg.txt' to your next reply.
8. You may close any remaining open windows now.
 
1. Right-click the program FRST64.exe on your desktop and select 'run as administrator'. When the tool opens click Yes to disclaimer.
2. Note: Ensure that the Addition.txt check box is checked at the bottom of the form within the Optional Scan area.
3. Press the Scan button.
4. Please wait for the tool to finish. It will produce two logfiles called FRST.txt and Addition.txt in the same directory the tool is run from (which should be the desktop)
5. Post the logfiles FRST.txt and Addition.txt as attachment in your next reply.
 
Doesn't Windows Update offers Internet Explorer 11 ?
If so, install it and report the result.
 
Hi PeterJ,

Hmmm... That's a slightly more convoluted issue.

Programs and Features > Installed Updates reports IE 11 as installed in late September.

Running a full administrative install in an attempt to repair IE 11 fails. Right-clicking the supposedly installed instance and Uninstalling fails.

In both 32-bit and 64-bit Program Files directories, the actual executable files are for IE 8.

Please see attached logs (zipped).
 

Attachments

Hi PeterJ,

I just wanted to give you a heads-up that from Dec. 23 - Jan. 2 our offices are closed, so after Friday I won't be back in the office until Jan. 3.

Thank you. :)

---
Cerber
 
No problem, we'll just wait for your next reply.
Follow the instructions below please.


Step 1:
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.


Step 2:
Start the System Update Readiness Tool (SURT) again.
On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log in your next reply.
 

Attachments

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