(Windows 7) Does anyone have these mums, cats, and manifests? (fixing missing files found by SURT)

FuzzleSnuz

FuzzleSnuz

Active member
Joined
Feb 18, 2023
Posts
35
My Enable/Disable Windows Features recently went blank for some reason, so I'm going through the rigmarole of alleged fixes. (I need to install RSAT, which is failing.) SURT, naturally, is one of the things to try in this situation and I have used it before for other problems with success. But it is ofc a game of luck when it comes to having the necessary files on hand...

CheckSUR.log:
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2023-06-28 21:36

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f) CBS Catalog Missing 0x00000002 servicing\Packages\Package_251_for_KB4022168~31bf3856ad364e35~amd64~~6.1.1.7.cat
(f) CBS Catalog Missing 0x00000002 servicing\Packages\Package_5_for_KB4040980~31bf3856ad364e35~amd64~~6.1.1.0.cat

Checking Package Watchlist

Checking Component Watchlist

Checking Packages
(f) CBS MUM Missing 0x00000002 servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.24.5.mum
(f) CBS Registry Error 0x80070002 Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.25.1 failed to get CurrentState
(f) CBS Registry Error 0x80070002 Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.25.1 failed to get Visibility
(f) CBS MUM Missing 0x00000002 servicing\Packages\Package_1_for_KB4493132~31bf3856ad364e35~amd64~~6.1.3.1.mum
(f) CBS MUM Missing 0x00000002 servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.24.5.mum
(f) CBS Registry Error 0x80070002 Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.25.1 failed to get CurrentState
(f) CBS Registry Error 0x80070002 Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.25.1 failed to get Visibility
(f) CBS MUM Missing 0x00000002 servicing\Packages\Package_4_for_KB4040980~31bf3856ad364e35~amd64~~6.1.1.0.mum
(f) CBS MUM Missing 0x00000002 servicing\Packages\Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.24.5.mum
(f) CBS Registry Error 0x80070002 Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.25.1 failed to get CurrentState
(f) CBS Registry Error 0x80070002 Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.25.1 failed to get Visibility
(f) CBS MUM Missing 0x00000002 servicing\Packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.24.2.mum
(f) CBS MUM Missing 0x00000002 servicing\Packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.24.5.mum
(f) CBS MUM Missing 0x00000002 servicing\Packages\Package_for_KB4493132_SP1~31bf3856ad364e35~amd64~~6.1.3.1.mum
(f) CBS MUM Missing 0x00000002 servicing\Packages\Package_for_KB4493132~31bf3856ad364e35~amd64~~6.1.1.4.mum
(f) CBS MUM Missing 0x00000002 servicing\Packages\Package_for_KB4493132~31bf3856ad364e35~amd64~~6.1.2.2.mum
(f) CBS MUM Missing 0x00000002 servicing\Packages\Package_for_KB4493132~31bf3856ad364e35~amd64~~6.1.3.1.mum

Checking Component Store
(f) CSI Manifest Missing 0x00000002 wow64_microsoft-windows-w..owsupdateclient-aux_31bf3856ad364e35_7.6.7601.23735_none_d83d9725c666a650.manifest wow64_microsoft-windows-w..owsupdateclient-aux_31bf3856ad364e35_7.6.7601.23735_none_d83d9725c666a650
(f) CSI Manifest Missing 0x00000002 x86_microsoft-windows-m..ditevtlog.resources_31bf3856ad364e35_6.1.7601.23642_en-us_5c740cc1d1567409.manifest x86_microsoft-windows-m..ditevtlog.resources_31bf3856ad364e35_6.1.7601.23642_en-us_5c740cc1d1567409
(f) CSI Manifest Missing 0x00000002 wow64_microsoft-windows-w..pdateclient-activex_31bf3856ad364e35_7.6.7601.23735_none_824857666c1dd84c.manifest wow64_microsoft-windows-w..pdateclient-activex_31bf3856ad364e35_7.6.7601.23735_none_824857666c1dd84c
(f) CSI Manifest Missing 0x00000002 wow64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.23717_none_21fa9b7afea23234.manifest wow64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.23717_none_21fa9b7afea23234
(f) CSI Payload File Missing 0x00000000 wmp.dll amd64_microsoft-windows-mediaplayer-core_31bf3856ad364e35_6.1.7601.23517_none_6a1c36c17ed465c0
(f) CSI Payload File Missing 0x00000000 wmploc.DLL amd64_microsoft-windows-mediaplayer-core_31bf3856ad364e35_6.1.7601.23517_none_6a1c36c17ed465c0
(f) CSI Payload File Missing 0x00000000 certcli.dll amd64_microsoft-windows-c..tionauthorityclient_31bf3856ad364e35_6.1.7601.23816_none_362f2e866c63126f

