SURT total detected corruption count

pgfiore

Member
Joined
Dec 6, 2016
Posts
7
Thank in advance to give it a look:
[enclosed CheckSUR.log]

SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-12-06 19:03:26.985
Microsoft Windows Server 2008 R2 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: 70
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.


Successfully processed all directives.


Failed to generate a complete zip file. Upload aborted.


SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2016-12-06 19:08:30.752
----------------------EOF-----------------------
 

Attachments

your welcome
if possibile yes; I wasn't able to fix it.
However the server is up and running and that problem does not seem to impact its job
 
No problem. Here's what I need you to do. I'm going to have you re-run SURT one more time and also provide your components hive.

Step#1 - Re-Run SURT and provide resulting CheckSUR.log

Step#2 - Retrieve Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
4. The file will likely be too large to upload here so please upload to SendSpace and just provide the link here.
 
Ciao
I was not able to copy directly the COMPONENTS files as in-use despite the reboot. I backuped everything using regbak and uploading the system part of the its result.

And I used dropbox sorry (sendspace is asking for the recipient email): Dropbox - RegBak.zip

Thank in advance
pf
 

Attachments

Let's start with the following.

Step#1 - 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. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCScript.txt, and save this to your Desktop.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
  5. Drag the file SFCScript.txt 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
 

Attachments

SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-12-16 09:55:49.376
Microsoft Windows Server 2008 R2 Service Pack 1 - amd64
Using .txt script file at C:\Users\administrator\Downloads\SFCFix\SFCScript.txt [0]


RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-cryptbase_31bf3856ad364e35_none_88c0c64358da105d\6.1.

Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-cryptbase_31bf3856ad364e35_none_88c0c64358da105d\6.1.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-cryptbase_31bf3856ad364e35_none_88c0c64358da105d\6.1.
RegistryScript:: directive completed successfully.


Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2016-12-16 09:55:49.681
Script hash: /+x/+lwIqHoDfhrSIkVuJS1/AYj3BIcyBk4unR6M2AQ=
----------------------EOF-----------------------
 
Thank for your help
here is the last log:

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2016-12-19 10:17


Checking Windows Servicing Packages


Checking Package Manifests and Catalogs


Checking Package Watchlist


Checking Component Watchlist


Checking Packages


