Solved Multiple Update Failures / Win7 x64 - Unable to Update, Error 800b010

[o0erk0o]

My problems are essentially those expressed in many previous posts, but specifically this one here was most pertinent (aside from the specific updates of course): http://www.sevenforums.com/windows-updates-activation/155225-win7-x64-unable-update-error-800b0100.html

Here is a list of the updates that are giving me trouble...

Important:

• Security Update for Windows 7 for x64-based Systems (KB2631813)
  
  Optional (but I am pretty sure I need a couple of them to fix other, non-Win issues):
  
  • Update for Windows 7 for x64-based Systems (KB2488113)
  • Update for Windows 7 for x64-based Systems (KB2492386)
  • Update for Windows 7 for x64-based Systems (KB2511250)
  • Update for Windows 7 for x64-based Systems (KB2515325)
  • Update for Windows 7 for x64-based Systems (KB2541014)
  • Update for Windows 7 for x64-based Systems (KB982018)
  
  I too have followed all the steps mentioned in the post I have cited, and have attached the same documentation as well in hopes of expediting a solution. Ultimately my hope was that some kind soul would be willing and able to provide a customized solution similar to what the previous poster, CoolStory, received from the user niemiro. Thanks in advance and will be sure to check back shortly!

 

[NoelDP]

From the SFC report, it looks like it found a couple of errors in the .NET 3.5 installation - and fixed them (together with a faulty bmp file)
Have you also run a CHKDSK? - often a random error can indicat file system problems, so it would be worth running CHKDSK C: /R and seeing if that helps.

Niemiro hopefully will be around later to assist - but there's nothing in your reports that suggests anything specific he can do.s

 

[o0erk0o]

Ok, thanks for the reply. I am currently (and have been for 2 hours so far) riunning chkdsk, and will update upon completion. Also, will there be a log file of any type that I should share? As far as having niemiro (sp? - replying from phone) look at it as well, is there a way to get it in front of him, or will he see it?

 

[NoelDP]

He'll pick it up and run with it as soon as he gets to the forum - but he's not around every day.

CHKDSK /R can take a while - depending on the size of the drive, and how many problems it finds (if any).
Once complete, look in the Windows Applications Logs in Event Viewer - the entry will be for WININIT. copy/paste the results if there are errors reported

 

[o0erk0o]

Very good, and thanks for the continued assistance!

I will preface this with the fact that I am learning as I go, so apologize in advance for the ignorance.. but upon reviewing Event Viewer, I did find one instance of Wininit with today's date (there are others from previous "auto-scans" I presume) that was flagged with a Warning. Upon clicking on it, I am provided with just a small bit of information which is as follows:

"Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications."

Windows Operating System;
Version: 6.1.7600.16385;
Event ID: 11;
Event Source: Microsoft-Windows-Wininit;


- System

- Provider

[ Name] Microsoft-Windows-Wininit
[ Guid] {206F6DEA-D3C5-4D10-BC72-989F03C8B84B}

EventID 11

Version 0

Level 3

Task 0

Opcode 0

Keywords 0x4000000000000000

- TimeCreated

[ SystemTime] 2012-02-04T09:49:55.736559600Z

EventRecordID 744320

Correlation

- Execution

[ ProcessID] 764
[ ThreadID] 796

Channel System

Computer Paul-HP

- Security

[ UserID] S-1-5-18


- EventData

StringCount 0
String

Log Name: System
Source: Microsoft-Windows-Wininit
Date: 2/4/2012 4:49:55 AM
Event ID: 11
Task Category: None
Level: Warning
Keywords:
User: SYSTEM
Computer: Paul-HP

Description:

Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Wininit" Guid="{206F6DEA-D3C5-4D10-BC72-989F03C8B84B}" />
<EventID>11</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2012-02-04T09:49:55.736559600Z" />
<EventRecordID>744320</EventRecordID>
<Correlation />
<Execution ProcessID="764" ThreadID="796" />
<Channel>System</Channel>
<Computer>Paul-HP</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="StringCount">0</Data>
<Data Name="String">
</Data>
</EventData>
</Event>


Is this the correct information that you requested, or am I missing something?

PS. Within the Event Viewer's "home page" > Summary of Admin Events, it shows hundreds of Errors + Warnings, of which one is the requested Wininit. Should I be overly concerned with what seems to be a very high number of these?

Thanks again!

 

[NoelDP]

It's actually not - but it *is* very interesting!
It certainly backs up the idea that all is not well in the registry.
http://www.eventid.net/techurl.asp?urlid=100126 applias - you may want to download the article it mentions and read it at your leisure.(http://www.eventid.net/techurl.asp?urlid=100126)

I'll have to read the article myself before I can comment.

 

[o0erk0o]

Quite the extensive read , but do thank you for the information!

Some other background history that may or may not be relevant. Two days ago, I was having issues after updating my ATI gfx drivers/CCC, where the CCC app wasnt loading. In an attempt to rectify these issues, I had to utilize DriveSweeper to remove all the AMD vid drivers for a clean install, which of course includes involves deleting registry files. I have since fixed that issue (after 2 LOOONG days of trial and error-testing), but since I strictly used this tool, felt it was safe and that it wouldnt harm other elements of the registry.