Summary:
Seconds executed: 4630
Found 26 errors
CSI Manifest Missing Total count: 4
CSI Payload File Missing Total count: 3
CBS MUM Missing Total count: 11
CBS Catalog Missing Total count: 2
CBS Registry Error Total count: 6

Unavailable repair files:
winsxs\manifests\wow64_microsoft-windows-w..owsupdateclient-aux_31bf3856ad364e35_7.6.7601.23735_none_d83d9725c666a650.manifest
winsxs\manifests\x86_microsoft-windows-m..ditevtlog.resources_31bf3856ad364e35_6.1.7601.23642_en-us_5c740cc1d1567409.manifest
winsxs\manifests\wow64_microsoft-windows-w..pdateclient-activex_31bf3856ad364e35_7.6.7601.23735_none_824857666c1dd84c.manifest
winsxs\manifests\wow64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.23717_none_21fa9b7afea23234.manifest
servicing\packages\Package_251_for_KB4022168~31bf3856ad364e35~amd64~~6.1.1.7.mum
servicing\packages\Package_5_for_KB4040980~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.24.5.mum
servicing\packages\Package_1_for_KB4493132~31bf3856ad364e35~amd64~~6.1.3.1.mum
servicing\packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.24.5.mum
servicing\packages\Package_4_for_KB4040980~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.24.5.mum
servicing\packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.24.2.mum
servicing\packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.24.5.mum
servicing\packages\Package_for_KB4493132_SP1~31bf3856ad364e35~amd64~~6.1.3.1.mum
servicing\packages\Package_for_KB4493132~31bf3856ad364e35~amd64~~6.1.1.4.mum
servicing\packages\Package_for_KB4493132~31bf3856ad364e35~amd64~~6.1.2.2.mum
servicing\packages\Package_for_KB4493132~31bf3856ad364e35~amd64~~6.1.3.1.mum
servicing\packages\Package_251_for_KB4022168~31bf3856ad364e35~amd64~~6.1.1.7.cat
servicing\packages\Package_5_for_KB4040980~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.24.5.cat
servicing\packages\Package_1_for_KB4493132~31bf3856ad364e35~amd64~~6.1.3.1.cat
servicing\packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.24.5.cat
servicing\packages\Package_4_for_KB4040980~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.24.5.cat
servicing\packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.24.2.cat
servicing\packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.24.5.cat
servicing\packages\Package_for_KB4493132_SP1~31bf3856ad364e35~amd64~~6.1.3.1.cat
servicing\packages\Package_for_KB4493132~31bf3856ad364e35~amd64~~6.1.1.4.cat
servicing\packages\Package_for_KB4493132~31bf3856ad364e35~amd64~~6.1.2.2.cat
servicing\packages\Package_for_KB4493132~31bf3856ad364e35~amd64~~6.1.3.1.cat
NB: Ignore the 2 entries for wmp.dll and wmploc.dll. I use WMP11 and I have been very careful to prevent SFC from making the WMP11 6.0.600x.x files from swimming upstream into my winsxs and replacing the proper 6.1.760x.x files. So SURT is correctly identifying them as "corrupt".

M$ redacts update files and Google searches for these hashes are turning up nothing. I've recovered the KB4040980 files from another one of my PCs that luckily had them, but all the others are all non-existant as far as our censored internet is concerned. Not that long ago, there used to be people who would post massive collections of mum, cat, and manifest files on places like Google Drive or OneDrive. Super helpful if I had this problem in back in say 2020 when that OneDrive link was first shared. Not very helpful if I have this problem today in 2023 after the owners of those files deleted them (or the file hosts did). 😑 All the links I've found & tried are dead.

While I really, really wish someone would share a permanent, public collection of these files on a safe upload host, I've noticed there are people here on these forums that have private hoards/collections and will selectively share individual files from said collection for SOL people like who post their SURT logs. I don't like having to make these kind of posts for a one-off solution for one specific person with one specific problem that no one else on the internet will likely be able to benefit from if they find this thread through the Googles, but I'm just not having any luck tracking down these files myself.

Soo... does anybody here have these mums, cats, and manifests?
Thanks much in advance!

mums cats and manifests.png
 
Last edited:
Hello and welcome,

Please attach the file CheckSUR.log to your next reply.
 
Hi, thanks for the reply.

