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

Anonymous

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:

<Channel>Application</Channel>

<Computer>Helga-PC</Computer>

</System>

<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.

0 comments

Answer accepted by question author

Anonymous

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.

0 comments

Answer accepted by question author

Anonymous

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

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!

0 comments

138 additional answers

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more
Anonymous

2009-06-03T16:24:05+00:00
Hi

Try adding windows updates to your trusted sites, then run the commands given bellow.

To make this site a trusted website:
1. In Internet Explorer, click Tools, and then click Internet Options.
2. On the Security tab, click the Trusted Sites icon.
3. Click Sites and under Add this website to the zone, copy and paste these website addresses.
You can only add one address at a time and you must click Add after each one: - http://*.update.microsoft.com - https://*.update.microsoft.com - http://download.windowsupdate.com

"Copy & paste following into command prompt ..hope this helps.

"ipconfig /flushdns

Cd %windir%

del /s *.chk;*.rip;*.tmp;~*.*

msiexec /regserver

sc config msiserver start= auto

net stop msiserver

msiexec /unreg

msiexec /regserver

regsvr32 msi.dll /s

regsvr32 msihnd.dll /s

net start msiserver

Regsvr32 wuaueng.dll /s

net stop wuauserv

cd /d %windir%

rmdir /s /q softwaredistribution

net start wuauserv

sc config eventlog start= auto obj= Localsystem

net start eventlog

regsvr32 qmgr.dll /s

regsvr32 qmgrprxy.dll /s

sc sdset bits D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)

regsvr32 wuaueng.dll /s

sc sdset wuauserv D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)

sc config wuauserv start= auto obj= Localsystem

net stop wuauserv

sc config bits start= DEMAND obj= Localsystem

net stop bits

regsvr32 msxml.dll /s

regsvr32 msxml2.dll /s

regsvr32 msxml3.dll /s

regsvr32 msxml4.dll /s

regsvr32 qmgr.dll /s

regsvr32 qmgrprxy.dll /s

regsvr32 muweb.dll /s

regsvr32 winhttp.dll /s

regsvr32 wuapi.dll /s

regsvr32 wuaueng.dll /s

regsvr32 wuaueng1.dll /s

regsvr32 wucltui.dll /s

regsvr32 wups.dll /s

regsvr32 wups2.dll /s

regsvr32 wuweb.dll /s

net start wuauserv

net start bits

sc config cryptsvc start= auto

net stop cryptsvc

cd %windir%\system32\catroot2

del *.* /f/q/s

regsvr32 cryptdlg.dll /s

regsvr32 cryptui.dll /s

regsvr32 dssenh.dll /s

regsvr32 gpkcsp.dll /s

regsvr32 initpki.dll /s

regsvr32 mssip32.dll /s

regsvr32 sccbase.dll /s

regsvr32 softpub.dll /s

regsvr32 slbcsp.dll /s

regsvr32 rsaenh.dll /s

regsvr32 winhttp.dll /s

regsvr32 wintrust.dll /s

net start cryptsvc

cd\

sc config ose start= demand

net start ose

regsvr32 qmgr.dll /s

regsvr32 qmgrprxy.dll /s

regsvr32 es.dll /s

cls

Rem **************End of the process*****************

pause

exit
Martin

Microsoft Answers Support Engineer

Visit ourMicrosoft Answers Feedback Forumand let us know what you think
Was this answer helpful?

0 comments No comments
Anonymous

2009-06-03T18:11:08+00:00

That's pretty scary.

How certain are you that that list of commands will fix the problem?

I'm worried that if I run that long list of commands, my system might end up in a non-standard state from which Microsoft will not be able to update it, or get it back (without a re-install, etc).

I think I've got a standard installation (standard Dell hardware, standard Vista), so I would think that if SP2 has a bug, Microsoft would address it by something other than a cut-and-paste -- what about all the people who don't know how to do cut-and-paste, etc? I'd prefer to wait until Microsoft has definitely found the problem and issued a tested fix -- something more formal than a cut-and-paste.

Will there be something formal? Maybe via Update?

If the problem is thought to be unique to me and the other poster, why is that? What is the problem?

If there is information I can provide from my system to help confirm the problem, that'd be great, I'd be happy to provide it.
Was this answer helpful?

0 comments No comments