G
Guest
I've been away from this for a time. Does Beta 2 solve the Defender
interfering with Symantec problem??
interfering with Symantec problem??
P
plun
Hi
No, perhaps if representatives from MS and Symantec sit down
and smokes a "piece pipe"....
Nevertheless if you are running NIS 2006 there is no meaning to also
run
WD, NIS definitions are better... NIS 2005 does not include security
threats.
regards
plun
No, perhaps if representatives from MS and Symantec sit down
and smokes a "piece pipe"....
Nevertheless if you are running NIS 2006 there is no meaning to also
run
WD, NIS definitions are better... NIS 2005 does not include security
threats.
regards
plun
G
Guest
Thanks for this.
It's NIS 2005 and corporate with the interference option locked on.
I guess I shall leave Defender off then...
Regards
It's NIS 2005 and corporate with the interference option locked on.
I guess I shall leave Defender off then...
Regards
G
Guest
Hi Plun
Well said. That just about sums it up . These guys need to sit down and
smoke `Um Big Pipe of Piece`true aboriginal style?. Just like they did B4 the
Brits arrived and settled in New Hampshire
Thing that I have to wonder is
....... Where did George Bush Jnr come from ? Not UK . Must have been a
stowaway from Sweden
Regards
Stu
Well said. That just about sums it up . These guys need to sit down and
smoke `Um Big Pipe of Piece`true aboriginal style?. Just like they did B4 the
Brits arrived and settled in New Hampshire
Thing that I have to wonder is....... Where did George Bush Jnr come from ? Not UK . Must have been a
stowaway from Sweden
Regards
Stu
G
Guest
The problem is that Windows Defender is 'interfering with' Symantec
-- that is, it keeps on trying to open Symantec files --
even though I have cited each of them (there are four folders)
under Windows Defender's
AdvancedOptions>DoNotScanTheseFilesOrLocations.
That makes this Windows Defender's bug, rather than a
[possible] problem with Symantec or Norton. I agree that
Symantec/Norton should have an 'ignore' list, but,
by offering the option above, Micro$oft claims to HAVE the
corresponding list.
-- that is, it keeps on trying to open Symantec files --
even though I have cited each of them (there are four folders)
under Windows Defender's
AdvancedOptions>DoNotScanTheseFilesOrLocations.
That makes this Windows Defender's bug, rather than a
[possible] problem with Symantec or Norton. I agree that
Symantec/Norton should have an 'ignore' list, but,
by offering the option above, Micro$oft claims to HAVE the
corresponding list.