[There's a reason that Yoda is the unofficial mascot of SBS.  Size indeed matters not.] Crypt32 8 events continuously reported on Windows Server 2003, Windows Server 2003 R2, or Windows XP: - THE OFFICIAL BLOG OF THE SBS DIVA
Tue, Jul 27 2010 23:06 bradley

Crypt32 8 events continuously reported on Windows Server 2003, Windows Server 2003 R2, or Windows XP:

Crypt32 8 events continuously reported on Windows Server 2003, Windows Server 2003 R2, or Windows XP:
http://support.microsoft.com/default.aspx?scid=kb;en-us;2253680&sd=rss&spid=10394

Okay so ... I'm not sure I like the resolution to ignore or untick the update root cert solution.  I've seen this on my servers that have no antivirus (ones that I just deployed), I've seen this on ones where the only firewall is the MS firewall so there's nothing third party on them.

So now what?  Ignore and hang loose looks like still the best plan of action. 

Filed under:

# re: Crypt32 8 events continuously reported on Windows Server 2003, Windows Server 2003 R2, or Windows XP:

Friday, July 30, 2010 7:08 PM by Dean

"On Windows Vista and higher, Microsoft requires that any software the registers and interacts with the Windows Security Center (WSC) be signed with a digital certificate that chains up to an internal Microsoft code signing root certification authority (CA). This CA is called the Microsoft Code Verification Root CA (MSCV). Microsoft has cross-certified the MSCV with multiple third-party code-signing CAs allowing these vendors to continue issuing valid code-signing certificates to their customers.

The MSCV certificate is embedded in the kernel on Windows Vista and higher, but it is not available as part of the Automatic Trusted Root Update service. Whenever the digital signature on one of these applications is checked on Windows XP, Windows Server 2003 or Windows Server 2003 R2, the chain of the vendor's code signing certificate is built up to both the root CA of the third-party that issued the code signing certificate and, by virtue of the cross-CA certificate issued by Microsoft, also to the MSCV. In short, two chains are built and the validity of both are verified.

. . . . . . . . . . . . . . . "

Does anyone understand what the hell Microsoft is saying here ?