Can't Access Secure Web Pages

[Guest]

Following the installation of KB913446, I have been unable to access secure
web pages, with IE immediately telling me it can't find the requested page.
Access to any nonsecure addesses works fine. I have XP and I have Norton
Internet Security 2004 installed. I tried turning off the Norton firewall as
well as having the Windows firewall turned off, but still couldn't access
secure pages. Then I uninstalled KB913446. After rebooting, I still
couldn't access secure pages. Then I turned off the Norton firewall and
could then get to secure pages. Reinstalled KB913446 and the problem was
right back, no access to secure pages no matter how the Norton firewall was
set. Uninstalled KB913446 again and after rebooting, turning off Norton
firewall, once again could access secure pages. I've looked through the
Norton firewall settings and don't see anything that makes sense as a
possible problem, but who knows. Any suggestions would be greatly
appreciated. I have 3 other machines that have similar configurations
(although the NIS is 2006 version) and I'm holding off on the security
updates for fear of introducing the same problem.

 

[Guest]

I am having the SAME problem. After installing KB913446 and KB911927 I
canNOT access any secure web pages - not even those in my trusted sites list.
I have turned off all firewalls, pop-up blockers, etc. No luck. I've even
removed KB913446 and still no luck. Anyone know what to do at this point?
Deb (Gladys)

 

[Guest]

Deb,

When I uninstalled and reinstalled KB913446 on my PC it was using the
file(s) that had been downloaded earlier via Automatic Update, not going back
to the Update site to retrieve a new copy. I could tell because when I'd go
to Windows Update and go through Express Install, etc., it told me the
KB913446 files were already on my PC and did I wish to proceed with the
install. Apparently uninstalling the update doesn't rid your PC of the
associated files. I was able to use this link
(http://www.microsoft.com/downloads/...74-C37B-472B-BB10-71D4680680A7&displaylang=en)
to download and install a fresh copy rather than what was already on my PC
and my problem went away following the reboot. I don't think it was dumb
luck or a coincidence because just prior to this I had gone back over the
same things I'd tried previously with no luck until I was able to download
the new copy of the update.