Windows 7 update problems

[NoelDP]

If there were no CBS.log created, the CBSPersist couldn't be created, since they are purely the compressed content of 'old' CBS.log files.
There is always the possibility that you have a 'cleaner' installed that wipes the log file at every boot - but I think it's unlikely, since the Persist files appear to be current.

The problem here appears to lie with the Windows Update Agent install - which seems to have barfed part-way through.


Please run the CheckSUR tool again - it may give us more clues to the source of the problem - and post the CheckSUR.log file

 

[larryfoster]

Thanks for your continued patience.

The only thing that is there is a CBS "text document that is now 95 Mb that I can't open or access.

Let me try again and will get back to you

 

[NoelDP]

You need to copy the CBS.log file to the desktop, then compress the copy, and upload the compressed file - it should be around 5MB.

 

[larryfoster]

I ran the SURT tool again and got these 2 files.
Looking at them, I get a feeling this isn't what you're looking for.

 

[larryfoster]

After a number of tries I was able to get the SURT to install and create logs.

I have attached them

Hopefully, you are still with me

Thank you

 

[NoelDP]

You have some confusing results there.
in the CheckSUR log, it appears that the run didn't complete - there is no final summary.
Looking in the Persist file, there are multiple runs of the tool
The first one is identical to the latest, and there are differences in between which make me think immediately that you ran Advanced System Care (or similar crapware) and then the fix we ran repaired it completely - and then another run leaves us back at the original problem of a missing manifest with an incomplete scan!

I'll post a fix protocol for the missing manifest a bit later

Checking Component Store
(f)	CSI Manifest Missing	0xC0150018	amd64_microsoft-windows-foundation_31bf3856ad364e35_6.1.7601.17514_none_3e8cb52f886c2db2.manifest	amd64_microsoft-windows-foundation_31bf3856ad364e35_6.1.7601.17514_none_3e8cb52f886c2db2	Unexpected failure fetching item from CdfManifest.  Probably a corrupt manifest.

 

[NoelDP]

Actually - checking a little deeper on the error code there, it seems that this could be a registry problem, rather than a file problem...

I need to have a look at your COMPONENTS registry hive

Please copy the C:\Windows\System32\config\COMPONENTS file (no extension) to your desktop and then compress it - upload the compressed file to your favoured fileshare site (preferably Dropbox or OneDrive) and post a link.

 

[larryfoster]

Thanks for not giving up on me, NoelDP.

I will reiterate that I have not used any cleaners since we started this journey.
I did use Ccleaner fairly regularly for a long time and very recently, Wise.

Both, on your suggestion, have been uninstalled.

I do use Malwarebytes and Superantispyware, both free.

This update problem has been going on for months.

This computer has multiple problems.

Not sure if hardware or software or both

Here is the components link.
https://www.dropbox.com/s/3amo4ihpjo36xba/components.rar?dl=0

 

[NoelDP]

A couple of interesting errors in the registry, there!
Unfortunately, they are in areas which don't appear to be documented at all - so I have no idea what effect they would have.

I've uploaded a file - laraa.zip - to my OneDrive at Noel's OneDrive
Please download and save it to your desktop.
Right-click on the file and select Extract All, and save to the default destination (which should be a folder on the desktop)

Create a new System Restore point

Open an Elevated Command Prompt, and run the following commands.

IF EXIST C:\Windows\System32\config\COMPONENTS.OLD1 DEL C:\Windows\System32\config\COMPONENTS.OLD1
REN C:\Windows\System32\config\COMPONENTS COMPONENTS.OLD1
COPY "%userprofile%\desktop\laraa\COMPONENTS" C:\Windows\System32\config
 
.

If you get an error with any command, STOP THERE - do not reboot! - post for instructions.

Assuming all commands go OK, reboot, and run another CheckSUR scan - post the new CheckSUR.log file.

 

[larryfoster]

Here you go.

Again, thank you NoelDP.

 

[NoelDP]

Well - CheckSUR seems happy, at least!
How is Windows Update behaving now?
DO a Check for Updates - attempt to install only the oldest update found.
If it goes in OK, try the rest
If it fails, post the C:\windows\windowsupdate.log file.

 

[larryfoster]

I have been checking for updates for a very long time.

It just continues but hasn't completed yet.

 

[NoelDP]

It can take a while - I think it'll have to rebuild the database from scratch.

 

[larryfoster]

At least no errors yet.

 

[larryfoster]

It's been about 4 hours and still checking for updates.
I think you fixed one problem but there may be more.

This computer seems to have multiple problems

 

[NoelDP]

Hmmm - that sounds as if it may be stuck in a loop, but give it a couple more hours yet. Open Task Manager and see if there is any activity going on - specifically svchost and TrustedInstaller should be showing fairly high memory usage and CPU count.

 

[larryfoster]

Windows crashed and rebooted.

I did grab an update log just in case

 

[NoelDP]

OKk- run the Fixit from here - it may help.

https://support.microsoft.com/en-us/kb/958046

 

[larryfoster]

That didn't fix the update problem

 

[larryfoster]

Tried to update again and got error 80091007