CAPI2 Errors

mjf said:

Hopefully MS will take include the addition.

I got a reply from Microsoft today and as usual it was not specific as to weather or not they will add the additional CryptNetUrl files (LocalSystem: %windir%\SysWOW64\config\systemprofile\AppData\LocalLow\Microsoft\CryptnetUrlCache\Content %windir%\SysWOW64\config\systemprofile\AppData\LocalLow\Microsoft\CryptnetUrlCache\MetaData) to their Support Fix It site (Event ID 4107 or Event ID 11 is logged in the Application log in Windows and in Windows Server) which by deleting these files should fix the CAPI2 4107 error problem on 64 Bit machines. Ultimately I hope that this thread will be helpful to anyone that may encounter this kind of application error in the future.

I noticed a boatload of entries in the CAPI2 log recently (in my case it seems they're a result of Comodo Internet Security's cmdagent not finding security certs for a number of programs on my PC) and looked at two other W7 PCs I have and on both of those this log is Disabled (indeed one of the MS pages about CAPI2 seems to indicate it's disabled by default)!!?!

I trust both of these PCs as they are relatively new, and thus wonder how the CAPI2 log on this 3rd PC even got Enabled in the first place.

maxseven said:

I noticed a boatload of entries in the CAPI2 log recently (in my case it seems they're a result of Comodo Internet Security's cmdagent not finding security certs for a number of programs on my PC) and looked at two other W7 PCs I have and on both of those this log is Disabled (indeed one of the MS pages about CAPI2 seems to indicate it's disabled by default)!!?!

I trust both of these PCs as they are relatively new, and thus wonder how the CAPI2 log on this 3rd PC even got Enabled in the first place.

The CAPI2 Operational Log is disabled by default I believe because of the potential performance hit it causes when enabled. The cause of your errors is different than that which I had. Perhaps a reinstallation of CIS will correct your problem but I'm pretty much just guessing.

Mcd73165 said:

The CAPI2 Operational Log is disabled by default I believe because of the potential performance hit it causes when enabled.

If that is the case, I wonder then how it got enabled on my (and your, and others' PCs). It's so well buried that I can say with confidence that I never enabled it myself. This seems odd to me, unless there is a trigger of some sort (e.g. "if you get this error, windows automatically enables CAPI2 Operational logging"). I've not found a discussion about this anywhere.

maxseven said:

Mcd73165 said:

The CAPI2 Operational Log is disabled by default I believe because of the potential performance hit it causes when enabled.

If that is the case, I wonder then how it got enabled on my (and your, and others' PCs). It's so well buried that I can say with confidence that I never enabled it myself. This seems odd to me, unless there is a trigger of some sort (e.g. "if you get this error, windows automatically enables CAPI2 Operational logging&quot. I've not found a discussion about this anywhere.

Maxseven, in my case it was not enabled, I enabled it temporarily for test purposes, then disabled it when I was finished with my test. How it is getting enabled on its own beats the heck out of me. Good luck with this anomaly.

Mcd73165

The Cap 12 drama has been around for quite a few years. Many threads have been written about the issue.

Suffice to say I was first introduced to this nuisance on two brand new Laptops with Vista Ultimate 64-bit & prior to SP1. Tried all the fixes & nothing worked. The error still comes & goes with monotonous regularity.

Lo & behold on another new Laptop running Win 7 Ultimate 64-bit a Cap 12 Error presented for a time, disappeared.... & the same pattern repeats.

Curiousity seeks answers always but there comes a time when one notices the sky hasn't fallen in. Monitor what happens whilst moving on.

After clearing the 64bit C:\Windows\SysWOW64\config\systemprofile\AppData\LocalLow\Microsoft\CryptNetUrlCache caches, I also stopped receiving CAPI2 Event ID 4107 error messages when I disabled CAPI2 logging. Interestingly, if I now re-enable CAPI2 logging, then I still get the same errors that I had before clearing the additional caches:

Event ID 11 Build Chain and Event ID 41 Verify Revocation errors for consent.exe, lsass.exe, dwm.exe, and SeaPort.exe

This time, though, these errors don't seem to trigger the Event ID 4107, CAPI2 error in Administrative Event log when the CAPI2 log is disabled.

Perhaps, these errors are now somehow being resolved whereas previously they were left hanging. Since booting now takes up to two minutes, I'll be re-installing and updating the operating system anyway. It will be interesting to see what happens on a "clean" system.

@wunderteam regarding your booting woes, you should give a hard look at freeware "Startup Delayer". This util intends to delay startup of individual components, but as a HUGE imo side benefit, in its Running Tasks tab it shows from smss.exe-on every component loaded, and the time for each, showing you exactly where your startup delay is at (if the delay is post-"Starting Windows" anyway). Further, if you right-click on the running task, it will show also the modules it has loaded (dependencies). I've not found anything like it anywhere.

Wunderteam, I never enabled the CAPI2 log after my problem was resolved so I don't know if I got any Event ID 11 or Event ID 41 errors. In any case, I think it's safe to assume that your problem is resolved (at least I hope so).