mcappins.exe

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

Guest

When running, my Defender only finds "mcappings.exe" which is something from
McAffee. It is "allowed" now, according to the Action taken under "History",
but it is not on the list of Allowed item under the Allowed items under
tools.
Which brings me to the questions, what is exactly that "mcappings.exe" thing
that is the only thing that Defender detects, why the Defender only catches
that in my new computer versus a lot of other things that my old Webrook
antispyware detected (in my old computer). Echoing a comment made by
someone elsewhere in the Microsoft Security newsgrooup, why the difference
between Defender and the other antispyware programs since the Defender seems
to be doing almost no catching and detection?
 
Octavio said:
When running, my Defender only finds "mcappings.exe" which is something from
McAffee. It is "allowed" now, according to the Action taken under "History",
but it is not on the list of Allowed item under the Allowed items under
tools.
Click to expand...

This is exactly the kind of behaviour that I've experienced with the AOL
driver ATWPKT2.sys - it's reported in history and allowed automatically, but
isn't listed as an allowed item - neither is there a mechanism that enables
you to tell Defender to ignore it.

It's worth checking what's happening to your system restore points. Defender
may be creating a 'Defender checkpoint' on every occurrence of this event,
and you may or may not be happy about on such proliferation of checkpoints.

If you go to 'options' and scroll down, and tick the two 'advanced options'
boxes, I think these McAfee events will probably no longer be recorded in the
Defender history, and the system restore points will cease - but you'll get
real time notifications (which you can ignore) instead.
 
I've added a fuller explanation in a new post in General, with the title
'Controlling Defender's spurious reports'.
 
Back
Top