"Matty" wrote:
> > Ehm, you may whish to contact Esent, the vendor of NOD32 instead to fix
> > the possible issue - although I doubt that NOD32 is causing the issue on
> > your end. 3rd party Personal Firewall Software running is my favorite,
> > followed by Anti-Spy/Mal/Adware software running in the background for
> > causing the issue.
>
> I do not have a third party firewall software.
> I run anti-spy/mal/adware softwares on demand. I do not run them in the
> background.
Okay, to shorten the story:
*Which* software is running *exactly*?
*Which* Anti-Spy/Mal/Adware do you have installed *exactly*?
And you're still asking for Windows XP SP2, on which you where *still*
unable to install the lastest OE Cumulative Update and the newly released
Security Update for OE under Windows XP SP2, right?
http://groups.google.com/groups?thre...TNGP04.phx.gbl
>>They are blocking the new version of iexplore.exe
>> contained in *every* Cumulative Update for IE7 from accessing "the net".
>> That's plain stupid and should be fixed by the vendors of the "Security
>> Software".
>
> The cumulative IE7 update came out much much later than the antivirus
> softwares already installed in people's computers. Shouldn't MS be coming
> out with updates that fit into what's already existing instead of expecting
> existing softwares (and users to switch to softwares that don't conflict
> with the updates) to adapt to the new IE7 updates?
Nope. You've decided to install IE7, right? The AV software (or whatever
"Security Software" is running/installed) shouldn't have any effect on the
contents of a Windows update, right?
Although some "Security Software" vendors are creating and releasing
application that seem to compatible only to themself and seem to be tested on
a Windows version which isn't yet released nor developed, it's still the
"Security Software" (vendors) which should make sure, that essential updates
for Windows aren't blocked by accident. It's IMHO not on MS to dance after
the pipe of "Security" or any mor or less broken application installed on
their OS, it's the other way around.
Anyhow, that doesn't solve the problem you've ran into (once again). So
please be so kind to simply answer the questions in case you're searching for
help from other users. If you want to contact MS, please do so by
calling/mailing them directly.
Bye,
Freudi