http://support.microsoft.com/Default.aspx?kbid=896424

I had a weird problem this morning. I have been working on an IE
application, and this application opens windows (using window.open())
without a status bar, but this morning these windows opened with status

bars.

After a bit of testing and head scratching, I realised that my intranet

based website was being shown as in the Internet zone according to the
status bar.

Off to Tools, Options, Security, Local Intranet, Sites, Advanced I go,
and my list is empty.

Humm, the security update wiped all my zones (I thought). So I added
my intranet URL back, OK'd everything... but the browser still shows it

as in the internet zone. So I go back into the sites dialog, and the
URL I had added is not there. I try and add it again, but I get a
message saying it is already in another zone.

As I knew there had been a windows update last night, I went to
add-remove programs and removed update KB896424, rebooted.

I can now add URL's back into my Local Intranet zone, and my
application is now working again. The *ONLY* thing I did to get this
working again is uninstall this update and it only started happend
after this update arrived, so it is almost certainly the culprit.

It auto-updated again over the weekend, and it broke IE in exactly the
same way. Uninstalling the update again fixes the problem.

How can I stop this update from installing? I have for now disabled
automatic installs.

"()z" <Austin.France@Ramesys.com> schrieb:

> Humm, the security update wiped all my zones (I thought). So I added
> my intranet URL back, OK'd everything... but the browser still shows it
>
> as in the internet zone. So I go back into the sites dialog, and the
> URL I had added is not there. I try and add it again, but I get a
> message saying it is already in another zone.
>
> As I knew there had been a windows update last night, I went to
> add-remove programs and removed update KB896424, rebooted.
>
> I can now add URL's back into my Local Intranet zone, and my
> application is now working again. The *ONLY* thing I did to get this
> working again is uninstall this update and it only started happend
> after this update arrived, so it is almost certainly the culprit.

I highly doubt that KB896424 is the culprit for what you've
experienced. Just let it install again while your AV scanner
and Personal Firewall software doesn't run in the background.
Since you seem to be running Windows XP SP2 according to the
headers of your Google posting, enable the Windows firewall
instead.

Bye,
Freudi

Ottmar Freudenberger wrote:
> I highly doubt that KB896424 is the culprit for what you've
> experienced. Just let it install again while your AV scanner
> and Personal Firewall software doesn't run in the background.
> Since you seem to be running Windows XP SP2 according to the
> headers of your Google posting, enable the Windows firewall
> instead.

Installing this update with the virus scanner disabled solved the
problem.

First time I have ever had a problem with a windows update when the
virus scanner is active and with the apparently unrelated symptoms it
hadnt occurd me to try without the scanner enabled.

I trick I will remember for the future.

Thanks

"()z" <Austin.France@Ramesys.com> schrieb:

> Installing this update with the virus scanner disabled solved the
> problem.

Fine, thanks for posting back :-)
I can assure, it's not the first time, AV software and the like
*does* have an influence on installing updates. I and many other
experienced users too recommend to disable *any* at least AV
software in front of *installing* any update.

Bye,
Freudi