Repeated notifications for same updates

[Millie]

Hello,

I have a Windows 2000 Professional SP4 computer. I keep
getting notifications, every 3-4 days, that the same six
updates are ready to be installed. I click install now
and receive the installations completed successfully
message.

They are: kb842526, kb840315, kb841873, kb841872,
kb839643, kb839645.

I posted a message about this a couple of months ago (but
my search returned no results so I couldn't continue on
the same thread). I was told to manually remove the six
updates and to manually download the six updates.
Unfortunately the six updates in question are not listed
in Add/Remove Programs.

I can't automatically update and I can't manually remove
the updates. Does anyone know how I can fix this problem?

Thank you,
Millie

 

[Guest]

I had a similar problem, and my solution ended up being a
reinstall of the program related to the updates (in my
case IE 6). Obviously, since none of your updates have to
do with IE, perhaps you should try a re-install of a
recently installed program, or perhaps SP4.

Just my 2 cents

 

[Guest]

1. From the command prompt, I typed: sfc /v scannow
2. When prompted, I inserted my Windows 2000 Professional CD
3. Basically it rolled my computer back to SP3.
4. I applied Windows 2000 Professional SP4.
5. I did Start... Windows Updates... scanned and installed
the same updates again.
6. The installation failed for all updates.

I am so frustrated by this. Any suggestions on what I should try next?

Thanks,
Millie

 

[Sky King]

1. From the command prompt, I typed: sfc /v scannow
2. When prompted, I inserted my Windows 2000 Professional CD
3. Basically it rolled my computer back to SP3.
4. I applied Windows 2000 Professional SP4.
5. I did Start... Windows Updates... scanned and installed
the same updates again.
6. The installation failed for all updates.

Hi, Millie;

Open the C:\Windows\Windows Update.log file; scroll down to the bottom to
get the most recent entries and look for error messages related to the most
recent update that failed. You will see something akin to "error
0x12345678" and a short description of the error. Please post back with
that error number and message.

Also check your C:\Windows folder for subfolders named
"$NtUninstallKB123456$" and see if any of those numbers match the ones you
have had problems installing (kb842526, kb840315, kb841873, kb841872,
kb839643, kb839645).

--

....Sky

Tom "Sky" King
=============

 

[Guest]

I am *relieved* to report to everyone that the problem has finally been
resolved. Microsoft Technical Support found the problem was caused by a
missing permission in the default group policy on my domain controller.

On the domain controller:

I didn't take notes for this part, so I don't have all the detailed steps.
(Maybe someone can fill in the blanks.) I had to open a new group policy
window, click on something, and remove a check mark from a box located in
the top left corner of a particular screen. Apparently removing the check
mark is critical in order for the workstation steps below to work.

1. Click on Start... Run... MMC.
2. ???

On the Windows 2000 computers:

*** Make sure the login ID used to login to the computer and to do the
windows update is a member of the computer's local administrators group. ***

1. Start... Run... SECPOL.MSC.
2. In the left pane, right click on the domain name.
3. Click Properties.
4. Click Local Policies... Local Users and Groups.
5. In the right pane, scroll down to "Take Ownership".
6. The Local Settings and Effective Settings columns
should both have the Local Administrators group listed.
7. If not, double-click "Take Ownership" and add the
Local Administrators group. (Only the Local Settings
box will be checked at this point.)
8. Exit Sec Pol.
9. Go back into Sec Pol. The Effective Settings box should
now be checked.
10. Exit Sec Pol.
11. Click Start... Windows Update. Scan for critical
updates. Downloaded and installed all found.
12. Restarted the computer.
13. Click Start... Windows Update. Scan for critical
updates showed there were none found! (Yeah!!!)

Millie

 

[Sky King]

I am *relieved* to report to everyone that the problem has finally
been resolved. Microsoft Technical Support found the problem was
caused by a missing permission in the default group policy on my
domain controller.

Perhaps if you had told us in the first place that you were working behind a
domain controller your issue could have been resolved much earlier here.

Playing "I've got a secret" when posting about problems here is NEVER a good
idea.

--

....Sky

Tom "Sky" King
=============

 

[Guest]

I am not a technically strong hardware/software person (I know a little bit
about some stuff and nothing about a lot of stuff) and was not deliberately
withholding information. I thought I had provided all necessary information.
It never occurred to me or to Microsoft Technical Support that it was a
domain controller related problem.

I had to speak to the setup team, the directory services team, the security
team, and the windows update team to resolve the problem. They had me
download and install the critical updates using the automated update icon,
using Start... Windows Update, using the Internet Explorer to go to their
website, applying one critical update at a time, etc. Then they said my
hardware wasn't on their approved hardware list and said they couldn't
support me. Then they wanted me to do an inplace repair of the operating
system.

The cause of the problem was *only* discovered when Microsoft asked me to
send them some logs (that I didn't even know existed) from my desktop
computer and from the domain controller. Also, no one (not the MVPs and more
experienced posters) in this forum asked me if I was working behind a domain
controller.

I appreciate the generous sharing of information in this forum and hope that
my posting of the resolution will help someone else down the road someday.

Millie