Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: CAPI2 Errors

21 Aug 2011   #31
Mcd73165

Windows 7 Home Premium 64 Bit
 
 

Quote   Quote: Originally Posted by Phone Man View Post
I have gone to the workaround by turning on the CAPI2 Operational log so the errors will not show up in the summary. You can control the size of that log and I can check every week or so and see if the problem is resolved. Out of site and out of mind.

Jim
That's certainly an option. Mark


My System SpecsSystem Spec
.
21 Aug 2011   #32
mjf

Windows 7x64 Home Premium SP1
 
 

These errors have frustrated others and MS took forever to provide a fix which doesn't appear to solve your problem.
This thread is not your solution but just example that your frustration has been shared.
CAPI2

McAfee has been accused in the past as being one cause.
After I installed SP1 I never had the CAPI2 reporting problem.
Maybe just ignore them. Event logs clearly have a purpose but if they get full of rubbish you can clear them
Event Viewer One Click Clear
My System SpecsSystem Spec
23 Aug 2011   #33
wunderteam

Windows 7 Home Premium 64-bit
 
 

I developed Event ID 4107: CAPI2 errors at the precisely same time as the initiator of this thread. These errors became much more frequently after I installed SP1, switched Antivirus programs from McAfee to BitDefender, and upgraded to IE9. The log of CAPI2 also identified the system program lsass.exe as having a security certificate issue as well as consent.exe (system program), dwm.exe (system program) and SeaPort.exe (Windows Live program):
lsass.exe, 80092014 The certificate is not in the revocation server's database & 800B0109 A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
consent.exe, 80092013 The revocation function was unable to check revocation because the revocation server was offline.
SeaPort.exe, 800B0101 A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.
dwm.exe, 80092013 The revocation function was unable to check revocation because the revocation server was offline.
The invalid certificate associated with authrootstl.cab when attempting to manually install from http://www.download.windowsupdate.co...c/trustedr/en/ is apparently a red herring:
As for the certificate status, it is marked as "invalid for this purpose" because the UI expects a different EKU rather than the one used by automatic root update. The CTL UI expects the signer to contain the Microsoft Trust List Signing EKU. However, the automatic root update mechanism uses a different EKU (Root List Signer) and as part of certificate chain validation, Windows checks for the presence of the Root List Signer EKU in the CTL signer chain. In this case, the chain is valid for the Root List Signer EKU. (see Event Log CAPI2 4107 and CAPI2 errors driving you crazy? - THE OFFICIAL BLOG OF THE SBS "DIVA").
Thus the Event ID 4107 error message “A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file” refers to problems identified above rather than the integrity of authrootstl.cab itself.

It is not clear how serious Event ID 4107: CAPI2 actually is. Perhaps this error is just a consequence of overly paranoid system “nanny-ware” or of Rube-Goldberg-type convoluted security measures. Since no resolution to this issue appears to be imminent, the nuclear option of reinstalling the entire system seems the only solution. This will (hopefully) also improve the greatly degraded boot performance that I have experienced after a year of Win 7 use. Full scans by McAfee, BitDefender, Malwarebytes and MS Safety Scanner have not revealed any signs of infection. Kudos to Mcd73165 for braving the MS chicane and sparing us some additional frustration.
My System SpecsSystem Spec
.

23 Aug 2011   #34
Mcd73165

Windows 7 Home Premium 64 Bit
 
 

Wunderteam, thank you very much for your input and kind words.
My System SpecsSystem Spec
23 Aug 2011   #35
Mcd73165

Windows 7 Home Premium 64 Bit
 
 

I hope I'm not being premature but I think I finally resolved this problem, at least for my case. This link, Event ID 4107 or Event ID 11 is logged in the Application log in Windows and in Windows Server does not include the CryptnetUrlCache for 64Bit systems which is located in C:\Windows\SysWOW64\config\systemprofile\AppData\LocalLow\Microsoft\CryptNetUrlCache\Content and C:\Windows\SysWOW64\config\systemprofile\AppData\LocalLow\Microsoft\CryptNetUrlCache\MetaData. After (once again for like the 5th time) following the procedure in the Microsoft fix link above and also deleting the CryptNetUrl cache in C:\ Windows SysWow64, I rebooted several times to confirm there were no more CAPI2 Errors. I'll post again after I definitely confirm this fix is valid after a day or so. I'll keep my fingers crossed! (I found this information about the Wow64 Cache while frantically searching for a fix. I don't want to take credit away from whoever originally figured this out. I can't seem to find the link again where I got this info from).
My System SpecsSystem Spec
23 Aug 2011   #36
mjf

Windows 7x64 Home Premium SP1
 
 

