CAPI2

[mjf]

I didn't get any updates, so no magic for me.

 

[Teerex]

Sorry to hear that. Considering the change in my situation, the root cause of this is even more misterious.

Keep looking, that date wasn't in that certificate for nothing.

 

[mjf]

Teerex
Have you received an update confirming your earlier message/screenshot?

 

[Teerex]

No. I reinstalled cleanly 10 days ago, and it seems that the offending certificate is not even present on the system. I'll check on another, older Win 7 installation this weekend.

 

[Sinclair]

I also have been inundated with this error since early July and despite my pc performance was not affected at all I didn't give up into trying to find the culprit and today, after leaving the Homegroup, it no longer shows up in the Application log.

What a relief.

I hope this post of mine may help someone.

 

[JMH]

This is the updated information from Microsoft Support.

Article ID: 2328240 - Last Review: September 20, 2010 - Revision: 2.0

Event ID 4107 or Event ID 11 is logged in the Application log in Windows Vista, in Windows Server 2008, and in later versions of Windows and of Windows Server

On a computer that is running Windows 7 or Windows Server 2008 R2, an error that resembles the following is logged in the Application log: Log Name: Application
Source: Microsoft-Windows-CAPI2
Date: Date and time
Event ID: 4107
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Computer name
Description:
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 (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 the timestamp in the signed file.

Read further -
Event ID 4107 or Event ID 11 is logged in the Application log in Windows Vista, in Windows Server 2008, and in later versions of Windows and of Windows Server

 

[youravinalarrrf]

You would have thought they would have included the following in their instructions for 64 bit users:-

LocalSystem:
%windir%\SysWOW64\config\systemprofile\AppData\LocalLow\Microsoft\CryptnetUrlCache\Content
%windir%\SysWOW64\config\systemprofile\AppData\LocalLow\Microsoft\CryptnetUrlCache\MetaData

Problem is now finally resolved and no more errors showing in Event Viewer!

 

[Phone Man]

I cleared all of mine including the sysWOW64 area last night so we shall see what happens.

Jim

 

[Joan Archer]

I've just seen the article but don't have time at present to do anything about it but will soon. Like others have said it doesn't cause any problems in the running but I was curious about it.
We shall see

 

[Phone Man]

I cleared all of mine including the sysWOW64 area last night so we shall see what happens.

Jim

So far no more CAPI2 errors and everything seems normal.

Jim

 

[mjf]

I got around to doing the changes so we'll see.
Except in Network Services:
my
\serviceprofiles\networkservice\appdata\LocalLow
directory doesn't exist.

 

[Flavius]

I got around to doing the changes so we'll see.
Except in Network Services:
my
\serviceprofiles\networkservice\appdata\LocalLow
directory doesn't exist.

First check in Control Panel>>Folder options you have checked "Show hidden files and folders" or better way use any good file manager which can see everything independly from system settings e.g Total Commander

 

[mjf]

I got around to doing the changes so we'll see.
Except in Network Services:
my
\serviceprofiles\networkservice\appdata\LocalLow
directory doesn't exist.

First check in Control Panel>>Folder options you have checked "Show hidden files and folders" or better way use any good file manager which can see everything independly from system settings e.g Total Commander

Direcory doesn't exist

 

[Flavius]

Direcory doesn't exist

So in this case you have to create below folders manually

C:\Windows\ServiceProfiles\NetworkService\AppData\LocalLow
C:\Windows\ServiceProfiles\NetworkService\AppData\LocalLow\Microsoft
C:\Windows\ServiceProfiles\NetworkService\AppData\LocalLow\Microsoft\CryptnetUrlCache
C:\Windows\ServiceProfiles\NetworkService\AppData\LocalLow\Microsoft\CryptnetUrlCache\Content
C:\Windows\ServiceProfiles\NetworkService\AppData\LocalLow\Microsoft\CryptnetUrlCache\MetaData

 

[mjf]

They exist under \LocalService but I doubt they ever existed under \NetworkService on my (64 bit) system.
I'm in the dark here so a couple of questions:
(1) What function do the sub directories perform (under NetworkServices)?
(2) Should they always be present?

thanks.

 

[Flavius]

(2) Should they always be present?

I also have 64bit Win 7 and have these folders.I suspect system need them to store some logs - poorly documented.

EDIT
I've just checked other machines with Windows 7 and some have these folders and another not so it's normal here.I do not know what does it depend...

 

[mjf]

Flavious thanks for checking. I'm running Home Premium and you appear to use Professional. Prof and above may provide more network services????? (yes a wild guess).

 

[Flavius]

Flavious thanks for checking. I'm running Home Premium and you appear to use Professional. Prof and above may provide more network services????? (yes a wild guess).

On virtual machine I have Basic,Home Premium and Ultimate and on Basic,Home Premium really LocalLow folder doesn't exist but in Ultimate and in my system for daily work (Proffessionall) this folder exist so it seem to confirm your theory although I'm not in 100% sure.Interesting on installation disk none of versions have this folder.Maybe other people will share their notices...

 

[Joan Archer]

I did the changes yesterday and the error hasn't come back yet, plus I got the 3 updates today so did those.

 

[mjf]

I made the changes and the CAPI2 4107 errors seemed to disappear. However, it may be coincidence but after the MS recommended deletions and syswow64 deletions my disk appeared to play up a bit. Lots of small disk activity/head seeking when normally I would expect far less activity. Big enough of a nuisance for me to image back to before the changes. Seems better now!!!