The contents of the relevant CheckSUR.log file are present in my OP. You can click on the button labeled "Spoiler: Show contents" to read it.

Attached to this message is the exact same log data (again).
 

Attachments

The contents of the relevant CheckSUR.log file are present in my OP. You can click on the button labeled "Spoiler: Show contents" to read it.
Click to expand...
I know but I needed the file itself, not only the content.

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.
  • Attach that file to your next reply.

Step 2:
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.
 

Attachments

Last edited:

Attachments

Remove Update Manually
  1. Click on the Start button and in the search box, type Command Prompt.
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator.
  3. When command prompt opens, copy and paste the following command into it, then press enter.
    wusa /uninstall /KB:4493132
  4. Let me know if it says it was successful or if there are any errors.
 
Copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.
 
Captured from fresh boot; log starts and ends with the wusa /uninstall /KB:4493132 command.
 

Attachments

FRST Registry Search
  1. Click the Start button and choose Control Panel.
  2. In the upper right corner ensure the View by: is set to Category.
  3. Select the Programs group.
  4. Click the Turn Windows features on or off link. This will bring up the Windows Features dialog.
    Note: This loads your components hive which is what we want. Please keep this dialog open while you perform the remaining steps. You can minimize it if you wish but keep it open.
  5. Download the Farbar Recovery Scan Tool and save it to your Desktop:
    64-bit: Downloading Farbar Recovery Scan Tool
    Note: Your antivirus program may report FRST incorrectly as an infection. If so, disable the real-time protection when downloading and running FRST.
  6. Right-click on the file FRST64.exe and choose Run as administrator.
  7. Copy and paste KB4493132 into the Search box and click the Search Registry button.
  8. When the scan is complete, a message will display that 'SearchReg.txt' is saved in the same folder FRST was started from. Notepad will open this file also. Close Notepad and attach the file 'SearchReg.txt' to your next reply.
  9. You may close any remaining open windows now.
 
Attached is the SearchReg.txt log file.

I should note that my OptionalFeatures.exe shows an empty list, which I why I was trying to get a clean bill from SURT in the first place.
asdfsdfgsehr.png
Hopefully whatever is breaking OptionalFeatures did not interfere with the results from FRST.
 

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. Attach the logfile Fixlog.txt to 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

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 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.
  • Attach that file to your next reply.
 

Attachments

FRST's fixlog.txt as well as CheckSUR.log from running SURT after FRST.

Still missing 3 payload files, have 3 corrupt mums (Windows still does not like three files from KB2952664), and 6 registry errors (all KB2952664).
 

Attachments

Still missing 3 payload files, have 3 corrupt mums (Windows still does not like three files from KB2952664), and 6 registry errors (all KB2952664).
Click to expand...
Please be patient.

Install Update with DISM
  1. Download the update MSU here: http://download.windowsupdate.com/c..._9c592f060c857166bb548b021223ed4b4cfe4d37.msu
  2. Copy the MSU file to a convenient location (such as C:\temp).
  3. Click on the Start button and in the search box, type Command Prompt
  4. When you see Command Prompt on the list, right-click on it and select Run as administrator
  5. 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-v25-x64_9c592f060c857166bb548b021223ed4b4cfe4d37.msu -f:* C:\temp

    DISM.exe /Online /Add-Package /PackagePath:C:\temp\windows6.1-kb2952664-v25-x64.cab

  6. You should receive the message:
    The operation completed successfully.
    Make sure to allow the computer to restart if prompted.
  7. If you receive any other message:
    Post a screenshot of the Commandprompt window.
    Zip and attach the file C:\Windows\Logs\CBS\CBS.log
 
PeterJ said:
Please be patient.
Click to expand...
I was just adding a quick glance summary of the SURT log. I'm not in any time pressure to get RSAT up and running on this machine, so I don't mind at all if this takes longer to get fully fixed. I was surprised that fixing this has gone deeper than just giving SURT the missing files, though. I really do appreciate all the continued help you've given me so far for each step of the solution.

Integrating the files with dism seemed to work just fine...
cmd.png

...but SURT still doesn't like them.

After dism, I rebooted and then re-ran SURT, which still complained about KB2952664. It looks like it's tripped up on the 6.1.1.3 files being named 6.1.24.5 or vice versa. Attached is the CheckSUR.log.
 

Attachments

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 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.
  • Attach that file to 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

In your initial post you said:
My Enable/Disable Windows Features recently went blank for some reason, so I'm going through the rigmarole of alleged fixes. (I need to install RSAT, which is failing.)
Click to expand...
Are both still failing ?
 
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