Defender and Symantic

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I run XP pro fully updated and a Corporate version of Symantic version 10
with the tamper protection switched on.(configured so that users can't switch
it off). I loaded defender this morning and symantic keeps telling me that
defender is trying to tamper with it. Any ideas?
 
There was a recent report on the Internet that Windows AntiSpyware was
deleting Symantec Antivirus, I don't know if its carried over into BETA 2.
If it does get Quarantined in Windows Defender, click Tools > Quarantined
Items > select any component relating to Symantec and choose Restore.
--
--
Andre
Windows Connect | http://www.windowsconnected.com
Extended64 | http://www.extended64.com
Blog | http://www.extended64.com/blogs/andre
http://spaces.msn.com/members/adacosta
FAQ for MS AntiSpy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
 
Thanks for this. It's not being quarantined, Symantec is just periodically
reporting that defender is tamper with it.
 
I am having the same problem

Windows XP Pro Service Pack 2

Symantec Antivirus Corportate Edition
Program: 10.0.2.2000
Scan Engine: 51.3.0.11
 
I'm having the same problem. XP SP2, SAV CE 10.0.1.1000. I get periodic
warnings from SAV tamper protection.

I'm also unable to update my definitions. Mine are 21 days old, version
1.0.0.0. Defender just says no updates are available. Seems like at least a
few others are having this problem too. Could they be related?

I have tried turning off SAV real time and tampering protection. Still not
able to update.
 
NO--that issue is not present in the definitions available with Windows
Defender, nor was it ever.

This issue with the tamper protection setting has been noted in at least
three threads in various groups. It's real, and I believe Microsoft is
aware of it.
--
 
Nothing in the Symantec app is interfering with Windows Defender updating.
Are you able to update via Windows Update?

--
 
Sorry if this is impertinent for a first-timer here, but,
Who are you, Bill Sanderson, to make this claim? AND
The original problem in THIS thread 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.
 
As a Symantec, Windows Defender, and SpySweeper user, which uniquely
qualifies me to make this post...<g> Symantec 2005+ complains about each
of these third party security products but does not provide an exclusion
list for it's option to "Turn on protection for my Symantec product." The
fault therefore becomes Symantec's for not providing such an
exclusion/authorization capability (unless you happen to be using
Symantec's own AS of course) and I have turned it off as a nuisance.
Symantec says it's Unauthorized access...

Where does Symantec allow me to authorize both Defender and SpySweeper the
access that they should have to any folder or service that Symantec
maintains on my system?

Two of many thousands of entries in Symantec's alert log when this
pain-in-the-neck alert runs:
Event Details:
Time: 10/23/2006 11:45:19 AM
Actor: C:\Program Files\Windows Defender\MsMpEng.exe (PID=1284)
Target: C:\Program Files\Common Files\Symantec Shared\ccLgView.exe
Action: Unauthorized access
Reaction: Unauthorized access stopped

Event Details:
Time: 10/23/2006 11:43:05 AM
Actor: C:\Program Files\Webroot\Spy Sweeper\WRSSSDK.exe (PID=2216)
Target: C:\Program Files\Common Files\Symantec Shared\ccApp.exe
Action: Unauthorized access
Reaction: Unauthorized access stopped
 
In that post, I was responding to the update issue, which has not, in my
experience, been caused by Symantec software.
--
 
Hesch wrote:
“The original 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.â€

This situation makes the it Micro$oft’s problem with Windows Defender,
as concurred by

Bill Sanderson MVP wrote:
“ … This issue with the tamper protection setting has been noted in at least
three threads in various groups. It's real, and I believe Microsoft is
aware of it.â€

It seems you missed this point when
 
So by your logic, Microsoft is also somehow responsible for Symantec
alerting to not only SpySweeper, but any other product that scans Norton's
folders? Symantec should do nothing, letting all the other vendors
accommodate it's pristine presence?

There's a simple solution, at least for you... don't use any security
product that you feel doesn't accommodate Norton. You can be what the
industry used to call a Symantec Shop.

Personally, I'd just like to see Ms and Symantec kiss and make up, but the
worldwide revenue from security software is estimated to be at $12 billion
next year, so the odds seem unlikely.
 
By MY logic, if Micro$oft's Windows Defender offers an option to
"NotScanTheseFiles" and then IGNORES that setting, it IS Micro$oft's
responsibility. If SpySweeper offers a similar option and ignores it, then
that is SpySweeper's provider's responsibility (I am not going to do the
research - I don't know who is connected to SpySweeper).

I still agree with you that Symantec / Norton should, in a better world,
offer an option to ignore 'interference' OF THIS KIND from specified
programs. It should NOT be required to ignore ALL file manipulations from
ANY sources, else what is the point of a security product?

My first temptation on reading your response was to ask if YOU could read.
I can NOT fully refrain.

Peace - Hesch
 
Back
Top