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?

Many, including me, got it. There is suppose to be an update by MS to fix it.

Thank you for your reply. Guess will just have to sit back and wait. Hope there faster than they usually are.

I was reluctant to give you this thread because it does not seem to work for most. I decided to, however, since the Media solution did indeed work for me.

https://www.sevenforums.com/crashes-d...e-install.html

Thanks, I'll work on it tomorrow and see what happens.

You said in the other link Go into the event viewer then locate the error and click on the link. and then install.
See if that helps, but I doubt it. Where would you install it to after you download it. When you click on it a box comes up and ask where to install it. That's my question, where do you install it?

About 3 weeks ago many, including me, started having this problem. It is probably caused by an update. Word is the MS will correct the problem with another update.

Re the CAPI2- 4107 errors in application event log.

This has been an ongoing nuisance for some Operating Systems for some time.
I too received this error when using Vista Ultimate 64-bit. [ on one laptop - the other identical laptop / OS was ok.]
Research provided many so called fixes, none of which worked.

Links below provided for you to peruse.

Windows 7 Ultimate getting tons of CAPI2- 4107 errors in application event log.

Getting a Load of Event 4107, CAPI2 in the Application Log

I was getting this on both PCs here, and looks like I resolved it. At least for now.

It seems to be related to WMP network so ..

I left the Homegroup on both PCs.
Re-created it and re-joined on both.

Then, in Network and sharing options in Control panel:
Chose troubleshoot problems, and Homegroup.

Ignored the test for network and let it continue with Home Network.
It applied fixes to the Home Network. (certificate refresh) and asked if fixed, I said yes.

Done this on both PCs and the error is gone.