"S7eele Rayne" wrote:
> I tried setting my date back going to the extent of restarting IE each time,
> no luck. I also visited the site specified below but the instructions I saw
> applied to web servers, not a "client" running IE.
For me this problem only began after installing the Update to IE6 SP1,
KB831167. Since the error message 0x800C0008 is related to SSL and the update
KB831167 also targeted SSL problems I believe the update 831167 is the
culprit. I am betting that it affects anyone who installs this "Critical"
update that does not infact need the update. i.e. they are not experiencing
the problems outlined in the "Critical" update. But since it is "Critical" it
gets installed... even, eventually, by reluctant professionals. The offending
update changes the way IE handles SSL. This update is not uninstallable.
Bummer. It should never have been placed as a "Critical" update, period. In
the debugger: The problem seems to occur when the browser attempts to
evaluate some code attached to the Update page that initializes a survey. Or
at least, the survey code is responsible for calling the DateTime function as
part of the code. Of course I do not have acess to the anonomous code that is
executed so it could be only related to SSL's time function needs or
whatever... So if anyone who can do anything solid about this, take that
update off the "Critical" list and release an update for your update. Just
what M$ needs more updates to replace the updates ( Go Figure ). Grrrrrrr
.............
Try this work around https:// connection to the Windows Update server URL
https://v4.windowsupdate.microsoft.com/en/default.asp ( copy and paste )
Seems to get through, so it seems like a code redirect/handover issue. I
can't imagine how many inexperienced users must've been confused.