XP Updates - FAILED 1

[RBH]

It seemed that I was just getting too many automatic updates for Windows XP Home, so I checked things. I discovered that "823559: Security Update for Microsoft Windows" had attempted to install itself over 12 times and failed. But via the autoupdate route, there was never a message that the install had failed. And in my list of "uninstalls" in the WINNT folder, it does show there, but is in black, as opposed to all the other uninstalls, which are in blue.

I went to the MS update site, had it do a search, and it came up with this same patch, and I OK'd the install. This time I got an error mesage shortly after, stating that the install had failed.

It seems that this patch/fix is related to Access, which I don't have on my machine - so that could be a good reason why the fix couldn't be applied.

Can anyone give me some words of wisdom on this situation? It seems that MS may have some screwed up directions for this patch, and thinks I need it, but it doesn't seem that I can install it???

Ron Hirsch

 

[MSeng]

Does the update appear in a registry key mentioned in the Security Bulletin?

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP2\KB823559.

Also, does the file versions that are listed in the manifest match what you have installed?

Date Time Version Size File name Platform
-------------------------------------------------------------------------------------
27-Jun-2003 16:38 2003.1100.5426 311,864 Html32.cnv Windows XP x86
27-Jun-2003 16:38 2003.1100.5426 116,288 Msconv97.dll Windows XP x86

 

[RBH]

I checked the Registry, and it is not listed in there, confirming that the update in question was not installed.

I do not understand what you are asking in the material I've shown below, and copied from your message.

+++++++++++++++++++++++++++++++++++

Also, does the file versions that are listed in the manifest match what you have installed?

Date Time Version Size File name Platform
-------------------------------------------------------------------------------------
27-Jun-2003 16:38 2003.1100.5426 311,864 Html32.cnv Windows XP x86
27-Jun-2003 16:38 2003.1100.5426 116,288 Msconv97.dll Windows XP x86

Ron Hirsch

 

[MSeng]

Someone on another forum had the same issue with the update you refer to. When asked to verify the file date and version, he responded he had a newer copy of msconv97.dll, which was probably installed when he put in a later update (

http://support.microsoft.com/default.aspx?kbid=824938).

I'm wondering if you have the same problem.

Search your root drive (the drive you have the OS installed on) for the two files referenced and report back your results.

 

[RBH]

Thanks for the comeback.

Both of the above files are in the $NtUninstallKB823559$ subfolderfolder in the c:\WINNT folder. They're dated 8/18/2001.

Also, lately I've not been getting the live update message to run that update. Possibly live update now recognizes that the update in question is either not appropriate, or already done.

Ron Hirsch

 

[MSeng]

Anywhere else - not necessarily in that folder? msconv97.dll is usually located in \program files\microsoft shared\textconv.

Also, you said the $NtUninstallKB823559$ folder exists so WU did try to install (although it may have failed). Is there an uninstall executable (SPUNINST) in a folder of the same name and if so, can you uninstall it?

 

[bcastner]

Try this:

http://support.microsoft.com/?kbid=319585

 

[RBH]

Yes, the file is in 2 other places. The initial search was only in the WINNT folder. There are 2 other listings in the Program Files folder.

There's one in C:\Program Files\MicrosoftActiveSync - dated 11/9/2000

There's 1 more in c:\program files\microsoftshared\textconv

In the $NtUninstallKB823559$ folder, there is a subfolder named "spuninst" with a file named spuninst.exe. Should I attempt an uninstall here, or since the ongoing attempt of MS Update has not had any further attempts, should I let the sleeping dog lie?

Ron

 

[bcastner]

Use the spuninst.exe.

Then follow my earlier link to clean your catalogue database for updates. The easiest way is to rename or delete the catalogue database file. This problem can occur if the hotfix installer was referencing:
C:\WINDOWS\system32\CatRoot2\edb.log and the file was corrupt. Either renaming C:\WINDOWS\system32\CatRoot2\edb.log or renaming the entire C:\WINDOWS\system32\CatRoot2 folder will allow the hotfix install to complete
normally.

Be certain to do the recommended flush of temporary internet files as well.

 

[RBH]

Thanks again for all the info - I'll do all the necessary steps as you suggested.

Ron Hirsch