[SOLVED] [W7SP1Pro x64] MissingWinningComponentKey errors

BlackHole

Member
Joined
Nov 10, 2017
Posts
12
Hello,

I see this is the most suitable section of the forum to explain my problem, if any administrator thinks it would be better located in another section, please do not hesitate to move it accordingly.

This lame Edge browser lost all I wrote in the last 2 hours, because it my session expired and couldn't recover the text by going back. Ok. I hope I remember all the words, it's harder for me to explain because English isn't my native language and the keyboard in this computer is very lousy.

I am using Windows 7 Professional 64 bits in my main system. Writing now from a Windows 10 browser in a small laptop (I really DO hate this operating system), until I get the big one fixed. Since I'm using the spanish version, I will try to translate the messages to english, but the translation could not be the exact one you'd find in a native english environment. I hope you'll understand.

A couple of weeks ago, since the C: partition in the boot drive was getting full, I decided to use the "Disk space cleanup manager" (CLEANMGR.EXE) to remove the Windows Update files that could be laying around, which summed 10 GB (this system hasn't be formatted since 2010). It really took a big time to finish and I forgot about it.

Yesterday, there was an update for the Avast antivirus, so I rebooted the machine at 2 AM in order to apply it. When I got the message "Limpiando..." (cleaning) on scren, then I realized that the cleanup manager had only flagged the files for deletion, but had not deleted them yet. I waited 30 minutes, but it was already too late and I went to sleep. Glad I did, since it finished at 11 AM, 9 hours later.

When I woke up, the computer was still busy and when it rebooted itself, everything was very slow and the hard drive activity led wasn't turning off. At first, I thought that the Avast antivirus update was to blame, so I uninstalled the program. It forced me to reboot, but I got the message that the system was "Getting ready" and I should not turn off the computer. However, 30 minutes later, I was desperate and I pressed the reset button in the case.

When I turned on the computer, the system was slightly more responsible, but was still very slow. The second thing I thought, was that the drive could have some physical errors, since I have the experience that a bad hard drive provoked symptoms alike, but CrystalDiskInfo S.M.A.R.T report showed that the disk was in good state with zero sector errors pending and zero relocations. The disk was healthy and that was not the problem.

I suddenly saw that the C: partition was 94 GB out of 100 GB. I launched TreeSizeFree tool to check where the space has been used. It's a program that normally lasts a few seconds to parse the folder sizes, but it took 20+ minutes to list them. The folder %LOCALAPPDATA%\Microsoft\Windows\WER\ReportQueuing was 47 GB long and increasing every minute!

So I decided to check the Event Viewer. It took quite a long time to open, but showed that there were thousands of events in the last 24 hours, related to MissingWinningComponentKey errors in lots of amd64_some_numbers files in the system. I needed the space, so I emptied all the event logs and rebooted. It took a long time to reboot, but I waited. 2 hours later, the WER folder was again 19 GB in size!

I launched a command prompt and tried to issue a sfc /scannow order, but I got a message saying that another system recovery process was in being executed and I should wait for it to finish. I cannot escape from that loop and don't know what to do.

Thanks in advance.
 
Re: [W7 Pro x64] MissingWinningComponentKey errors

Information update: I started the computer in Safe Mode, and the sfc /scannow command finished without any integrity errors. Then I downloaded the System Update Readyness Tool (KB947821) for Windows 7 64 bits. However, I wasn't allowed to launch it in safe mode and had to start in normal mode. This is the summary of the CheckSUR log, the full contents are attached below, just in case...
Code:
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2017-11-11 01:19
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
[...]
Summary:
Seconds executed: 1969
 Found 2237 errors
 Fixed 217 errors
  CSI Catalog Missing Total count: 4
  Fixed: CSI Catalog Missing.  Total count: 4
  CSI Missing Deployment Key Total count: 1779
  CSI C Mark Deployment Missing Total count: 5
  CSI F Mark Bad Type Total count: 89
  Fixed: CSI F Mark Bad Type.  Total count: 89
  CSI F Mark Missing Total count: 8
  Fixed: CSI F Mark Missing.  Total count: 8
  CSI Missing Winning Component Key Total count: 352
  Fixed: CSI Missing Winning Component Key.  Total count: 116
 
Re: [W7 Pro x64] MissingWinningComponentKey errors

Update 2: I have tried repairing with CheckSUR 3 times more. I attach the logs below, but there are still 240 errors that cannot be fixed. The system is again responsive and the lagging is gone. I have just reinstalled Avast and everything seems fine. However, I don't know if they are orphan entries, or are indeed important files that should be present. Also I don't know if I should use the SCFFix tool.

Please take a look when you have time. Thanks.
 

Attachments

Re: [W7 Pro x64] MissingWinningComponentKey errors

Hello and welcome,

Which version of Avast did you install ?
 
Re: [W7 Pro x64] MissingWinningComponentKey errors

After the problems seemed to dissapear? Well, the latest one in their web, 17.8.2318
I don't know which was the version before when it auto-updated itself and the problems started, probably the last but one.
 
Please follow the instructions below.

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

Thanks for your answer. Atacched below are the logs from both tools, hope you don't mind they are zipped even if they weren't too big.
It found 220 errors and fixed 175. We're narrowing the gap :)
 

Attachments

Well done.
Please follow the instructions below.

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

Please follow the instructions below.

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

Thank you for your patience. The results show 3 errors fixed and 6 pending this time.

After applying SURT, the update KB890830 (which was already installed some weeks ago) has reappeared in the listing of available updates.

What do I do with that one?
 

Attachments

Please follow the instructions below.

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

I finally found the remaining one's.
Please follow the instructions below.

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

2 errors left...
The CheckSur log reports that the 2 remaining errors are fixed.
Please check Windows Update and report the result.
 
Oh..it's true, you're right! I did read too fast and didn't notice. A further SURT shows no errors detected.

I have launched Windows Update and strangely shows two updates that I had already applied:

Malicious Software Removal Tool - October 2017 (KB890380) that I successfully applied on October 31st
Malicious Software Removal Tool - November 2017 (KB890380) that was applied on November 17th

Anyway I have re-applied them and got no errors.

Thank you very much!
 
Yes, it seems so. I have some other Event Logs error entries, but they're not related to Windows Update.

I think we can close this thread.
 
OK. I will close this thread.

All the best.
 

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

Back
Top