Vista - Microsoft`s Silent Trusted Root Authority update is Invalid?

As far as I know there’s nothing to be worried of. I also had the event CAPI2 logged after every bootup in the past and, to have it stop showing up, I changed the Cryptographic Services Startup Type from default Automatic to Automatic (Delayed Start).

My computer is working well also.
Am I worried? No.
Confused as to why it is so? Yes.
Curious as to why it hasn't been dealt with? Very curious.

That describes the feeling exactly!

Vista reports a problem with time, so I looked on that side. After few trials, I was able to get rid of the CAPI2 event ID 11 errors and also able to get them back ! Here's the story :

- I first tried to set my Vista clock one year earlier (no change in BIOS): no success, CPI2 errors were there. System event viewer also reported that my time was not properly set.
- I tried to set the Bios date earlier ( Sept 16 2007 ) (Vista time properly set). No success CAPI2 errors were there.
- I tried to set both Bios and Vista clocks to Sept 16 2007 and ... no more CAPI2 errors.
- I set correct time in Bios and Vista and CAPI2 errors were back. It looks like both the Bios and Vista clock are involved in the check.

Additionnaly, I noticed a huge difference in boot time. As an example, time difference between the first and last boot information in Application Event Viewer is 2 min 29 sec. with CAPI2 errors and is .... 21 sec. without CAPI2 errors. No need to say I would prefer the second one, booting time is always too long !

Additionnally, during the trials, I noticed that Windows update was asking to check updates ... after checking updates, none was reported available even if I know one was waiting for couple of days. After correctly setting time, I could effectively see the waiting update.

So, Vista and Bios with earlier time solves the problem but it's just not possible the keep a PC with wrong time. Updates are also not possible.

Now, I'll wait experts thoughts and possible solutions, because it could really be fun to get rid of these errors and minimize boot time. Thanks

Jean

My error disappeared for good after the changes I did with with Media Player. Don't need it.

Windows Media player sharing options have no effects on my side.

Indeed system time has been suggested to be involved in this issue. I do not know if you have read the thread linked by me on the 27th of June above. It contains a lot of useful information. This is how to enable CAPI2 logging in the Event Viewer:

"Go to Applications and Services Logs\Microsoft\Windows\CAPI2\Operational in the event viewer. Right click and enable logging for this service. Then give the log about 10 minutes to log stuff. You should get some informational logs and then some errors. Open the error and click the details tab. Scroll down and it should at least tell you the process that is causing the error."

Thanks Submarine for the answer.

Yes I read the whole thread and Yes I enabled CAPI2 log to have more information. The 3 errors were all related to trust certificate, time validity, etc ... and all three were initiated by Avira's sched.exe. As I was reluctant to disable or change Avira, so I posted my message hoping we could find something else than removing Avira. Now I did some additional tests ...

I disabled sched.exe and as you can imagine errors disappeared. It was predictable, the call is coming from Avira. Between you and me, removing the "initiator" doesn't mean we found the real culprit !

I just hope that another Antivirus scheduler will work. We'll see.

Thanks again

Hmm, I remember I had some odd recurring error. It went away after I flashed my BIOS and immediately after restart installed some program. Cannot remember what it was, if it was SP1, or if it was a re-installation of McAfee. It was related to system time somehow.

Anyway, good luck!

I subscribe to the MS feed on this topic. The problem continues to be discussed, speculation on causes are many, the "techs" offer various "solutions" & yet the problem still remains.
[dmex started this thread on 26-12-08 ,a long time ago, & things still haven't changed.]
For anyone who wants to persue the topic further it has been suggested to use this link.
https://connect.microsoft.com/default.aspx