Microsoft-Windows CAPI2 failed extract of third-party root list from auto update cab

Martin, more info:  As mentioned, when doing a 'clean boot' using msconfig.exe, I noticed afterwards that ZoneAlarm (from Zonelabs) had still installed itself at boot but all other non-Microsoft items had not.

Today I tried setting ZoneAlarm to NOT install at start-up, using its own configuration options.  When I restarted the system (normal mode), the start-up was much faster and there was only about 1 second between the Welcome screen and the rendering of my desktop.  Nice!  However, the CAPI2 error was still in the event log.

I restarted again and it was again very fast.

I re-set ZoneAlarm to load at start-up and restarted and it behaved as reported previously -- a long display of the Welcome message, followed by a few seconds of empty blue screen, then the rendering of the desktop.

I conclude ZoneAlarm is a factor in the delay (once apparently indefinite) and 'blue screen'.  Maybe it's waiting for internet connectivity during its startup.

I presume Microsoft coordinates problem-solving within its 'ecosystem' since many end-users probably judge PCs by the overall experience.  (I'd dump ZoneAlarm but I like knowing what wants to go out, and, AFAIK, the Vista firewall doesn't provide that.)

Hey Alex

take a look at this forum thread:

http://www.vistax64.com/vista-installation-setup/113153-vista-error-updating-kb942763-code-80070643-a.html

It is the Daylight Saving Time update, Open Windows Update, rt click on

it, and Hide it. Same goes for Office SP1. They wont trouble you again.

You can manually download the update/fix from 'here'

(http://tinyurl.com/ypfrqf).

For some Vista updates troubleshooting tips, click 'here'

(http://www.winvistaclub.com/t4.html).

Today was a good day, I didn't have to use my AK.

04 June, 2009

Hello Everyone,

I too started experiencing CAPI2 11 errors on 27May2009 - the day Windows Vista SP2 appeared on my Windows Update list.  At that time however, I only set Windows Update to 'hide' Vista SP2 for the meantime to allow it time to go through the usual debugging process for newly issued software. 

But after noticing the CAPI2 11 errors a few days later, I decided to install Vista SP2 immediately to see if the CAPI2 11 errors will go away.  So now with deep foreboding I am using Vista SP2 and the CAPI2 11 errors still haven't gone away.

What I noticed though is that:

(a) The CAPI2 11 errors occur only during pc start-up and only when my internet connection is enabled prior to pc start-up - my usual pradtice ever since;

(b) I have tried disabling my internet connection is disabled prior to start-up - by disabling the on-board LAN prior to shutdown - and discovered that no CAPI2 11 error occurs during the next pc start up.

Aside from Windows Vista, the only other software I have that has automatic update enabled is Norton 360 v2.  By experimentation, I have determined that the CAPI2 11 errors still occur during pc start up when the on-board LAN is enabled, whether N360 v2 automatic update is enabled or disabled.

To Martin:  I do not think the problem is Vista SP2.  I think it was Windows Update on 27May2009 - all CAPI2 11 errors started occuring on that date!  The last time something like this happened to me with automatic Windows Update, I lost access to my Security Center.  Back then, I was also directed to run SFC and to check my start-up programs one by one - to no avail.  I have forgotten the prescribed solution for that problem, but it I think it involved fixing a corrupted configuration file(?) that could not be detected by SFC.

Alex_PH