CAPICOM KB931906 - Continuously queued for install.

[chiefsmt123]

I've read several posts on the internet for this issue and have yet to see a reason/solution for it. I have a workstation that WSUS continuously queues KB931906. Add/Remove
Programs list this update as being installed. Also, the WindowsUpdate.log
file indicates a successful install, followed shortly by a redetection of the
need to install the update. I can include the WindowsUpdate.log file for
reference if needed.

Any ideas? I don't believe malware is at the root of this.

 

[linney]

See if there is anything here.

This is the "classic" fix for all strange Windows Update problems.

Temporarily stop the automatic updates service.
Rename C:\windows\software distribution to C:\windows\software distribution-old
Rename C:\windows\windowsupdate.log to c:\windows\windowsupdate-old.log
restart the automatic updates service.


When Update... Won't

http://langa.com/newsletters/2004/2004-06-21.htm

319109 - Windows Update Site Lists Updates That You Already Installed

http://support.microsoft.com/default.aspx?scid=kb;en-us;319109&FR=1&PA=1&SD=HSCH

How to troubleshoot Windows Update, Microsoft Update, and Windows Server Update Services installation issues

http://support.microsoft.com/kb/906602/#appliesto

Windows Update Troubleshooter

http://v4.windowsupdate.microsoft.com/troubleshoot/

 

[chiefsmt123]

Very good. I've seen a variation of the first suggestion. I will give it a try. Thanks.

 

[linney]

Here's some more.

You cannot install some updates or programs

http://support.microsoft.com/kb/822798#appliesto

 

[chiefsmt123]

I located a second copy of the CAPICOM.DLL file on this computer. It looks like it was installed by the HP OfficeJet 6210 All-in-One software. This version of CAPICOM.DLL is 2.0.0.2, while the other version on this computer is 2.1.0.2 (which is the actual updated version). I'm thinking this second copy from HP is what is messing up the works.

 

[linney]

I wonder what would happen if you replaced the 2.0.0.2 with the 2.1.0.2 as a manual operation?

 

[chiefsmt123]

I had that very thought. Couldn't hurt. I'll give it a try and post the results.

 

[linney]

What is it they say about "famous last words"? Backup the old version first.

 

[chiefsmt123]

That didn't do it. I also tried the renaming of the %windir%\softwaredistribution and WindowsUPdate.log procedure. Still queues up. I even tried the following: msiexec.exe /fa capicom2.msi. Two things I've noticed. One, the following registry entry is missing HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CAPICOM.Certificates.4\CLSID
It is my understanding that this registry entry is made after a successful update. Also, the KB931906.log is missing from the C:\windows directory. So, even though Add/Remove programs has the update as being installed, it is failing somewhere.

 

[linney]

Have you got a copy of CAPICOM-KB931906-v2102.exe obtainable via Windows Catalog or Microsoft Download Center?

If you did you could first uninstall what's on your machine in Add or Remove, then manually install the downloaded .exe.

At the very least you should end up with a log to to look at.

http://www.microsoft.com/downloads/...18-4a66-4da6-a6c5-206df13af316&DisplayLang=en

http://test.catalog.update.microsoft.com/v7/site/

 

[chiefsmt123]

Thanks again. Earlier today we discussed removing the update using Add/Remove Programs, then boot into safe mode and try installing manually. When the user gets a moment, we will give that a whirl.