SCAV 10 Tamper Protection warning

[Guest]

Since installing Windows Defender I am getting the below warnng from Symantec
Corporate Antivirus 10.x:

SYMANTEC TAMPER PROTECTION ALERT

Target: C:\Program Files\Symantec AntiVirus\VPC32.exe
Event Info: Open Process
Action Taken: Logged
Actor Process: C:\Program Files\Windows Defender\MsMpEng.exe (PID 908)
Time: Saturday, February 18, 2006 12:48:13 PM

I have noticed that at least one other person is having a similiar issue and
was wondering if there is a fix yet? Thanks

Mac

 

[Bill Sanderson]

The only fix I've heard is turning off the optional feature.

 

[Guest]

Yes, that is the conclusion I have also reached. I checked Symantec's site
and one of the other boards here and this seems to be the only solution at
this time -- hope this is addressed when the final edition is released.
Thanks for the response, it is appreciated.

JRM

 

[Bill Sanderson]

I can understand that this is annoying. Essentially, you have two competing
vendors each of which is trying to do things to protect your system, and
there's a clash, in terms of the actions they separately believe are
appropriate.

I think it is quite likely that this is already under discussion at some
level--we'll see what (and when!) the resolution is.

In some threads related to this issue, users have taken exception to
Microsoft "attacking" Symantec's software. I want to say that I think
nothing could be farther from the truth--I've no doubt that each vendor is
acting in good faith, and taking actions they believe are not
harmful--they'll figure out a way to work this out, I'm sure.
--

 

[Guest]

I agree completely. Each product has many positive attributes but neither can
be responsible for the other. I, too, feel that this issue will be resolved
-- hopefully sooner than later

Mac

 

