Home > Windows 7 > Windows 7 Event Id 4107

Windows 7 Event Id 4107

Contents

Surely the OS is supposed to handle this stuff?? I also started to get the message yesterday. A copy of the CTL with an expired signing certificate exists in the CryptnetUrlCache folder. http://social.answers.microsoft.com/Forums/en-US/w7repair/thread/8f6a032a-86c2-4f54-a0bb-9ea6e45384d2 the following was from a post in that thread by rjw40: If you enable CPI2 logging no errors are displayed in the Application Event Viewer. Source

i then wiped all drives and formatted for clean install of windows 7. The last time I saw any ID 4107 CAPI2 errors on the 64-bit machine was a rash of errors Dec. 9-10, 2011, after Windows Update installed 38 updates on Dec. 9, Wednesday, March 02, 2011 9:08 AM Reply | Quote 0 Sign in to vote I already tried the Microsoft Fix it tools, edited the registry and removed the CyrptnetUrlCache folders, whatever. so the MS idiots sent me a link to resend issue to a list of just about every MS program ever made and i am suppose to choose where to send

Microsoft-windows-capi2 Error 513

one would think with all this info it would be simple to fix issue and while i know my way around my computer this is above my pay grade but ican Eventually this should be corrected from Microsoft. i did turn on capi2 logging to try to make tracking this down easier (hence the info pasted below). Has anyone at Microsoft checked the new certificate chain is correct?

It's a Puget Systems built machine as i was an early i7 adopter hence having Vista 64 at first. Not interested in getting this event via email? Backup and delete the contents of the following folders: C:\Windows\System32\config\systemprofile\AppData\LocalLow\Microsoft\CryptnetUrlCache\Content C:\Windows\System32\config\systemprofile\AppData\LocalLow\Microsoft\CryptnetUrlCache\MetaData 2. Kb2328240 Since the cached CTL does not have a time valid signature, CAPI will retrieve the CTL from WU and obtain the valid CTL.

Update: This appears to have something to do with the Windows Search service i.e. Failed Extract Of Third-party Root List From Auto Update Cab At: Capi2 Not sure how that task relates to certificates but hopefully Microsoft will fix the certificate at some point soon and I'll re-enable the task. Saturday, July 17, 2010 12:45 AM Reply | Quote 0 Sign in to vote Chevysales - I found the information at the links provided. Do not run the May 2010 update - Letyour machine update on its own.

Coral Bay CC on July 12, 2010 at 7:23 am said: I concur. Capi2 4107 Error Windows 7 Seems like all 12 of them are reporting this error. The last CAPI2 entry was dated 7:09 pm tonight. See the article on how to clear the expired certificate from the cache.

Failed Extract Of Third-party Root List From Auto Update Cab At: Capi2

Pete on July 27, 2010 at 4:53 pm said: Its the ongoing quest to have clean/all green checks in the daily server reports. Seems to be a lot of inquiries but no answers. Microsoft-windows-capi2 Error 513 Source: http://support.microsoft.com/kb/2328240 Add link Text to display: Where should this link go? Microsoft Windows Capi2 4107 After restart, the 3 root certs referenced by http://support.microsoft.com/kb/293781/en-us were present.

Looks like the error started again (about every 12 hours). this contact form as i have not one listed RAC based error in log. Contact me 11Jul 2010 Failed extract of third-party root list from auto update cab admin I've been seeing this error on my SBS 2008 and another Win2k8 r2 box I have I didn't enable and check the CAPI2 log. A Required Certificate Is Not Within Its Validity Period Windows 10

To be honest, I still struggle with certificates, so I'm not sure exactly how, or why this worked, or for that matter if it will continue to work. 2.) Something a You can safely disable the RAC task or RAC agent (as it is called in Vista) in Task Scheduler. Wednesday, July 14, 2010 5:40 PM Reply | Quote 0 Sign in to vote In my case I didn't need to do anything on my win 7 64 bit PC except have a peek here HELP ME PLEASE - MAKE WIN7 WORK BETTER!

At approximately 7:09 pm on Monday, July 12th, the CAPI2 event errors stopped on my PC and have notreoccurred. Microsoft Certificate Trust List Publisher Certificate Now all windows update are from update.microsoft.com, so I took a look and found the following article on CNET.com from August of 2003: http://news.cnet.com/2100-1002_3-5064433.html Don't know if this still applies or Please see Search Help for suggestions.

and now again after last weeks up dates which were for me on w/7 malicous tool remover, outlook junk mail update and (in capi2 log i have read errors on OSA...which

one thing i did find is most users with the issue have the exact same info i posted above and looking at event viewer and capi2 log one can surmise that For your information, you can submit a Windows 7 service request from the following site: Windows 7 Support https://support.microsoft.com/oas/default.aspx?gprid=14019&" In other words - "it's not my job" type response! Now all windows update are from update.microsoft.com, so I took a look and found the following article on CNET.com from August of 2003: http://news.cnet.com/2100-1002_3-5064433.html Don't know if this still applies or Microsoft-windows-capi2 513 In our case the problem occurs onWindows 2008 R2 servers.

I'm getting it on my Windows 7 64-bit machine.Rod Tuesday, October 11, 2011 1:27 AM Reply | Quote 0 Sign in to vote Failed extract of third-party root list from auto the certificatr that signed the list is not valid" if a certificate is not valid then its not valid....nothing to do with peoples machines that simple Example: http://mariboe.net/signingcertnotvalid.png I'm ignoring this Wednesday, July 14, 2010 8:01 PM Reply | Quote 0 Sign in to vote i sent them the cab file, a link to this thread and the google results on this Check This Out Pete Matthew Konkol on July 12, 2010 at 6:49 am said: seeing this error on SBS2k3 boxes as well.

Proposed as answer by djanrd Tuesday, July 13, 2010 1:56 AM Marked as answer by Magon LiuModerator Tuesday, May 03, 2011 7:36 AM Monday, July 12, 2010 8:53 PM Reply | Wednesday, July 14, 2010 7:11 PM Reply | Quote 0 Sign in to vote Here is the link I used to the Windows Update support site: https://support.microsoft.com/oas/default.aspx?gprid=6527&st=1&wfxredirect=1 The free I'm getting the feeling MS just doesn't care whether their stuff works or not. Reboot your computer.

Update: Looks like Microsoft got it fixed. Running win 7 64 bit. You can help protect your system by installing this update from Microsoft.