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

PeterJ said:
In your initial post you said:
Are both still failing ?
Click to expand...
Yes, unfortunately the "Turn Windows feature on or off" dialog is still empty.

Attempting to install RSAT goes nowhere because it stalls out on "Initializing installation..." and never completes. I've waited up to 10 hours before giving up and killing wusa. During these 10 hours, the TrustedInstaller process appears to be stuck in a death loop because the CPU load and memory allocation remain exactly same value for the entire 10 hours - and during this time there is zero disk activity and it does not write any new lines to CBS.log. Now do I know that trustedinstaller might actually be programmed by monkeys since it makes some horrifically slow & wasteful queries instead of doing things the sane way, but I've never seen it get stuck like this for 10 hours with zero cpu/mem/disk/log changes. So I really have no idea what is wrong with it. I'm guessing it is related to the OptionalFeatures dialog being empty, though, i.e. both might be two symptoms of a single (unknown) root problem.

My hope was that I could get a clean bill from SURT to at least rule out the possibility of corruption in the sxs and servicing parts of Windows. Then figure out where to go next if OptionalFeatures is still broken.
 
Last edited:
Ok. I was just asking for the current state of your machine. Not giving up if that is what you think.

Export registry as hive
  • Click on the Start button and in the search box, type regedit
  • When you see regedit on the list, right-click on it and select Run as administrator.
  • When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing

  • Once selected, click File > Export....
  • Change the Save as type: to Registry Hive Files (*.*).
  • Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
  • Right-click on the saved file and choose Send To -> Compressed (zipped) Folder.
  • Attach the .ZIP file to your next post.
  • If the file is too large to upload here, please upload to Gofile or WeTransfer and just provide the downloadlink here.
 
FRST File Search
  1. Right-click on the file FRST64.exe and choose Run as administrator.
  2. Copy and paste Package_for_KB2952664~31bf3856ad364e35~amd64* into the Search box and click the Search Files button.
  3. When the scan is complete, a message will display that 'Search.txt' is saved in the same folder FRST was started from. Notepad will open this file also.
  4. Close Notepad and attach the file 'Search.txt' to your next reply.
 
SFC Scan
  1. Click 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 commands into it, press enter after each.

    Code: 
    sfc /scannow
    Wait for this to finish before you continue

    Code: 
    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
    Note: if the file is too big to upload to your next post please upload via a service such as Gofile or WeTransfer and just provide the download link.
 
Results from sfc. Log is attached.
result.png

Despite the "no errors found" result, I should note that this result may not be accurate. I know sfc can make bad files swim "upstream" and replace the known good versions in the component store. This exact thing has happened to this computer at least once before, after I replaced wmp 12 with wmp 11, and then ran sfc sometime later which replaced the wmp 12 files in the component store with the wmp 11 versions. I did eventually fix this much later, and I have learned a lot more about Windows internals since then so I try very hard to avoid making sfc pollute winsxs with bad versions of files. But it is entirely possible that there are other rogue files in the component store from the past that sfc is erroneously giving a pass.
 

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

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:2952664
  4. Let me know if it says it was successful or if there are any errors.
 
I was not able to uninstall the update. Using the wusa command, the progress bar in the wusa uninstall dialog reached 100% and the dialog closed normally. But, when I went to Installed Updates and searched for KB2952664, I saw it was still installed. So I tried to uninstall it using the Installed Updates panel this time. After the uninstall appeared to complete and the Installed Updates list refreshed, KB2952664 was still listed as installed. For good measure, I ran the wusa command again. Just like the first time, the uninstall appeared to complete 100% successfully, but KB2952664 still appeared in the Installed Updates list.

Attached is the relevant CBS.log created by the wusa uninstall command
 

Attachments

Please do following only.

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. Right-click on the file FRST64.exe and choose Run as administrator.
    Note: Your antivirus program may report FRST incorrectly as an infection. If so, disable the real-time protection when downloading and running FRST.
  6. Copy and paste KB2952664 into the Search box and click the Search Registry button.
  7. 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.
  8. You may close any remaining open windows now.
 
OptionalFeatures is now suddenly working again. The list populates and correctly displays the enabled/disabled status of the various features. I haven't opened it since my Wednesday post, so any of the procedures done since then could have been the magic feather.

At any rate, attached is the SearchReg.txt produced by FRST. I'd still like to get a clean bill from SURT before I wrap this up and consider the problem resolved.
 

Attachments

OptionalFeatures is now suddenly working again.
Click to expand...
Great.

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

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

FRST 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. Right-click on the file FRST64.exe and choose Run as administrator.
    Note: Your antivirus program may report FRST incorrectly as an infection. If so, disable the real-time protection when downloading and running FRST.
  6. Copy and paste SearchAll:KB2952664 into the Search box and click the Search Files button.
  7. When the scan is complete, a message will display that 'Search.txt' is saved in the same folder FRST was started from. Notepad will open this file also. Close Notepad and attach the file 'Search.txt' to your next reply.
  8. You may close any remaining open windows now.
 
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.
 

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