11 replies
by cg it
find out if the update actually gets installed by checking the list of installed programs add/remove programs.
If not, it's possible [but I don't think so] that antivirus software is dening script writing which would not allow the update to install.
A better way to apply patches, hotfixes,service packs over your network is SUS [Software Update Service] instead of the standard Microsoft Windows Update Service. That way you have complete control over what,where,and when updates get installed.
by cg it
Poster rated this answer.
by joseph moore
Yep, there is a problem with the update and this hotfix on Win2K. I have been dealing with this issue on another question forum site for over a week now. In fact, my own Win2K machines are suffering from this.
The other question thread, with all of the info, is here:
http://tinyurl.com/26aeo
Take a look at the full thread. You will see the Newsgroup posts I found from Microsoft technicians, talking about how Microsoft is working on this, that there is a problem with Update and this patch.
Now, earlier this morning, a person did post something that worked for him. I was going to try this tonight, and see if it worked, but I will not be able to see if it really works until Wednesday! I am taking a couple of vacation days, so I won't be able to test if this posted fix works until I get back to the office. So, I cannot verify if the fix (posted by OlivierBataille at 6:43AM this morning) works or not. But I am gonna try it later tonight (Friday night).
My fingers are crossed!
Anyway take a look at the thread, and you will know all that I know on this.
Good luck!
by joseph moore
Ok, just to add to this.
First off, thanks DR for the compliment! This one was really driving folks crazy! I just searched through
microsoft.public.windowsupdate
newsgroup, and there are currently 590 references to this one hotfix; I browsed through the first 100, and MOST were about the hotfix reinstalling itself every day, so a LOT of people have this problem!
As of last night (Jan 23) it looks like the fix that is being suggested works! I tested it myself on my test Win2K machine, that originally had the re-installing problem from Windows Update. But, last night, I got it to stop!
The thread that I posted in my answer above does include the fix.
It really is that the MDAC that comes with Win2K SP4 is NOT in the minimum compatible list for this hotfix! This hotfix is rated for MDAC 2.6 and higher. Apparently, a normal Win2K machine with SP4 does NOT meet this requirement! And when you read the Technet article on this hotfix, it does say for MDAC 2.6 and up.
So, the Technet article on this hotfix is correct; it just doesn't emphasize that unless you had upgraded MDAC previously, the hotfix isn't gonna apply correctly!
So, I put on MDAC 2.8 on my Win2K test machine, rebooted, then went to Windows Update site and had it scan. It said I needed the kb832483 still. Ok. I let it install it.
Reboot again.
Went back to Windows Update, did the scan, and NOTHING was needed! It successfully detected that my system HAD kb832483 and didn't need it again!
Yeah! Success!
Now, I will check this machine in a few days (I am on vacation until Wednesday) to make sure that the automatic Automatic Update service doesn't try and install the hotfix again, but I don't think it will. It looks like upgrading the MDAC, then putting this kb832483 hotfix on, takes care of this Win2K problem.
This one has been fun to work on!
Poster rated this answer.
by mark
Yes, I had the same issue. You can fix by upgrading MDAC. Here is a link for the download:
http://msdn.microsoft.com/nhp/Default.asp?contentid=28001860
4th item down on the list - MDAC 2.8 available for download.
Poster rated this answer.
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending