I have this error message in my eventviewer: 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. It freezes up the windows 7 PC whenever this occurs. Can someone help please, I am not experienced how to correct errors listed in eventviewer. Thanks!

Click the link that shows up in the error log (http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab ), download it and install it manually should fix this error. Best regards.

Click the link that shows up in the error log (http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab ), download it and install it manually should fix this error. It doesn't, since the invalid certificate is in that package. And this since July. Best greetings from Germany Olaf

I followed the advice of MS web site, it seemed to have fixed my problem on error 4107: http://support.microsoft.com/kb/2328240/en-us Thanks for everyone's help, I surely appreciated all the replies. Hello Olaf, :o) I love get conflicting replies. So please pray tell what did you do in this instance? Love to know.

Thanks for trying to help. Did this solution work for you?

For me I am able to download it now and I found a .stl file signed by a certificate delivered to Microsoft Certificate Trust List Publisher that expires 09/07/2011. Best regards.

Please would you care to explain exactly what you did? I am not familiar with EventViewer nor the error codes, nor how to find a non-valid certificate? Would appreciate :o)

I downloaded the .cab file from this link http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab. I found into the .cab file a list of trusted certificates. This list was signed by a certificate that is not valid for the required use. Best regards.

Thanks! However, I did d/l this yesterday, it looks to be the standard fix, however, in my eventlog TODAY I found the same CAPI2 error 4107.

It is strange that a such thing freeze your computer. Are you sure there is no other error IDs? Best regards.

only one application error with vipre 1000, which I hope I fixed but the CAPI2 error freezes the pc alright (wonderful lovely windows 7 64 bit) had more trouble with this barely 3 months pc :( Thanks for helping, nice to have support

My PCs do not "freeze", but I can confirm, that the signature shows as not valid for the required use in the downloaded file. (And it is not fixed, unfortunately.) I will see, if I can escalate the issue to Microsoft. Best greetings from Germany Olaf

open an elevated command prompt run certutil -urlcache * delete ---> press enter this will clear cache of the expired "Microsoft Certificate Trust List Publisher". Note: 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 and run the following command before running certutil: psexec -i -s cmd.exe latest KB http://support.microsoft.com/kb/2328240 been released

open an elevated command prompt run certutil -urlcache * delete ---> press enter this will clear cache of the expired "Microsoft Certificate Trust List Publisher". Note: 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 and run the following command before running certutil: psexec -i -s cmd.exe latest KB http://support.microsoft.com/kb/2328240 been released This may fix the issue for some but not for most: still getting CAPI2 4107 errors every hour or so that seem to be triggered by RAC Task as the times correspond.

So is there any word forthcoming from MS about this matter? I ask as my event log listed 4107 on the 27th (twice at the same timestamp) and then 31 seconds later the log lists 4108 denoting... Successful auto delete of third-party root certificate:: Subject: <CN=Entrust.net Certification Authority (2048), OU=(c) 1999 Entrust.net Limited, OU=www.entrust.net/CPS_2048 incorp. by ref. (limits liab.), O=Entrust.net> Sha1 thumbprint: <801D62D07B449D5C5C035C98EA61FA443C2A58FE>. But sort of oddly once more on the 29th, 4107 again lists and immediately thereafter my NAV2010 stopped running, restarted and seconds later again the application event log immediately lists event 4101 (Winlogon source, stating "Windows license validated."). Not sure what's going on, some issue with NAV2010, the validation process, or some matter involving MS's issuances of the authrootstl.cab file, ref. event ID 4107... 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. But again, on the 29th and the 30th I got that error and despite the 27th's entry stating 'Successful auto delete of third-party root certificate...', and yet still the 4107 event error again lists on the 29th and 30th (and neither subsequently state 'Successful auto delete of third-party root certificate...'. So any added looking into and/or resolution is appreciated for all concerned. My best to all and happ-e-trails, yourweldguru

I am still getting hourly CAPI2 4107 errors logged after executing kb2328240 fix suggestion just the same. RAC Task does seem to trigger this error.

I have now finally resolved the CAPI2 4107 issue with following method: Turn off UAC, restart machine and delete all files found in: C:\Windows\System32\config\systemprofile\AppData\LocalLow\Microsoft\CryptnetUrlCache\Content C:\Windows\System32\config\systemprofile\AppData\LocalLow\Microsoft\CryptnetUrlCache\MetaData C:\Windows\ServiceProfiles\LocalService\AppData\LocalLow\Microsoft\CryptnetUrlCache\MetaData C:\Windows\ServiceProfiles\LocalService\AppData\LocalLow\Microsoft\CryptnetUrlCache\Content C:\Windows\ServiceProfiles\NetworkService\AppData\LocalLow\Microsoft\CryptnetUrlCache\MetaData C:\Windows\ServiceProfiles\NetworkService\AppData\LocalLow\Microsoft\CryptnetUrlCache\Content C:\Users\*username*\AppData\LocalLow\Microsoft\CryptnetUrlCache\Content C:\Users\*username*\AppData\LocalLow\Microsoft\CryptnetUrlCache\Metadata Delete all keys under: HKEY_LOCAL_MACHINE\Software\Microsoft\SystemCertificates\AuthRoot\Certificates Turn back ON UAC, restart

Win7ine - Very interesting. I think for sure you're on to something, ref. UAC as I think my same errors seem to have appeared about the time I re-enabled UAC that and/or I also re-enabled (started using) system restore's utility. You seem to have had some inkling as to the cause, so maybe you realized corresponding dates of errors and your own enabling/disabling UAC? Ultimately, what led you to deriving your solutions needed file deletions? In my instance(s) of the 4107 errors, oddly after my last one (on 8-29-10), fortunately I'm finding (in the event log's Windows Logs>Application) 'info' loggings pertaining to CAP12's workings, ref. event ID 4097 (8-30-10, 9-3-10, 9-5-10 & 9-9-10, ie; probably my 're-boot' dates) with which CAP12 info is now detailing 'Successful auto update of third-party root certificate', ie; no more 4107's seen. So it seems my own CAP12 4107 issue resolved itself. Go figure.