Checking Component Store
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-cryptbase_31bf3856ad364e35_6.1.7601.19044_none_c36b3415c4b216c8
(f) CSI Missing Winning Component Key 0x00000000 wow64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.19043_none_0ea39367a7e5006d
(f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-security-credssp_31bf3856ad364e35_6.1.7601.19043_none_c59df43effeb99d7
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-security-digest_31bf3856ad364e35_6.1.7601.19044_none_98d2a9b4936d335c
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-cryptbase_31bf3856ad364e35_6.1.7601.19043_none_c36a33cbc4b2fd71
(f) CSI Missing Winning Component Key 0x00000000 wow64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7601.19043_none_8a6f53b3a05c9ef8
(f) CSI Missing Winning Component Key 0x00000000 wow64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7601.19043_none_e50bf578ada48b4f
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-msauditevtlog_31bf3856ad364e35_6.1.7601.19044_none_2547d8eb8f25944f
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-security-digest_31bf3856ad364e35_6.1.7601.19043_none_98d1a96a936e1a05
(f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-bcrypt-primitives-dll_31bf3856ad364e35_6.1.7601.19044_none_14183c7e7564fb39
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7601.19044_none_44dc3bc8c785af8b
(f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-cryptbase_31bf3856ad364e35_6.1.7601.19044_none_674c98920c54a592
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7601.19043_none_dab74b267943c954
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-msauditevtlog_31bf3856ad364e35_6.1.7601.19043_none_2546d8a18f267af8
(f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-m..ditevtlog.resources_31bf3856ad364e35_6.1.7601.19044_en-us_5bec670cb837152a
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-lsa.resources_31bf3856ad364e35_6.1.7601.19044_en-us_e4ad32eead5376ba
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-bcrypt-primitives-dll_31bf3856ad364e35_6.1.7601.19043_none_7035d7b82dc35318
(f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-msauditevtlog_31bf3856ad364e35_6.1.7601.19043_none_c9283d1dd6c909c2
(f) CSI Missing Winning Component Key 0x00000000 wow64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.19044_none_0ea493b1a7e419c4
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-ncrypt-dll_31bf3856ad364e35_6.1.7601.19044_none_bbe3b42f08542e36
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-rpc-local_31bf3856ad364e35_6.1.7601.19043_none_11fefd6a5bcd559b
(f) CSI Missing Winning Component Key 0x00000000 wow64_microsoft-windows-rpc-local_31bf3856ad364e35_6.1.7601.19044_none_1c54a806902d30ed
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-security-credssp_31bf3856ad364e35_6.1.7601.19044_none_21bd900cb8482464
(f) CSI Missing Winning Component Key 0x00000000 wow64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7601.19044_none_8a7053fda05bb84f
(f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-ncrypt-dll_31bf3856ad364e35_6.1.7601.19043_none_5fc418614ff7a3a9
(f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-bcrypt-primitives-dll_31bf3856ad364e35_6.1.7601.19043_none_14173c347565e1e2
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-rpc-local_31bf3856ad364e35_6.1.7601.19044_none_11fffdb45bcc6ef2
(f) CSI Missing Winning Component Key 0x00000000 wow64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7601.19044_none_4f30e61afbe67186
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7601.19043_none_44db3b7ec7869634
(f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-m..ditevtlog.resources_31bf3856ad364e35_6.1.7601.19043_en-us_5beb66c2b837fbd3
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-smb10-minirdr_31bf3856ad364e35_6.1.7601.19043_none_e6a8e9dc6227b3c1
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-m..ditevtlog.resources_31bf3856ad364e35_6.1.7601.19044_en-us_b80b029070948660
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-smbminirdr_31bf3856ad364e35_6.1.7601.19044_none_dd96cbd267d58eb6
(f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-msauditevtlog_31bf3856ad364e35_6.1.7601.19044_none_c9293d67d6c82319
(f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-ncrypt-dll_31bf3856ad364e35_6.1.7601.19044_none_5fc518ab4ff6bd00
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-smb20-minirdr_31bf3856ad364e35_6.1.7601.19044_none_e8e05438a07e0089
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7601.19044_none_dab84b707942e2ab
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.19043_none_044ee91573843e72
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7601.19043_none_801aa9616bfbdcfd
(f) CSI Missing Winning Component Key 0x00000000 wow64_microsoft-windows-security-digest_31bf3856ad364e35_6.1.7601.19044_none_a3275406c7cdf557
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-security-credssp_31bf3856ad364e35_6.1.7601.19043_none_21bc8fc2b8490b0d
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7601.19044_none_801ba9ab6bfaf654
(f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-security-credssp_31bf3856ad364e35_6.1.7601.19044_none_c59ef488ffeab32e
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-ncrypt-dll_31bf3856ad364e35_6.1.7601.19043_none_bbe2b3e5085514df
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-bcrypt-primitives-dll_31bf3856ad364e35_6.1.7601.19044_none_7036d8022dc26c6f
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-smb20-minirdr_31bf3856ad364e35_6.1.7601.19043_none_e8df53eea07ee732
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-smbminirdr_31bf3856ad364e35_6.1.7601.19043_none_dd95cb8867d6755f
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-smb10-minirdr_31bf3856ad364e35_6.1.7601.19044_none_e6a9ea266226cd18
(f) CSI Missing Winning Component Key 0x00000000 wow64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7601.19044_none_e50cf5c2ada3a4a6
(f) CSI Missing Winning Component Key 0x00000000 wow64_microsoft-windows-security-digest_31bf3856ad364e35_6.1.7601.19043_none_a32653bcc7cedc00
(f) CSI Missing Winning Component Key 0x00000000 wow64_microsoft-windows-rpc-local_31bf3856ad364e35_6.1.7601.19043_none_1c53a7bc902e1796
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-lsa.resources_31bf3856ad364e35_6.1.7601.19043_en-us_e4ac32a4ad545d63
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-m..ditevtlog.resources_31bf3856ad364e35_6.1.7601.19043_en-us_b80a024670956d09
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.19044_none_044fe95f738357c9
(f) CSI Missing Winning Component Key 0x00000000 wow64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7601.19043_none_4f2fe5d0fbe7582f


Summary:
Seconds executed: 720
Found 55 errors
CSI Missing Winning Component Key Total count: 55
 
Please do the following.

Step#1 - 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. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCScript.txt, and save this to your Desktop.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
  5. Drag the file SFCScript.txt 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
 

Attachments

I went a step ahead already and run SURT
Many thank, everything sounds ok now.
ciao

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2016-12-20 10:55


Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store

Summary:
Seconds executed: 533
No errors detected
 

Attachments

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

Back
Top