Problems with windows update after reinstalling win 2k pro

Hi,

I recently had to reformat my hard drive and reinstall windows 2000 pro (sp4) due to the OS crashing and I was unable to make windows reboot again properly. And in my previous installation, I didn't have these issues but this is what's happening:

When I went to the windows update website to reinstall the security updates, etc, from the first get go, the updates downloaded but gave me a "failed to install" error. There was no number code associated with the error so checking the windows update troubleshooter didn't help. It just tells me that " A problem on your computer is preventing updates from being downloaded or installed ".

But some later time that day, I was looking in my add/remove programs for something, and saw all the security updates I had previously tried to install on the list. I checked my update history on windows update, and it told me these updates were indeed installed, and the source they were installed with was "automatic update ". The thing is, unless this was done while I was asleep, I don't remember seeing the auto update icon appear in my taskbar.

There are currently more updates I need to install and I'm still getting the failed to install error. Also, the "restore hidden updates" link on windows update is blanked out (the only way to descibe it, is it's showing as a disabled link).

The second strange problem I'm having that I also didn't have in my previous installation, is I had "system mechanic 8" installed, but since it of course was wiped out after my formatting, I had to reinstall it, so when I tried to do this now, it starts up, checks for updates, and then the setup shuts down with no reason why given. No error or anything.

So far this seems to be the only piece of software this is happening with, I've successfully installed other software after this.

I did a complete scan of my computer for viruses/adware/malware with "Avast! home edition ", and nothing was found.

I also disabled the virus software, and the updates still failed.

I don't know if this could be a registry problem, an unforeseen configuration problem with the OS install, or what. So any help and suggestions anyone can give me here will be appreciated.

Thanks.

 

No dice

Thanks for the suggestion Arie, but unfortunately it didn't work. I even tried it twice and even rebooted afterwards, and no luck. One thing though, when I tried it the first time, all the dll's registered successfully except: wuaueng1.dll

I got an error message, so it seemed to me that file was probably missing, so I downloaded a copy of it from the web, put it in my system32 folder and it registered successfully, but again, it still didn't solve the issue.

I'm wondering if there could be other related dll's that maybe didn't install or register with my reinstallation? Any idea?

 

Hi again Arie,

I checked event viewer, and yes, there are quite a few errors and warnings. Especially in the application log.

The system log has quite a few as well but not as many as the application log.

I'm not familiar with how event viewer works so a lot of the listings in the source area seem confusing. There's a few errors in here that say the source is "SAM "


Is there a particular error source I should be looking for that would be related to my problem with windows update?

 

Thanks

Oh well. Thanks for trying to help anyway Arie. I really appreciate it.

Fortunately though, this Friday I'll be getting another computer anyway. This one will have windows xp on it, and will be much faster as well. I'm going to keep this computer, so what I'll do is wait till I get the new one, and transfer what I can from this one to the new one and then try another reformat.

Just one other question if you don't mind answering Arie...Do you have any idea what could've happened? Did something not load in correctly with the install of 2k?

If so, why didn't I get some sort of error message during the installation? I love using computers, but this is the one thing that drives me crazy, how they do this strange stuff that just makes no sense at all, and you go crazy trying to figure out what's causing it.

 

It most likely was a dirty CMOS battery contact from acid corrosion unseen.

I reinstalled Windows 2000 about seven times recently but the last three times on a new WD hard drive. I almost bought a new motherboard after I had already bought the WD hard drive. It turned out to most likely be the CMOS battery as it not only went down to 2.6 volts (with no surge) but it spilled a little acid on the connection and it was basically static like or on/off real quick with a dirty connection. I even had to take out the new battery to clean real good as I finally got the two indications of "bad CMOS battery" on the first start up screen with the new battery. It only happened like one time before like when it was dead for a month while I used another. I have not yet checked the old Maxtor drive to see if it really was that. I don't think it was because I had to reinstall the new WD three times with MS and after a few drivers installed. Next thing I know I should have installed the WD disk ASAP to configure to ATA and not SATA. That had caused a crash or two too after the battery discover, man. I now run FARCRY at the highest settings possible and it runs strong. I have expensive liquid contact cleaner for electronics (the battery contact) and used a paper towel to scrub a bit maybe even scratch it with a tool. Was able to use the ultimate boot disk for nothing but acknowledge that the files were still there and I did use AVG from it. Before that it was like the Sasser Worm having the LSASS.exe problem. The ntkrlmp.exe problem will always be because MS does not want you to have a boot disk to which you can command from DOS as BestBuy has an agreement not to sell bootdisks. Basically they are like thier own OS right on DOS to which the HD then is a slave drive. That just about sums up the last 6 weeks.

 

addendum

The internet suggests that per the LSASS problem solution is to replace about five files including the SAM file. So it seems coincidental. I had replaced those files and too did not resolve it. (I really think it was the dirty CMOS battery connection and not a worm or the old HD).

 

addendum 2

Still it could be your HD. But if it formats without problems that may signal its good. Run "chkdsk /f" and it will check all your sectors on your disk to see if there's corruption. But still it could say there is corruption with the battery contact problem. Also, Errorsmart found 3548 problems with the new HD and the messed up contact.

 

Update your Java before visiting Windows/Microsoft Updates page.

 

Problem finally solved!!

Thanks for the suggestion Whiskeyman, but it seems that wasn't the problem.

I first looked in my windows update log text file and found the error number that was causing the installation failures. I did a google search using this error number, and came across this site:

http://kbalertz.com/910341/Error-me...Windows-Update-Microsoft-Update.aspx#Feedback


I followed his tips for windows 2000 and found a couple of things not set up.. after I finished, I rebooted, and the next thing I knew, my little automatic update globe icon popped in my task bar telling me "your computer has recently been updated" (it was like reuniting with a long lost friend )

I clicked it and as of this writing, the updates successfully installed. So I now need to reboot my computer to finish the installations.

Thank you all tremendiously for your help and suggestions! I hope the link to this I put here for this person's site will be able to help others on this board that may experience this problem.