FuzzleSnuz
Active member
- Feb 18, 2023
- 35
Fixlog.txt result
(Windows 7) Does anyone have these mums, cats, and manifests? (fixing missing files found by SURT)
- Thread starter FuzzleSnuz
- Start date
FuzzleSnuz
Active member
- Feb 18, 2023
- 35
SURT results after reboot
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.
Step 2:
Restart the machine.
Start the System Update Readiness Tool (SURT) again.
On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log to your next reply.
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
- Download the attachment fixlist.txt and save it to your desktop.
- Right-click on FRST64.exe and select "Run as administrator".
- Press the Fix button.
- The tool will now process fixlist.txt.
- 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.
- When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
- Attach the logfile Fixlog.txt to your next reply.
Step 2:
Restart the machine.
Start the System Update Readiness Tool (SURT) again.
On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log to your next reply.
FuzzleSnuz
Active member
- Feb 18, 2023
- 35
Install Update with DISM
- Download the update CAB here: http://au.download.windowsupdate.co..._2ca40901839e21f253bfd29a3122be19d45c4ff5.cab
- Copy the file to a convenient location (such as C:\temp).
- Click on the Start button and in the search box, type Command Prompt
- When you see Command Prompt on the list, right-click on it and select Run as administrator
- When command prompt opens, copy and paste the following commands into it, press enter after each
cd C:\temp
replace C:\temp with your path if different
DISM.exe /Online /Add-Package /PackagePath:C:\temp\windows6.1-kb2952664-v24-x64-express_2ca40901839e21f253bfd29a3122be19d45c4ff5.cab
- You should receive the message:
The operation completed successfully.
Make sure to allow the computer to restart if prompted.
- If you receive any other message:
Post a screenshot of the Commandprompt window.
Zip and attach the file C:\Windows\Logs\CBS\CBS.log
FuzzleSnuz
Active member
- Feb 18, 2023
- 35
Attached is the relevant CBS.log
And here is the relevant DISM.log as well: SafeNote | Encrypt and send files and notes with a link that automatically destruct after being read.
How old is this machine ?
Check for a BIOS update.
Provide the 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 Gofile or WeTransfer and just provide the link here.
Option#2 (only if you are unable to follow the previous instructions)
Check for a BIOS update.
Provide the 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 Gofile or WeTransfer 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 Gofile or WeTransfer and then just provide the link in your reply.
- You can close any open windows you have as well as the RegBak program now.
FuzzleSnuz
Active member
- Feb 18, 2023
- 35
The Windows install on this machine is about 6 years old. The hardware is between 10 and 1 years old. Windows is installed via a conventional MBR partition & boot, and the BIOS is the latest version. I am curious why you think the version of the BIOS might be relevant. Pardon my lack of expertise, but I can't imagine any way that the BIOS program could affect Windows's CBS system; unless you were supposing this machine was a UEFI-based install?
Anyways, here is the components file as requested: SafeNote | Encrypt and send files and notes with a link that automatically destruct after being read.
Also, please excuse me for deviating from your directions, but I did try something which at least managed to reduce the error count reported by SURT (3 -> 2). One of the first things we did was use SFCFix to replace some of the .mums and .cats from KB2952664 with a cabinet you provided. Before we did that, iirc, SURT was reporting zero "CBS MUM Corrupt" errors. After we did that SFCFix step, SURT began reporting those 3 stubborn "CBS MUM Corrupt" errors for KB2952664 that we have been stuck on for a while. I had noticed that SFCFix had produced a backup folder at C:\SFCFix\Backups which included the original versions of the 3 .mum+.cat pairs that SURT does not like. So I copied those backed-up versions to the SURT source packages directory and then ran SURT. It found only 2 "CBS MUM Corrupt" errors instead of 3, and it did replace the 2 it found with the original backed-up copies we had from SFCFix. Hooray, 0 errors from SURT now! Well, until I rebooted and re-ran SURT for good measure, and it started reporting 2 "CBS MUM Corrupt" errors again. But it's just 2 now, instead of 3, so perhaps that is progress?
Attachment 1 is the CheckSUR.log from running SURT with those backed-up .mum and .cat files. (0 grand total errors after the "fixes" it did)
Attachment 2 is the CheckSUR.log from running SURT after the reboot (2 grand total errors)
Anyways, here is the components file as requested: SafeNote | Encrypt and send files and notes with a link that automatically destruct after being read.
Also, please excuse me for deviating from your directions, but I did try something which at least managed to reduce the error count reported by SURT (3 -> 2). One of the first things we did was use SFCFix to replace some of the .mums and .cats from KB2952664 with a cabinet you provided. Before we did that, iirc, SURT was reporting zero "CBS MUM Corrupt" errors. After we did that SFCFix step, SURT began reporting those 3 stubborn "CBS MUM Corrupt" errors for KB2952664 that we have been stuck on for a while. I had noticed that SFCFix had produced a backup folder at C:\SFCFix\Backups which included the original versions of the 3 .mum+.cat pairs that SURT does not like. So I copied those backed-up versions to the SURT source packages directory and then ran SURT. It found only 2 "CBS MUM Corrupt" errors instead of 3, and it did replace the 2 it found with the original backed-up copies we had from SFCFix. Hooray, 0 errors from SURT now! Well, until I rebooted and re-ran SURT for good measure, and it started reporting 2 "CBS MUM Corrupt" errors again. But it's just 2 now, instead of 3, so perhaps that is progress?
Attachment 1 is the CheckSUR.log from running SURT with those backed-up .mum and .cat files. (0 grand total errors after the "fixes" it did)
Attachment 2 is the CheckSUR.log from running SURT after the reboot (2 grand total errors)
Maybe the update we installed last time, with only partial installed, fixed 1 of the 3 issues in the SURT log.
Lets see if this update installs.
Install Update with DISM
Lets see if this update installs.
Install Update with DISM
- Download the update MSU here: http://download.windowsupdate.com/d..._cd95eff6a0b4dc190709f9a0e7a00f782a74ee5c.msu
- Copy the MSU file to a convenient location (such as C:\temp).
- Click on the Start button and in the search box, type Command Prompt
- When you see Command Prompt on the list, right-click on it and select Run as administrator
- When command prompt opens, copy and paste the following commands into it, press enter after each
cd C:\temp
replace C:\temp with your path if different
expand windows6.1-kb2952664-v24-x64_cd95eff6a0b4dc190709f9a0e7a00f782a74ee5c.msu -f:* C:\temp
DISM.exe /Online /Add-Package /PackagePath:C:\temp\windows6.1-kb2952664-v24-x64.cab
- You should receive the message:
The operation completed successfully.
Make sure to allow the computer to restart if prompted.
- If you receive any other message:
Post a screenshot of the Commandprompt window.
Zip and attach the file C:\Windows\Logs\CBS\CBS.log
FuzzleSnuz
Active member
- Feb 18, 2023
- 35
Please excuse my long absence. I've been trying to get RSAT up and running for the last 5 days, since that last set of directions from you seemed to seal the deal and lay those CBS errors to rest once and for all!
Back to Monday. The dism command completed successfully. Afterwards, I ran SURT and it reported 0 grand total errors. To confirm that result, I rebooted and re-ran SURT, and again it came back with 0 grand total errors. Hooray!
And the rest of the week was dealing with RSAT. After I confirmed the clean bill from SURT, I tried to install RSAT again (many times). The MSU install completes without error (after a very long 4-5 hours), which is progress since it was stalling out beforehand. However, when I go to OptionalFeatures to check the box and enable just the one RSAT component I actually need (GPMC), it fails with the message "Not all features were successfully changed". I've tried uninstalling and re-installing the RSAT msu several times and running sfc and surt in between, which is a very slow process because RSAT is a 4-5 hr install and 1-2 hr uninstall, and SURT is another 1 hr as well, which is why it took the whole week for me to post here again. Unfortunately Google isn't being particularly helpful here, since it seems no one else that has experienced this specific problem cared enough to post online about it.
But, at any rate, thank you very, very much for fixing the CBS problems on this machine and getting OptionalFeatures working again. And it only took 50 posts!
Thanks for your patience with me. I do wonder, though, if there is still some CBS corruption elsewhere that might be the reason why I cannot get the RSAT components to enable themselves successfully. If you don't mind going even further down the rabbit hole with me, I'd be more than happy to have your help with fixing that as well.
Back to Monday. The dism command completed successfully. Afterwards, I ran SURT and it reported 0 grand total errors. To confirm that result, I rebooted and re-ran SURT, and again it came back with 0 grand total errors. Hooray!
And the rest of the week was dealing with RSAT. After I confirmed the clean bill from SURT, I tried to install RSAT again (many times). The MSU install completes without error (after a very long 4-5 hours), which is progress since it was stalling out beforehand. However, when I go to OptionalFeatures to check the box and enable just the one RSAT component I actually need (GPMC), it fails with the message "Not all features were successfully changed". I've tried uninstalling and re-installing the RSAT msu several times and running sfc and surt in between, which is a very slow process because RSAT is a 4-5 hr install and 1-2 hr uninstall, and SURT is another 1 hr as well, which is why it took the whole week for me to post here again. Unfortunately Google isn't being particularly helpful here, since it seems no one else that has experienced this specific problem cared enough to post online about it.
But, at any rate, thank you very, very much for fixing the CBS problems on this machine and getting OptionalFeatures working again. And it only took 50 posts!
Thanks for your patience with me. I do wonder, though, if there is still some CBS corruption elsewhere that might be the reason why I cannot get the RSAT components to enable themselves successfully. If you don't mind going even further down the rabbit hole with me, I'd be more than happy to have your help with fixing that as well.No problem.
Great.
Which update or program are you trying to install ? A downloadlink or screenshot would be helpful.
Attach the files C:\Windows\Logs\CBS\cbs.log and C:\Windows\WindowsUpdate.log to your next reply.
FuzzleSnuz
Active member
- Feb 18, 2023
- 35
The MSU I'm installing is Windows6.1-KB958830-x64-RefreshPkg.msu, which is the "refreshed" (see: signed with different cert) installer for RSAT for Win 7 SP1. It is one the many updates redacted by Microsoft, so there is no official public download anymore. Thankfully, the official download link was crawled by the wayback machine, if you need to download it here.
It takes a very long time (4-6 hrs), but the MSU for RSAT does install successfully, and the various RSAT components appear in the OptionalFeatures list, all disabled by default per usual and waiting to be enabled by the user. Everything is fine up to this point.
The problem is when I go to enable one or more RSAT components by checking their box and clicking OK. The progress dialog appears and churns for a minute, but then an error occurs. The only thing from RSAT I need on this machine is GPMC (enabled via the "Group Policy Management Tools" component), so that is what I have been testing with. Here's what that looks like:
At this point, Group Policy Management Tools is not enabled and GPMC is thus not available (search for it in the start menu, get nothing). If I restart my computer and open OptionalFeatures again, the checkbox for Group Policy Management Tools is still disabled. If I check the box, click OK, and wait again, it will fail with the same error again. I can then restart my computer, see Group Policy Management Tools is not enabled, and repeat this process ad infinitum with no results.
Attached below is the relevant lines from CBS.log that were generated during Pic #3 in the sequence above.
No lines were written to WindowsUpdate.log during the picture sequence above. That log was flushed sometime between today and when I last (re)installed RSAT several days ago, so there is no residual data left over from installing the RSAT MSU. I could re-install the RSAT MSU to fill out WindowsUpdate.log, but it really does require an entire day to do because the uninstall takes about 1-2 hours and the install takes about 4-6 hours. I can do that if it's necessary, but I hope that the info from CBS.log is good enough for now.
It takes a very long time (4-6 hrs), but the MSU for RSAT does install successfully, and the various RSAT components appear in the OptionalFeatures list, all disabled by default per usual and waiting to be enabled by the user. Everything is fine up to this point.
The problem is when I go to enable one or more RSAT components by checking their box and clicking OK. The progress dialog appears and churns for a minute, but then an error occurs. The only thing from RSAT I need on this machine is GPMC (enabled via the "Group Policy Management Tools" component), so that is what I have been testing with. Here's what that looks like:
At this point, Group Policy Management Tools is not enabled and GPMC is thus not available (search for it in the start menu, get nothing). If I restart my computer and open OptionalFeatures again, the checkbox for Group Policy Management Tools is still disabled. If I check the box, click OK, and wait again, it will fail with the same error again. I can then restart my computer, see Group Policy Management Tools is not enabled, and repeat this process ad infinitum with no results.
Attached below is the relevant lines from CBS.log that were generated during Pic #3 in the sequence above.
No lines were written to WindowsUpdate.log during the picture sequence above. That log was flushed sometime between today and when I last (re)installed RSAT several days ago, so there is no residual data left over from installing the RSAT MSU. I could re-install the RSAT MSU to fill out WindowsUpdate.log, but it really does require an entire day to do because the uninstall takes about 1-2 hours and the install takes about 4-6 hours. I can do that if it's necessary, but I hope that the info from CBS.log is good enough for 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.
Download the attachment and extract it.
Open the extracted folder, double-click the file regfix.reg.
When prompted allow to change the registry settings.
Report the result.
Step 2:
Restart the computer.
Open an elevated command prompt.
Copy and paste the following commands into it, press enter after each.
Wait for this to finish before you continue
This will create a file, cbs.txt on your Desktop. Zip this file and attach the zipped cbs.txt to your next post.
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
Download the attachment and extract it.
Open the extracted folder, double-click the file regfix.reg.
When prompted allow to change the registry settings.
Report the result.
Step 2:
Restart the computer.
Open an elevated command prompt.
Copy and paste the following commands into it, press enter after each.
Code:
sfc /scannow
Code:
copy %windir%\Logs\CBS\cbs.log "%userprofile%\Desktop\cbs.txt"FuzzleSnuz
Active member
- Feb 18, 2023
- 35
I was unable to complete step 1:
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.
Step 2:
Restart the computer.
Open an elevated command prompt.
Copy and paste the following commands into it, press enter after each.
Wait for this to finish before you continue
This will create a file, cbs.txt on your Desktop. Zip this file and attach the zipped cbs.txt to your next post.
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
- Download the attachment fixlist.txt and save it to your desktop.
- Right-click on FRST64.exe and select "Run as administrator".
- Press the Fix button.
- The tool will now process fixlist.txt.
- 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.
- When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
- Attach the logfile Fixlog.txt to your next reply.
Step 2:
Restart the computer.
Open an elevated command prompt.
Copy and paste the following commands into it, press enter after each.
Code:
sfc /scannow
Code:
copy %windir%\Logs\CBS\cbs.log "%userprofile%\Desktop\cbs.txt"FuzzleSnuz
Active member
- Feb 18, 2023
- 35
FRST step completed without issue, and the log is attached.
SFC found a heap of files to move/replace. Looks like all moves/replaces succeeded due to the end message.
Zipped CBS.log generating during SFC run is last attachment.
SFC found a heap of files to move/replace. Looks like all moves/replaces succeeded due to the end message.
Zipped CBS.log generating during SFC run is last attachment.
Looks good. Any improvement on the issues you reported in message #53 ?
FuzzleSnuz
Active member
- Feb 18, 2023
- 35
D'oh, I should have done that before replying.
Unfortunately the issue is still present. Same error message from OptionalComponents when trying to enable GPMC.
Attached is the relevant CBS.log
Unfortunately the issue is still present. Same error message from OptionalComponents when trying to enable GPMC.
Attached is the relevant CBS.log
Provide the 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 Gofile or WeTransfer and just provide the link here.
Option#2 (only if you are unable to follow the previous instructions)
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 Gofile or WeTransfer 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 Gofile or WeTransfer and then just provide the link in your reply.
- You can close any open windows you have as well as the RegBak program now.
Has Sysnative Forums helped you? Please consider donating to help us support the site!