Windows 7 Ultimate getting tons of CAPI2- 4107 errors in application event log.

Anonymous
2010-07-13T21:54:36+00:00

Log Name:      Application

Source:        Microsoft-Windows-CAPI2

Date:          7/11/2010 11:57:04 AM

Event ID:      4107

Task Category: None

Level:         Error

Keywords:      Classic

User:          N/A

Computer:    

Description:

Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.

.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Microsoft-Windows-CAPI2" Guid="{5bbca4a8-b209-48dc-a8c7-b23d3e5216fb}" EventSourceName="Microsoft-Windows-CAPI2" />

    <EventID Qualifiers="0">4107</EventID>

    <Version>0</Version>

    <Level>2</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x8080000000000000</Keywords>

    <TimeCreated SystemTime="2010-07-11T16:57:04.513600000Z" />

    <EventRecordID>3251</EventRecordID>

    <Correlation />

    <Execution ProcessID="1156" ThreadID="1192" />

    <Channel>Application</Channel>

    <Computer>Kronos</Computer>

    <Security />

  </System>

  <EventData>

    <Data>http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab</Data>

    <Data>A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.

</Data>

  </EventData>

</Event>

I started getting this error on July 11th at 11:57am CST.  I was doing nothing at the time other than browsing.  My computer is properly time syncing.  It appears that Microsoft is issuing a certificate with bad info, since downloading the cert myself and viewing it says that the certificate is not valid for the requested usage.  There are literally over a thousand of these errors now piled up but there seems to be no end in sight.  I tripped across them doing a weekly check of the logs.  I am experiencing no performance degradation or BSODs.  I ran "sfc /scannow" as admin and it found no problems.

The certificate is issued by Microsoft and signed by Microsoft, off of Microsoft servers.

Other places mention that the windows media player media server can cause this but their only fix is to disable the service.  Not kosher.

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2010-08-24T21:07:48+00:00

Hi everyone,

For the people receiving the CAPI2 ID 11 “Failed extract of third-party rootlist…” generated in the application log:

·        Click the Pearl (Start) Orb on the Desktop

·        In the Search box typeCMD (do not hit enter)

·       Right-Click cmd.exe and selectRun as administrator

Once the Command Prompt window is open type the following command and press enter.

certutil -urlcache * delete

*Note* There is a space between * & delete

Once it has completed it should show the following:

CertUtil: -URLCache command completed successfully

If the expired certificate is cached in the system profile, then you will need to run it in the system context.

 To do this, download PsExec 

Select Open then Double click PsExec.exe

Select Extract and choose the location, (Take note of this location) make a new folder called PsTools and select Extract

Now Open the Command Prompt as the administrator and browse to the location of the PsTools folder.

So if you extracted to your Desktop the Command Prompt should look like this:

C:\Users&lt;username>\Desktop\PsTools

Type the following and hit enter:

psexec -i -s cmd.exe

A new Command Prompt window should open, from here type the following command again and hit enter:

certutil -urlcache * delete

If these steps do not work use the steps below to enable CAPI2 logging, please copy and paste the details of the error log in this thread.

Click 'Start' > Type Event in the search bar and select 'Event Viewer'

Expand 'Applications and Services Logs'

Expand 'Microsoft'

Expand 'Windows'

Expand 'CAPI2'

Select 'Operational'

On the far right pane > Click 'Enable Log'

Cody C

Microsoft Answers Support Engineer

Visit our Microsoft Answers Feedback Forum and let us know what you think.

Was this answer helpful?

2 people found this answer helpful.
0 comments
Answer accepted by question author
Anonymous
2010-09-03T22:32:48+00:00

FYI, compliments of SBS MVP Susan Bradley...

CAPI2 errors driving you crazy? - THE OFFICIAL BLOG OF THE SBS "DIVA"

http://msmvps.com/blogs/bradley/archive/2010/09/02/capi2-errors-driving-you-crazy.aspx

~Robear Dyer (PA Bear) ~ MS MVP (IE, Mail, Security, Windows & Update Services) since 2002 ~ Disclaimer: MS MVPs neither represent nor work for Microsoft

Was this answer helpful?

0 comments

52 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2010-07-31T01:39:02+00:00

    Someday?  I thought something like this is VERY important, so why is it going on so long??

    because of a number of reasons. many aren't explaining the issue properly to ms help lines.

    others are going to wrong departments, etc.

    ms has gotten like dell they will not pass on an issue form one dept to another.

    google this and you will see the exact same issue poped up with vista sp2 update....

    Samuel,

    just opening the cab file and reading the signature/certificate will show you this, at least it does on my cab from here

    http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab

    Was this answer helpful?

    0 comments
  2. Anonymous
    2010-07-30T21:38:22+00:00

    Someday?  I thought something like this is VERY important, so why is it going on so long??

    Was this answer helpful?

    0 comments
  3. Anonymous
    2010-07-28T06:46:10+00:00

    One of Microsoft's certs expired. This is the cause of the CAPI2 4107 errors.

    If you download the root certificate trust list from http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab, it contains authroot.stl. This is a PKCS#7 formatted file.

    I used OpenSSL to translate this file to ASCII format, and it shows this:

    Certificate:

        Data:

            Version: 3 (0x2)

            Serial Number:

                61:01:b0:75:00:01:00:00:00:0b

            Signature Algorithm: sha1WithRSAEncryption

            Issuer: C=US, ST=Washington, L=Redmond, O=Microsoft Corporation, CN=Micr

    osoft Certificate Trust List PCA

            Validity

                Not Before: Apr 11 06:09:39 2009 GMT

                Not After : Jul 11 06:19:39 2010 GMT

            Subject: C=US, ST=Washington, L=Redmond, O=Microsoft Corporation, OU=AOC

    , CN=Microsoft Certificate Trust List Publisher

    So the "Microsoft Certificate Trust List Publisher" cert expired on 7/11.

    Only Microsoft can fix this snafu. 

    Never underestimate your own stupidity.

    Was this answer helpful?

    0 comments