[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, I think, makes it more than just annoying -- it's a bug.
[Bill - I am just now reading the other threads, and apologize for the
tone of my response in another thread. I read well, but slowly.
Peace - Hesch]

 

[Bill Sanderson MVP]

Can you confirm that the issue is still happening with the released version
of Windows Defender? If your download of Windows Defender predates October
23, and Help, About yields a first version number which is less than
1.1.1592.0

You should go to www.microsoft.com and click on the link about in the middle
of the page, and download the new version which will upgrade what you have
in place.

I don't know wheter in fact this will help with this issue or not but I'd
like to hear from someone using the released version about this.

--

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, I think, makes it more than just annoying -- it's a bug.
[Bill - I am just now reading the other threads, and apologize for the
tone of my response in another thread. I read well, but slowly.
Peace - Hesch]

I can understand that this is annoying. Essentially, you have two
competing
vendors each of which is trying to do things to protect your system, and
there's a clash, in terms of the actions they separately believe are
appropriate.

I think it is quite likely that this is already under discussion at some
level--we'll see what (and when!) the resolution is.

In some threads related to this issue, users have taken exception to
Microsoft "attacking" Symantec's software. I want to say that I think
nothing could be farther from the truth--I've no doubt that each vendor
is
acting in good faith, and taking actions they believe are not
harmful--they'll figure out a way to work this out, I'm sure.

 

[Dave M]

Still Bill...

Event Details:
Time: 10/29/2006 11:46:36 AM
Actor: C:\Program Files\Windows Defender\MsMpEng.exe (PID=1284)
Target: C:\Program Files\Common Files\Symantec Shared\SPBBC\SPBBCSvc.exe
Action: Unauthorized access
Reaction: Unauthorized access stopped

--

Regards, Dave

Can you confirm that the issue is still happening with the released
version of Windows Defender? If your download of Windows Defender
predates October 23, and Help, About yields a first version number which
is less than 1.1.1592.0

You should go to www.microsoft.com and click on the link about in the
middle of the page, and download the new version which will upgrade what
you have in place.

I don't know wheter in fact this will help with this issue or not but I'd
like to hear from someone using the released version about this.

--

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, I think, makes it more than just annoying -- it's a bug.
[Bill - I am just now reading the other threads, and apologize for the
tone of my response in another thread. I read well, but
slowly. Peace - Hesch]

I can understand that this is annoying. Essentially, you have two
competing
vendors each of which is trying to do things to protect your system,
and there's a clash, in terms of the actions they separately believe
are appropriate.

I think it is quite likely that this is already under discussion at
some level--we'll see what (and when!) the resolution is.

In some threads related to this issue, users have taken exception to
Microsoft "attacking" Symantec's software. I want to say that I think
nothing could be farther from the truth--I've no doubt that each vendor
is
acting in good faith, and taking actions they believe are not
harmful--they'll figure out a way to work this out, I'm sure.
--

message
Yes, that is the conclusion I have also reached. I checked Symantec's
site
and one of the other boards here and this seems to be the only
solution at
this time -- hope this is addressed when the final edition is
released. Thanks for the response, it is appreciated.

JRM

:

The only fix I've heard is turning off the optional feature.

--

message
Since installing Windows Defender I am getting the below warnng from
Symantec
Corporate Antivirus 10.x:

SYMANTEC TAMPER PROTECTION ALERT

Target: C:\Program Files\Symantec AntiVirus\VPC32.exe
Event Info: Open Process
Action Taken: Logged
Actor Process: C:\Program Files\Windows Defender\MsMpEng.exe (PID
908)
Time: Saturday, February 18, 2006 12:48:13 PM

I have noticed that at least one other person is having a similiar
issue
and
was wondering if there is a fix yet? Thanks

Mac

 

[Bill Sanderson MVP]

Thanks. I think that answers the question about whether Microsoft will
"fix" this issue. The hope I'd leave is that now that Windows Defender is
released, and Symantec has the final signed code available, perhaps Symantec
will make the change.

--

Still Bill...

Event Details:
Time: 10/29/2006 11:46:36 AM
Actor: C:\Program Files\Windows Defender\MsMpEng.exe (PID=1284)
Target: C:\Program Files\Common Files\Symantec Shared\SPBBC\SPBBCSvc.exe
Action: Unauthorized access
Reaction: Unauthorized access stopped

--

Regards, Dave

Can you confirm that the issue is still happening with the released
version of Windows Defender? If your download of Windows Defender
predates October 23, and Help, About yields a first version number which
is less than 1.1.1592.0

You should go to www.microsoft.com and click on the link about in the
middle of the page, and download the new version which will upgrade what
you have in place.

I don't know wheter in fact this will help with this issue or not but I'd
like to hear from someone using the released version about this.

--

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, I think, makes it more than just annoying -- it's a bug.
[Bill - I am just now reading the other threads, and apologize for the
tone of my response in another thread. I read well, but
slowly. Peace - Hesch]

:

I can understand that this is annoying. Essentially, you have two
competing
vendors each of which is trying to do things to protect your system,
and there's a clash, in terms of the actions they separately believe
are appropriate.

I think it is quite likely that this is already under discussion at
some level--we'll see what (and when!) the resolution is.

In some threads related to this issue, users have taken exception to
Microsoft "attacking" Symantec's software. I want to say that I think
nothing could be farther from the truth--I've no doubt that each vendor
is
acting in good faith, and taking actions they believe are not
harmful--they'll figure out a way to work this out, I'm sure.
--

message
Yes, that is the conclusion I have also reached. I checked Symantec's
site
and one of the other boards here and this seems to be the only
solution at
this time -- hope this is addressed when the final edition is
released. Thanks for the response, it is appreciated.

JRM

:

The only fix I've heard is turning off the optional feature.

--

message
Since installing Windows Defender I am getting the below warnng from
Symantec
Corporate Antivirus 10.x:

SYMANTEC TAMPER PROTECTION ALERT

Target: C:\Program Files\Symantec AntiVirus\VPC32.exe
Event Info: Open Process
Action Taken: Logged
Actor Process: C:\Program Files\Windows Defender\MsMpEng.exe (PID
908)
Time: Saturday, February 18, 2006 12:48:13 PM

I have noticed that at least one other person is having a similiar
issue
and
was wondering if there is a fix yet? Thanks

Mac

 

[Guest]

Here, too, I have to maintain
"Micro$oft has provided 'Windows Defender's
AdvancedOptions>DoNotScanTheseFilesOrLocations', but seems to be
ignoring it. Again, 'That makes this Windows Defender's bug', no matter
what additional function we CAN agree Symantec/Norton should provide."

Thanks. I think that answers the question about whether Microsoft will
"fix" this issue. The hope I'd leave is that now that Windows Defender is
released, and Symantec has the final signed code available, perhaps Symantec
will make the change.

--

Still Bill...

Event Details:
Time: 10/29/2006 11:46:36 AM
Actor: C:\Program Files\Windows Defender\MsMpEng.exe (PID=1284)
Target: C:\Program Files\Common Files\Symantec Shared\SPBBC\SPBBCSvc.exe
Action: Unauthorized access
Reaction: Unauthorized access stopped

--

Regards, Dave

Can you confirm that the issue is still happening with the released
version of Windows Defender? If your download of Windows Defender
predates October 23, and Help, About yields a first version number which
is less than 1.1.1592.0

You should go to www.microsoft.com and click on the link about in the
middle of the page, and download the new version which will upgrade what
you have in place.

I don't know wheter in fact this will help with this issue or not but I'd
like to hear from someone using the released version about this.

--

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, I think, makes it more than just annoying -- it's a bug.
[Bill - I am just now reading the other threads, and apologize for the
tone of my response in another thread. I read well, but
slowly. Peace - Hesch]

:

I can understand that this is annoying. Essentially, you have two
competing
vendors each of which is trying to do things to protect your system,
and there's a clash, in terms of the actions they separately believe
are appropriate.

I think it is quite likely that this is already under discussion at
some level--we'll see what (and when!) the resolution is.

In some threads related to this issue, users have taken exception to
Microsoft "attacking" Symantec's software. I want to say that I think
nothing could be farther from the truth--I've no doubt that each vendor
is
acting in good faith, and taking actions they believe are not
harmful--they'll figure out a way to work this out, I'm sure.
--

message
Yes, that is the conclusion I have also reached. I checked Symantec's
site
and one of the other boards here and this seems to be the only
solution at
this time -- hope this is addressed when the final edition is
released. Thanks for the response, it is appreciated.

JRM

:

The only fix I've heard is turning off the optional feature.

--

message
Since installing Windows Defender I am getting the below warnng from
Symantec
Corporate Antivirus 10.x:

SYMANTEC TAMPER PROTECTION ALERT

Target: C:\Program Files\Symantec AntiVirus\VPC32.exe
Event Info: Open Process
Action Taken: Logged
Actor Process: C:\Program Files\Windows Defender\MsMpEng.exe (PID
908)
Time: Saturday, February 18, 2006 12:48:13 PM

I have noticed that at least one other person is having a similiar
issue
and
was wondering if there is a fix yet? Thanks

Mac