Windows 7 pro SP1 CheckSUR.log error 0x80070002 and 0x00000000

H

Hasseen

Active member
Joined
Jun 30, 2020
Posts
28
Hi All,

Checking System Update Readiness, the errors found in CheckSUR.log are "CBS Watchlist Component Missing 0x80070002","CSI Missing Deployment Key 0x00000000" and "CSI Missing Winning Component Key 0x00000000"


I tried to fix these errors by using (SFC /SCANNOW), (dism /online /cleanup-image /scanhealth) and SFCFix.exe. Kindly Find below the SFCFix.txt.


CORRUPT: Failed to repair orphaned component "value name not identified" (x86_microsoft-windows-os-kernel_31bf3856ad364e35_0.0.0.0_none_900a574dfc4d4e9e) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (wow64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_4340b53dcf6f3927) on component watchlist

CORRUPT: Failed to repair orphaned component "value name not identified" (amd64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_38ec0aeb9b0e772c) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (amd64_microsoft-windows-r..gistry-trustedtypes_31bf3856ad364e35_0.0.0.0_none_03f68ac42eefca6e) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (amd64_microsoft-windows-os-kernel_31bf3856ad364e35_0.0.0.0_none_ec28f2d1b4aabfd4) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (amd64_microsoft-windows-ntfs_31bf3856ad364e35_0.0.0.0_none_2669baee1d7346ff) on component watchlist.


i need help to fix these problems. Thanks!


Code: 
==============================

SFCFix version 3.0.2.1 by niemiro.

Start time: 2020-07-08 22:29:21.347

Microsoft Windows 7 Service Pack 1 - amd64

Not using a script file.





AutoAnalysis::

WARNING: Failed to backup registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\x86_microsoft-windows-os-kernel_31bf3856ad364e35_0.0.0.0_none_900a574dfc4d4e9e.

CORRUPT: Failed to repair orphaned component "value name not identified" (x86_microsoft-windows-os-kernel_31bf3856ad364e35_0.0.0.0_none_900a574dfc4d4e9e) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (x86_microsoft-windows-os-kernel_31bf3856ad364e35_0.0.0.0_none_900a574dfc4d4e9e) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (x86_microsoft-windows-os-kernel_31bf3856ad364e35_0.0.0.0_none_900a574dfc4d4e9e) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (x86_microsoft-windows-os-kernel_31bf3856ad364e35_0.0.0.0_none_900a574dfc4d4e9e) on component watchlist.



WARNING: Failed to backup registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\wow64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_4340b53dcf6f3927.

CORRUPT: Failed to repair orphaned component "value name not identified" (wow64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_4340b53dcf6f3927) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (wow64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_4340b53dcf6f3927) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (wow64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_4340b53dcf6f3927) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (wow64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_4340b53dcf6f3927) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (wow64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_4340b53dcf6f3927) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (wow64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_4340b53dcf6f3927) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (wow64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_4340b53dcf6f3927) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (wow64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_4340b53dcf6f3927) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (wow64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_4340b53dcf6f3927) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (wow64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_4340b53dcf6f3927) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (wow64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_4340b53dcf6f3927) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (wow64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_4340b53dcf6f3927) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (wow64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_4340b53dcf6f3927) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (wow64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_4340b53dcf6f3927) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (wow64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_4340b53dcf6f3927) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (wow64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_4340b53dcf6f3927) on component watchlist.



WARNING: Failed to backup registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_38ec0aeb9b0e772c.

CORRUPT: Failed to repair orphaned component "value name not identified" (amd64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_38ec0aeb9b0e772c) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (amd64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_38ec0aeb9b0e772c) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (amd64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_38ec0aeb9b0e772c) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (amd64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_38ec0aeb9b0e772c) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (amd64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_38ec0aeb9b0e772c) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (amd64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_38ec0aeb9b0e772c) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (amd64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_38ec0aeb9b0e772c) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (amd64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_38ec0aeb9b0e772c) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (amd64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_38ec0aeb9b0e772c) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (amd64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_38ec0aeb9b0e772c) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (amd64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_38ec0aeb9b0e772c) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (amd64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_38ec0aeb9b0e772c) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (amd64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_38ec0aeb9b0e772c) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (amd64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_38ec0aeb9b0e772c) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (amd64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_38ec0aeb9b0e772c) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (amd64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_38ec0aeb9b0e772c) on component watchlist.



WARNING: Failed to backup registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-r..gistry-trustedtypes_31bf3856ad364e35_0.0.0.0_none_03f68ac42eefca6e.

