Originally Posted by
zman
March 9, 2010 (if u mean my windows date), today
I missed what the "solution" is if it happens again.
As of 3PM it is working, and I did nothing (not even re-boot).
The solution is to check (and correct) your system date at the time that the error occurs.