Failed extract of third-party root list from auto update cab

System: Microsoft Windows Vista Ultimate SP2 32bit

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 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.
Event ID: 11
Source: CAPI2

Online resources had no clue how to solve this, but they all agreed that it started happening in May, 2009 when SP2 was released. 

7/12/2009
I first added a couple sites to the Trusted List in Internet Explorer:

Also changed time servers:
Click on your Time in the System Tray and then click on the hyperlink for Change date and time settings and then click over to Internet Time and change settings. Change the server to another and click Update Now.  Mine was off a little:

The system time has changed to 7/12/2009 7:33:50 AM from 7/12/2009 7:33:42 AM.

Still no dice.

Changed the time server again after I was getting too many failures updating the system time with time.nist.gov – I’m now using time-nw.nist.gov

7/12/2009
I also followed the link in the error and installed the certificate manually.  It said that the CTL on my computer was newer (probably from installing SP2) but I installed it anyway.

Rebooted and the CAPI2 error is still here.  Reset IE8 and just set it up with default settings.

Rebooted and I’m still getting errors.  Here’s a new one in fact:

WPF error – The Windows Presentation Foundation Font Cache 3.0.0.0 service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

7/14/2009
Still not working. Downloaded and installed the May 2009 Root Certificates from: http://support.microsoft.com/?kbid=931125  but when I installed them, there were errors:

Fault bucket 10471791, type 5
Event Name: PCA2
Response: None
Cab Id: 0

7/14/2009
Opened DCOM config window and recorded some missing references.  Rebooted and the error is still there.

8/1/2009
The error is gone.  Might have been a recent MS Update that cleared it.