Win7ine - Very interesting. I think for sure you're on to something, ref. UAC as I think my same errors seem to have appeared about the time I re-enabled UAC that and/or I also re-enabled (started using) system restore's utility. You seem to have had some inkling as to the cause, so maybe you realized corresponding dates of errors and your own enabling/disabling UAC? Ultimately, what led you to deriving your solutions needed file deletions? In my instance(s) of the 4107 errors, oddly after my last one (on 8-29-10), fortunately I'm finding (in the event log's Windows Logs>Application) 'info' loggings pertaining to CAP12's workings, ref. event ID 4097 (8-30-10, 9-3-10, 9-5-10 & 9-9-10), ie; probably my 're-boot' dates) with which CAP12 info is now detailing 'Successful auto update of third-party root certificate', ie; no more 4107's seen. So it seems my own CAP12 4107 issue resolved itself. Go figure.

1. First you need to get some detailed logging on what's failing, Click Start > Control Panel > Administrative tools > Event Viewer > Expand Applications and Services > Microsoft > Windows > CAPI2 > Right click "Operations" > Select "Enable Log" >Then reboot. 2. Return to the same place in Event Viewer > And open the errors listed there, as you can see "In My Case" the problem is McAfee, after I removed McAfee and installed the latest version (8.7i with patch 3 at time of writing), the error ceased.

1. First you need to get some detailed logging on what's failing, Click Start > Control Panel > Administrative tools > Event Viewer > Expand Applications and Services > Microsoft > Windows > CAPI2 > Right click "Operations" > Select "Enable Log" >Then reboot. 2. Return to the same place in Event Viewer > And open the errors listed there, as you can see "In My Case" the problem is McAfee, after I removed McAfee and installed the latest version (8.7i with patch 3 at time of writing), the error ceased. Thanks for the info, i did what wine say and yes no more errors(4107) in event log, but the freeze was still ther, with ur info i can see that was the fault of CAPI2 41 and 11 errors, so my question is, there is a way to get rid of this??? i dont rly wanna to make a fresh install. PS. The cache is empty, so i was thinking is there a way to stop downloading that certificate? I forget to tell, this happend a lot when im playing videos or listen music, but the event dont show problems with the software-hardware.