[SOLVED] Twenty thousand errors in CBS

The link for the SOFTWARE file (instead of that earlier .reg version) has been in the private message box.
 
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 Farbar Recovery Scan Tool and save it to your Desktop:
    64-bit: Downloading Farbar Recovery Scan Tool
  2. Download the attachment fixlist.txt and save it to your desktop.
  3. Right-click on FRST64.exe and select "Run as administrator".
  4. Press the Fix button.
  5. The tool will now process fixlist.txt.
  6. 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.
  7. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  8. 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 in your next reply.
 

Attachments

Last edited:
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 in 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 in your next reply.
 

Attachments

The fix didn't work as expected. Did you restart Windows after you send me the SOFTWARE hive ?
 
Yes. I restarted Windows several times after sending you the SOFTWARE hive. Shouldn't I do that?
 
Shouldn't I do that?
No, leave it running till I send you a fix.
Please provide a fresh copy of the SOFTWARE hive, follow the instructions in message #10.
 
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 in 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 in your next reply.
 

Attachments

Great. All Component Watchlist errors have been fixed.
You may shutdown or restart the machine whenever you like.

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

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

It is indeed a great job. Thanks again. Now there are only 352 missing deployment keys to be fixed.


SFCFix version 3.0.1.0 by niemiro.
Start time: 2019-04-27 19:24:42.438
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at C:\Users\Xiang Song LI\Desktop\SFCFix.zip [0]

PowerCopy::
Successfully took permissions for file or folder C:\Windows\winsxs\wow64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.18539_none_c1e8a48f945da7dd
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.18539_none_1708c9fbb1322437
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.18539_none_b793fa3d5ffce5e2

Successfully copied file C:\Users\Xiang Song LI\AppData\Local\niemiro\Archive\winsxs\wow64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.18539_none_c1e8a48f945da7dd\gdi32.dll to C:\Windows\winsxs\wow64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.18539_none_c1e8a48f945da7dd\gdi32.dll.
Successfully copied file C:\Users\Xiang Song LI\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.18539_none_1708c9fbb1322437\win32k.sys to C:\Windows\winsxs\amd64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.18539_none_1708c9fbb1322437\win32k.sys.
Successfully copied file C:\Users\Xiang Song LI\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.18539_none_b793fa3d5ffce5e2\gdi32.dll to C:\Windows\winsxs\amd64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.18539_none_b793fa3d5ffce5e2\gdi32.dll.

Successfully restored ownership for C:\Windows\winsxs\wow64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.18539_none_c1e8a48f945da7dd
Successfully restored permissions on C:\Windows\winsxs\wow64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.18539_none_c1e8a48f945da7dd
Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.18539_none_1708c9fbb1322437
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.18539_none_1708c9fbb1322437
Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.18539_none_b793fa3d5ffce5e2
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.18539_none_b793fa3d5ffce5e2
PowerCopy:: directive completed successfully.

Successfully processed all directives.
SFCFix version 3.0.1.0 by niemiro has completed.
Currently storing 1444 datablocks.
Finish time: 2019-04-27 19:24:45.928
Script hash: /V365XQKUs842HQjXC8KMzORqV5ErS8txMKHO3tcwRQ=
----------------------EOF-----------------------
 

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 in your next reply.
 

Attachments

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

Back
Top