Quote   Quote: Originally Posted by Mcd73165 View Post
I hope I'm not being premature but I think I finally resolved this problem, at least for my case. This link, Event ID 4107 or Event ID 11 is logged in the Application log in Windows and in Windows Server does not include the CryptnetUrlCache for 64Bit systems which is located in C:\Windows\SysWOW64\config\systemprofile\AppData\LocalLow\Microsoft\CryptNetUrlCache\Content and C:\Windows\SysWOW64\config\systemprofile\AppData\LocalLow\Microsoft\CryptNetUrlCache\MetaData. After (once again for like the 5th time) following the procedure in the Microsoft fix link above and also deleting the CryptNetUrl cache in C:\ Windows SysWow64, I rebooted several times to confirm there were no more CAPI2 Errors. I'll post again after I definitely confirm this fix is valid after a day or so. I'll keep my fingers crossed! (I found this information about the Wow64 Cache while frantically searching for a fix. I don't want to take credit away from whoever originally figured this out. I can't seem to find the link again where I got this info from).
It did for someone else
CAPI2

Meaning of a black hole: Send a suggestion to MS to improve something.
My System SpecsSystem Spec
23 Aug 2011   #37
Phone Man

Windows 8.1 Pro w/Media Center 64bit, Windows 7 HP 64bit
 
 

Quote   Quote: Originally Posted by mjf View Post
Quote   Quote: Originally Posted by Mcd73165 View Post
I hope I'm not being premature but I think I finally resolved this problem, at least for my case. This link, Event ID 4107 or Event ID 11 is logged in the Application log in Windows and in Windows Server does not include the CryptnetUrlCache for 64Bit systems which is located in C:\Windows\SysWOW64\config\systemprofile\AppData\LocalLow\Microsoft\CryptNetUrlCache\Content and C:\Windows\SysWOW64\config\systemprofile\AppData\LocalLow\Microsoft\CryptNetUrlCache\MetaData. After (once again for like the 5th time) following the procedure in the Microsoft fix link above and also deleting the CryptNetUrl cache in C:\ Windows SysWow64, I rebooted several times to confirm there were no more CAPI2 Errors. I'll post again after I definitely confirm this fix is valid after a day or so. I'll keep my fingers crossed! (I found this information about the Wow64 Cache while frantically searching for a fix. I don't want to take credit away from whoever originally figured this out. I can't seem to find the link again where I got this info from).
It did for someone else
CAPI2

Meaning of a black hole: Send a suggestion to MS to improve something.
I am getting to old for this. I remember that fix and for some reason I thought it was included in the MS FixIt but I was wrong. It worked last time and it worked again this time. I have now saved the FixIt file and a text file with the missing cache location. Maybe next time (and there will be a next time) I will get it fixed the first time.

Jim
My System SpecsSystem Spec
24 Aug 2011   #38
Mcd73165

Windows 7 Home Premium 64 Bit
 
 

MJF, it was the CAPI2 link that you provided that led me to the solution. Apparently, some of you already went through this mess back in 2010. So far there have been no more CAPI2 errors on my machine. This whole thing then with the invalid trust list certificates which I thought were the sole cause of my problem was then related to some bad entry in the SysWOW64 CryptNetUrlCache. This is a bit above my level of understanding.
My System SpecsSystem Spec
24 Aug 2011   #39
Mcd73165

Windows 7 Home Premium 64 Bit
 
 

I e-mailed Microsoft Support (for whatever it's worth) telling them that they should update their Fix It link Event ID 4107 or Event ID 11 is logged in the Application log in Windows and in Windows Server to include Windows\SysWOW64 CryptNetUrl entries for 64 Bit systems. This will save a lot of people a lot of aggravation if this CAPI2 4107 error problem is ever encountered. Thanks to everyone that provided input to this thread.
My System SpecsSystem Spec
24 Aug 2011   #40
mjf

Windows 7x64 Home Premium SP1
 
 

Hopefully MS will take include the addition.
My System SpecsSystem Spec
Reply

 CAPI2 Errors




Thread Tools




Similar help and support threads
Thread Forum
CAPI2 errors in Event Viewer
I'm getting hundreds of these every day showing in Event Viewer: Log Name: Application Source: Microsoft-Windows-CAPI2 Date: 12/24/2010 7:52:14 PM Event ID: 4107 Task Category: None Level: Error Keywords: Classic User: N/A
BSOD Help and Support
CAPI2
I noticed since the last windows update I'm getting a lot of CAPI2 Event 4107 in my application log in the event viewer. Anyone else getting this?
Windows Updates & Activation
CAPI2 Error, then system crashes
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...
BSOD Help and Support
CAPI2 error
Hi people I keep getting the following error in event viewer. It only started a couple of days ago. The seems to be a cab file to download but i dont know where to save it to.Any ideas what this means or where to save the file Thankyou
BSOD Help and Support
Event ID 1407 CAPI2 Help please
I'm now getting 50 of these errors on bootup: Log Name: Application Source: Microsoft-Windows-CAPI2 Date: 11/07/2010 15:10:13 Event ID: 4107 Task Category: None Level: Error Keywords: Classic User: N/A
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 21:59.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App