The other possibility might stem from my use of Advanced System Care and CCleaner, which automates the process of "cleaning up one's registry" (amongst other things) as I am sure you are aware. In my ignorance, I assumed all the actions performed by programs such as these would be safe, but am now concerned I was terribly wrong in making such an assumption.

The last, and presumably irrelevant, notable action that I have taken in the past couple days was to uninstall and reinstall all of my .NET framework versions (also suggested by those assisting with the issues I was having with my ATI driver update). That was a fairly seamless process, but thought I would mention it in the event it might shine new light on the situation at all.

 

[NoelDP]

The other possibility might stem from my use of Advanced System Care and CCleaner, which automates the process of "cleaning up one's registry" (amongst other things) as I am sure you are aware. In my ignorance, I assumed all the actions performed by programs such as these would be safe, but am now concerned I was terribly wrong in making such an assumption.

ASC belongs to that select group of Registry Cleaners that has actually managed to break clean installs of Windows. (WiseFixer is another and more common one)

CCleaner is great - but do NOT use the registry cleaner part of it as anything other than a search engine!

ALL Registry Cleaners are hazardous to the health of a machine - and WILL break it sooner or later.

Since you seem to have been using both, it's likely that the situation is unrecoverable by use of their Undo capabilities, but you could try a System Restore back to a time when things worked properly, and see if that works.

 

[o0erk0o]

Well, better to know later than never i suppose

Unfortunately, my attempts at system restore were fruitless yesterday - i received an error message stating that it failed (tried multiple points to no avail) - so given that unfortunate fact, do you think that perhaps using the Windows disk i got with the machine might "fill in the gaps" as it were? I seem to remember an option where you could use the disk to fix any reg errors that may have occurred.. or perhaps there is a DL that MS provides that does the same thing? (I will also begin a preliminary search on my own, but any specific advice as to where to look/what to look for would be greatly appreciated!)

Now knowing all these factors, do you think the root cause of the update failures/errors is a direct result of the reg issues?

 

[o0erk0o]

Now that i think about it, my question essentially contradicts exactly what you suggested earlier re: not using reg cleaners at all... (derp). So i guess my only question really is if utilizing a repair function that i am not aware of would be a viable solution.

Additionally, i have attached a rundown of all the reg errors detected as a .txt, and was thinking perhaps you might be able to identify any SERIOUSLY impactful errors listed. (i.e. i noticed that the first 2 listed were found in "C:\Windows\Installer\*" which obviously was a big red flag as it pertains to updates, but I could just be reading too far into it of course..)

View attachment regreport.txt

 

[NoelDP]

The words LONG BARGEPOLE and DO NOT TOUCH come to mind!!!
Steer well clear of such things, please - they are what got you into this position in the first place.

Yes, a repair install is possibly the best way forward. There is an excellent tutorial on doing it in these forums -
http://www.sevenforums.com/tutorials/3413-repair-install.html?ltr=R

Remember - ask questions *before* starting the job, as it may be too late otherwise.

 

[o0erk0o]

Duly noted - and truthfully i should know better - but whats done is done i suppose..

Anyhow, some good news (finally). In terms of the updates, i have successfully installed 6/7 updates that have been plaguuuuu-ing me, most notably the 1 "Important" update. I ended up just running msconfig, clean-booting, and installing with nothing running. My guess is it had something to do with an AVG process that continued to run despite turning it off via the AVG control panel, but that is a guess - who the heck knows. Either way, its done....... and i suppose i will need to manually run WinUpdate in the future under the same parameters.

*NOTE - the only one that still fails to update is some random IE9 update that i could really care less about as i dont use IE.

I did read that article on Repair Install, and have it bookmarked already - but thanks for sending it my way. I may go ahead and do that (another day... im at wits end with computer repair for the time being) as my system seems to be running just fine atm.

I really want to thank you again for ALL your help and insight, and will go ahead and close this thread out now. Cheers!

 

[NoelDP]

Well done - and good luck.
Clean boot success means that something that's loading at startup is causing the problem - but it could be a nightmare trying to work out what.
I honestly doubt that it's AVG, or we'd have seen more problems - although it could be a comination problem involving AVG and something else.

What security software do you have installed (running or not)? (which version of AVG, as well)

 

[o0erk0o]

Well upon installing AVG, i was sure to completely wipe off any other security software that came preloaded/was used in the past, so unless it was a conflict of Windows Firewall and AVG both being active, dont think thats was the prob (but you would know better than i).

I have AVG on auto-update, and it is currently @ v10.0.1424.

 

[NoelDP]

Is this the paid version of AVG or the free one?
What other AV has ever been installed on this machine since the last format??

 

[o0erk0o]

I use the paid version of AVG.

Im pretty sure my rig came with Norton pre-installed (HP machine), but its been a while so cant say for sure. I do remember uninstalling whatever it was upon purchasing/installing AVG approx. 3 yrs ago.

 

[NoelDP]

The dregs of Norton and McAfee products can come back to haunt you - and are like poltergeists in the way they act!.

I suggest uninstalling AVG temporarily, and then running the Norton Removal Tool - you can then reinstall AVG
https://www-secure.symantec.com/nor...10133834EN&product=home&version=1&pvid=f-home
(It doesn't really matter which profuct you had, as they all use the same removal program)