This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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>
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.
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.
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!
Using this method revealed "wmpnetwk.exe" to cause the error to be logged. This process seems to provide the Windows Media Player Network Sharing Service. It was set to "Auatomatic (Delayed)" start on my machine. Stopping it and setting the start method to "Manual" made the CAPI2 error disappear until now. However I think this is rather a work-around than a solution. Disabling this service will most probably disable media sharing capabilities of WMP - so if you don't use/need it this might be an acceptable solution. But if you want to use media sharing, then this is probably not helpful at all. Moreover I have the feeling that WMP is not the only application which triggers the Certificate Trust List (CTL) update. So the error might re-appear. Apparently the CTL provided by Microsoft on their pages is broken (signed by wrong certificate) which causes the error to be logged by WMP. This might be related to some DRM-code too which requires certificates to verify licenses (another reason to avoid DRM-systems). So disabling the "Windows Media Player Netwrok Sharing Service" might help some people here to work around the problem.
I am getting this recurring on Winxp Pro SP3 too.
Event Type: Error
Event Source: crypt32
Event Category: None
Event ID: 8
Date: 03/07/2009
Time: 10:50:50 AM
User: N/A
Computer: XXX
Description:
Failed auto update retrieval of third-party root list sequence number from: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootseq.txt> with error: This network connection does not exist.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Hello,
we have at 4 different customers and at our own office with SBS2008-SP2 exactly the same problem since 27.05.2009. The certificate-trust-list (authroot.stl) show the same error like at the diskussion above (the certicate that sign this list is not correct). I search allready for the solution, but i am sure, that MS make something wrong. The rtc onboard the server are syncronized at ntp server here in germany and the timezone is correct. Hardware wasn´t changed. The MS-sites are included the trusted sites and are not running over any proxy, this mistake is known too... Deactivated the Trendmicro virusscanner at our office: no result. Only SBS and Trendmicro are running at the SBS2008, nothing more. No addons. All is functionaly (at moment) only this error is all time at the event-log.
Let´s look, if after one MS-update, or a new trust list with correct sign, next time the error are away ;)
