Help: SURT total detected corruption count = 779

Aura said:
Alright, follow the instructions below please.

myjIXnC.png
SFCFix - Fix Time
Click to expand...

SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-07-31 14:37:27.999
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at C:\Users\x\Desktop\SFCFixScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_885afb5bed212f4b073563b5024dfe8c_31bf3856ad364e35_6.1.7601.19018_none_33885207d59f7617.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_885afb5bed212f4b073563b5024dfe8c_31bf3856ad364e35_6.1.7601.19018_none_33885207d59f7617.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 6 datablocks.
Finish time: 2016-07-31 14:37:28.695
Script hash: jgZ5XmSoIV2oP9RD/lTWXQdG4HFWX9Uc9Uf88yHlS6Y=
----------------------EOF-----------------------
 
Alright, try to install the update again, and if it fails, upload the new CBS.log and WindowsUpdate.log for me please.
 
Aura said:
Alright, try to install the update again, and if it fails, upload the new CBS.log and WindowsUpdate.log for me please.
Click to expand...

Said it didn't install, so I PM'd the link for the August 1st logs.

Thanks!!
 
New error. Do you have your Windows installation media by the way?
 
If you do, a Repair Install might be the fastest way to solve your issue, considering that we may have to go through a lot of fixes if everything continues that way.
 
Aura said:
If you do, a Repair Install might be the fastest way to solve your issue, considering that we may have to go through a lot of fixes if everything continues that way.
Click to expand...

I re-ran SFCFix and got the log below, showing 1 error (down from 779!). Is it a continual 1 error problem, or did we get it down to the last one?
Thanks!




SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-08-04 21:59:24.628
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.




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




Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 6 datablocks.
Finish time: 2016-08-04 22:00:34.446
----------------------EOF-----------------------
 
It could be 1 error from an old log, meaning that there's actually none left. Let's see.

IGJdB0T.png
System Update Readiness Tool (SURT) - Scan
Follow the instructions below to run a scan with the System Update Readiness Tool (SURT) and provide a log;
  • Download the right version of SURT for your system;
    • Your version of Windows is: Windows 7 SP1 x64
  • Once downloaded, execute the installer, and go throught the installation (this process can take around 15-20 minutes);
  • On completion, a log will be created in C:\Windows\Logs\CBS\CheckSUR.log;
  • Attach this log in your next reply;
Alternatively, if these instructions are unclear for you, you can follow the tutorial below.

System Update Readiness Tool (SURT)
 
Aura said:
It could be 1 error from an old log, meaning that there's actually none left. Let's see.

IGJdB0T.png
System Update Readiness Tool (SURT) - Scan
  • On completion, a log will be created in C:\Windows\Logs\CBS\CheckSUR.log;
Click to expand...


=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2016-08-08 17:20

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f) CSI Catalog Missing 0x00000002 d500a9c53097f90db661b3cfc3354f45d34c9828a55ab0d9760ea7755faf6916.cat 885afb5bed2..3b5024dfe8c_31bf3856ad364e35_6.1.7601.19018_33885207d59f7617 Missing catalog or invalid CatalogThumprint
(fix) CSI Catalog Missing CSI File Replaced Deleted CatalogThumbprint
(f) CSI Manifest Missing 0x00000002 amd64_885afb5bed212f4b073563b5024dfe8c_31bf3856ad364e35_6.1.7601.19018_none_33885207d59f7617.manifest amd64_885afb5bed212f4b073563b5024dfe8c_31bf3856ad364e35_6.1.7601.19018_none_33885207d59f7617

Summary:
Seconds executed: 600
Found 2 errors
Fixed 1 errors
CSI Manifest Missing Total count: 1
CSI Catalog Missing Total count: 1
Fixed: CSI Catalog Missing. Total count: 1

Unavailable repair files:
winsxs\manifests\amd64_885afb5bed212f4b073563b5024dfe8c_31bf3856ad364e35_6.1.7601.19018_none_33885207d59f7617.manifest
 
Alright, we'll replace that corrupt manifest file.

IGJdB0T.png
System Update Readiness Tool (SURT) - Fix

WARNING! The following fix is specific to the user's system in this thread. No one else should follow the instructions below to apply that fix, as it could damage your system. If you need assistance with an issue, please start a new thread and someone will assist you shortly.

Follow the instructions below to fix the errors reported by the System Update Readiness Tool (SURT);
  • Download the attached archive file, Packs.zip and save it on your Desktop;
  • Once it's downloaded, right-click on it and select Extract All...;
  • Check the Show extracted files when complete checkbox, and click on Extract;
  • On completion, a folder will open with two folders inside it, Manifests and Packages;
    • Copy and paste the files of the Manifests folder (if there are any) inside C:\Windows\Temp\CheckSur\winsxs\Manifests
    • Copy and paste the files of the Packages folder (if there are any) inside C:\Windows\Temp\CheckSur\servicing\Packages
  • Run the System Update Readiness Tool (SURT) again;
  • On completion, attach the log located at C:\Windows\Logs\CBS\CheckSUR.log in your next reply;
Packs.zip
 
Now it replaced even more stuff that weren't even detected in the first SURT runs... Run SURT again please and provide me a new CheckSUR.log, I want to see if it'll come up with stuff it wasn't showing before again.
 
Okay good. Back to SFC.

EndqYRa.png
System File Checker (SFC)
Follow the instructions below to run a SFC scan on your system and to provide the CBS log in your next reply;
  • On Windows Vista & 7, click on the Windows Start Menu, then enter cmd in the search box, right-click on the cmd icon and select
    Spcusrh.png
    Run as Administrator
  • On Windows 8, drag your cursor in the bottom-left corner, and right-click on the metro menu preview, then select Command Prompt (Admin);
  • On Windows 8.1 and Windows 10, right click on the Windows logo in the bottom-left corner and select Command Prompt (Admin);
  • Enter the command below and press on Enter;
    Code: 
    sfc /scannow
    Note: There's a space between "sfc" and "/scannow";
  • Once the scan is complete, enter the command below and press on Enter
    Code: 
    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  • A file called cbs.txt will have appeared on your Desktop. Upload the file on Dropbox, Google Drive or OneDrive and post the download URL for it here;
Note: Please note that the CBS.log is volatile, which means that if you don't upload it after the SFC scan is completed, it won't have the information from the scan anymore. So archive it and upload it as soon as you can.
 
Good, no corruption! Now, try to install the update again and if it fails, upload the new CBS.log and WindowsUpdate.log for me please.
 
Just wondering, did you ever consider upgrading your system to Windows 10?
 
Aura said:
Just wondering, did you ever consider upgrading your system to Windows 10?
Click to expand...

Sorry for the delay; I was out of town.

I had, but I decided against the upgrade for the popular reasons (I never did an install/roll back). The decision to keep win7 (and be patched) led me to the failed install.
 
You must log in or register to reply here.
Back
Top