CORRUPT: Failed to repair orphaned component "value name not identified" (amd64_microsoft-windows-r..gistry-trustedtypes_31bf3856ad364e35_0.0.0.0_none_03f68ac42eefca6e) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (amd64_microsoft-windows-r..gistry-trustedtypes_31bf3856ad364e35_0.0.0.0_none_03f68ac42eefca6e) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (amd64_microsoft-windows-r..gistry-trustedtypes_31bf3856ad364e35_0.0.0.0_none_03f68ac42eefca6e) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (amd64_microsoft-windows-r..gistry-trustedtypes_31bf3856ad364e35_0.0.0.0_none_03f68ac42eefca6e) on component watchlist.



WARNING: Failed to backup registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_0.0.0.0_none_ec28f2d1b4aabfd4.

CORRUPT: Failed to repair orphaned component "value name not identified" (amd64_microsoft-windows-os-kernel_31bf3856ad364e35_0.0.0.0_none_ec28f2d1b4aabfd4) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (amd64_microsoft-windows-os-kernel_31bf3856ad364e35_0.0.0.0_none_ec28f2d1b4aabfd4) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (amd64_microsoft-windows-os-kernel_31bf3856ad364e35_0.0.0.0_none_ec28f2d1b4aabfd4) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (amd64_microsoft-windows-os-kernel_31bf3856ad364e35_0.0.0.0_none_ec28f2d1b4aabfd4) on component watchlist.



WARNING: Failed to backup registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-ntfs_31bf3856ad364e35_0.0.0.0_none_2669baee1d7346ff.

CORRUPT: Failed to repair orphaned component "value name not identified" (amd64_microsoft-windows-ntfs_31bf3856ad364e35_0.0.0.0_none_2669baee1d7346ff) on component watchlist.

CORRUPT: Failed to repair orphaned component "value name not identified" (amd64_microsoft-windows-ntfs_31bf3856ad364e35_0.0.0.0_none_2669baee1d7346ff) on component watchlist.



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: 1713

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 87 datablocks.

Finish time: 2020-07-08 22:31:01.749

=======================================



CBS_CheckSUR.zip
 
Hello and welcome,

Follow the instructions below to run a fresh scan with the System Update Readiness Tool (SURT) and provide a log.
  1. Download SURT for your system. (Windows 7 SP1 x64)
  2. Once downloaded, execute the installer, and go through the installation (this process can take around 15-20 minutes).
  3. On completion, a log will be created in C:\Windows\Logs\CBS\CheckSUR.log.
  4. 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)
 
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. Note: If you find that you need to reboot and are unable to because this is a server then try Option#2 below.
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 Filedropper or SendSpace and just provide the link here.


Option#2 (only if you are unable to follow the previous instructions)

  • Please download the Freeware RegBak from here: Acelogix Software - Download products
     You will find it at the bottom of the page that the link brings you to.
  • Go ahead and install this program and accept all the defaults. After the last install screen the program should open.
  • Click the New Backup button. Accept the defaults and simply click Start.
  • When it says Finished successfully, click the Close button.
  • This will bring you back to the main screen of the program. You will see one entry in this list with the date that you did it. Right-click on this line-item and select Explore Backup...
  • This will bring you into the folder where the backup was made. You should see a Users folder and a Windows folder along with a couple other files. Double-click on the Windows folder to open it. Then open the System32 folder and then config folder. You should see around 6 files in here, one of which is named COMPONENTS.
  • Copy the COMPONENTS file to your Desktop. If the COMPONENTS file does not exist, please fetch it instead from C:\Windows\System32\config\COMPONENTS.
  • Now right-click on the COMPONENTS file that is on your desktop and select Send to > Compressed (zipped) folder.
  • Then please upload the zip file (COMPONENTS.zip) to your favourite file sharing website (it will be too big to upload here). Examples of services to upload to are Filedropper or One Drive or SendSpace and then just provide the link in your reply.
  • You can close any open windows you have as well as the RegBak program now.
 
Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Post the logfile Fixlog.txt as attachment 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 to your next reply.
 

Attachments

Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Post the logfile Fixlog.txt as attachment 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 to your next reply.
 

Attachments

Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Post the logfile Fixlog.txt as attachment 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 to your next reply.
 

Attachments

Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Post the logfile Fixlog.txt as attachment 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 to your next reply.
 

Attachments

Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Post the logfile Fixlog.txt as attachment 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 to your next reply.
 

Attachments

Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Post the logfile Fixlog.txt as attachment 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 to your next reply.
 

Attachments

Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Post the logfile Fixlog.txt as attachment 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 to 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