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

Anonymous
2009-06-02T10:11:30+00:00

Hi, I get this error in the last few weeks and I am not sure, whether I should do something about it. I went to TechNet, Event ID 11 Automatic Root Certificates Update Configuration, but I would need something simpler that I can follow. Confuseduser P.S. Exact error message is below: -

Log Name:      Application

Source:        Microsoft-Windows-CAPI2

Date:          27/05/2009 8:42:16 PM

Event ID:      11

Task Category: None

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      Helga-PC

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="49154">11</EventID>

    <Version>0</Version>

    <Level>2</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2009-05-27T10:42:16.000Z" />

    <EventRecordID>32381</EventRecordID>

    <Correlation />

    <Execution ProcessID="0" ThreadID="0" />

    <Channel>Application</Channel>

    <Computer>Helga-PC</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>

Windows for home | Other | Performance and system failures

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 No comments
Answer accepted by question author
Anonymous
2009-10-20T11:32:58+00:00

I don't see any reason the solution above would not work in Vista.  I see the same folder structure and registry entries on Vista. 

If you are not familiar with the registry, here is a very detailed instruction set on how to delete entries:  http://support.microsoft.com/kb/136393

Be sure to use the export option before deleting entries in order to back them up.

Was this answer helpful?

2 people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2010-02-26T21:34:07+00:00

This does help.

Now that you've pointed this out I've seen the same behaviour in the CAPI2 Event Viewer log file. My Windows 7 clients have been trying to access two URL's at the domain http://crl.microsoft.com/

None of the posts I had seen on this had mentioned the need for this path.

Thanks,

Michael

hi

Here's a basic definition for CRL in general terms. You can search Google using "Certificate Revocation List" and find a lot more information.

it could also be that direct X is looking for some updated drivers

what happens is that your browser is checking for provoked certificates , is perfectly normal and safe , its to keep you safe

have a nice day

ps for some further info

http://technet.microsoft.com/en-us/library/dd772269.aspx


Scan with OneCare + 50 Windows 7even Tips + Plagued by the Privacy Center? REMOVE IT + Threat Research & Response Blog + Sysinternals Live tools + TRANSLATOR+ Photosynth + Microsoft Security + Microsoft SUPPORT + PIVOT from Live Labs+ Microsoft Live Labs + Office 2010 beta + Get Windows LIVE!

Was this answer helpful?

0 comments No comments

138 additional answers

Sort by: Newest
  1. Anonymous
    2009-06-19T12:36:53+00:00

    Hi Rainer Meier,

    Thanks for using the Answers Forum.

    It looks like you might want to check your motherboard manufactuer for a firmware/BIOS update or patch.

    You may also want to investigate the CMOS battery to see if it needs replacing.

    Hope this helps.


    Chris

    Microsoft Answers Support Engineer

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

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2009-06-17T18:29:07+00:00

    So I went to the BIOS and changed the current time (well I assumed if I change any value it will force the BIOS setup to overwrite whatever value is currently stored within the RTC). I just increased the minutes by 1. Then I saved and exited the BIOS setup.

    Now I rebooted Vista twice and up to now I did not get the error again.

    Unfortunately I have to report that Event 11 on CAPI2 source returned on my laptop. I might have been cheated by the WLAN I was using at this location (requires login). As reported already the error is not logged immediately if no internet connection can be established. That's probably why it did not happen this afternoon. Now I returned home, booted the machine and here it is again... :-(

    I leave the original message untouched for reference, even if it seems it did not do any change.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2009-06-17T12:57:08+00:00

    I've read that several times on different forums but it did not help in my case. I am using a timeserver to synchronize time and my BIOS time is set correctly.

    Actually I found the hint with the system time the most promising to investigate further. I also thought to remember that I read something on the Internet that the cryptography services in Windows do not use the Windows clock/time but instead some weird direct hardware access (RTC?).

    Recently I noticed too, that the BIOS on my HP 8510w anyway behaved a bit oddly. The modem entry (to disable the built-in modem) was not showing up any more and the device was missing in the device manager. The solution was to load setup defaults, switch off the machine (remove battery) and then restart the machine.

    So I thought let's give it a try, probably the current clock is no properly written to the RTC on Windows shutdown.

    So I went to the BIOS and changed the current time (well I assumed if I change any value it will force the BIOS setup to overwrite whatever value is currently stored within the RTC). I just increased the minutes by 1. Then I saved and exited the BIOS setup.

    Now I rebooted Vista twice and up to now I did not get the error again.

    Probably this will help others too... let us know.

    Was this answer helpful?

    0 comments No comments