I run a program called VersionTracker Pro that runs at system startup.
Defender intercepts this and asks what action to take as it is currently 'Not
Yet Classified'. I allw the action but the entry VersionTracker Pro.lnk is
not placed in the allowed list. In fact this is and remains empty. Anyone
else seen this behaviour?

Phil

It seems that the only items that go into the allowed list are items allowed
during/after a scan. Items that are allowed following a pop up from real
time protection go into the history. Check the history screen. There also
does not seem to be a way to "always allow" under those circumstances. I
hope they add that function soon.
--
Old Rebel: Too Old to Rebel; Too Young to just take it!


"lonewolf246" wrote:

> I run a program called VersionTracker Pro that runs at system startup.
> Defender intercepts this and asks what action to take as it is currently 'Not
> Yet Classified'. I allw the action but the entry VersionTracker Pro.lnk is
> not placed in the allowed list. In fact this is and remains empty. Anyone
> else seen this behaviour?
>
> Phil

Thanks for the reply.
It would seem an obvious 'enhancement' to always allow after any scan or
other notify action!

"Old Rebel" wrote:

> It seems that the only items that go into the allowed list are items allowed
> during/after a scan. Items that are allowed following a pop up from real
> time protection go into the history. Check the history screen. There also
> does not seem to be a way to "always allow" under those circumstances. I
> hope they add that function soon.
> --
> Old Rebel: Too Old to Rebel; Too Young to just take it!
>
>
> "lonewolf246" wrote:
>
> > I run a program called VersionTracker Pro that runs at system startup.
> > Defender intercepts this and asks what action to take as it is currently 'Not
> > Yet Classified'. I allw the action but the entry VersionTracker Pro.lnk is
> > not placed in the allowed list. In fact this is and remains empty. Anyone
> > else seen this behaviour?
> >
> > Phil

I like Defender even though I have had a few problems with it. I think the
final GM product should be great. My biggest complaint so far is that there
is too much that is not "obvious" to us ordinary users. The Help file is not
that enlightening either.
--
Old Rebel: Too Old to Rebel; Too Young to just take it!


"lonewolf246" wrote:

> Thanks for the reply.
> It would seem an obvious 'enhancement' to always allow after any scan or
> other notify action!
>
> "Old Rebel" wrote:
>
> > It seems that the only items that go into the allowed list are items allowed
> > during/after a scan. Items that are allowed following a pop up from real
> > time protection go into the history. Check the history screen. There also
> > does not seem to be a way to "always allow" under those circumstances. I
> > hope they add that function soon.
> > --
> > Old Rebel: Too Old to Rebel; Too Young to just take it!
> >
> >
> > "lonewolf246" wrote:
> >
> > > I run a program called VersionTracker Pro that runs at system startup.
> > > Defender intercepts this and asks what action to take as it is currently 'Not
> > > Yet Classified'. I allw the action but the entry VersionTracker Pro.lnk is
> > > not placed in the allowed list. In fact this is and remains empty. Anyone
> > > else seen this behaviour?
> > >
> > > Phil

Shoot me a mail if you have some specific topics in the help file which seem
confusing. We would love to correct those.

--
-steve

Steve Dodson [MSFT]
Windows Defender Beta Lead
MCSE, CISSP
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
"Old Rebel" <(E-Mail Removed)> wrote in message
news:7B20F096-282F-4DAB-81E3-(E-Mail Removed)...
>I like Defender even though I have had a few problems with it. I think the
> final GM product should be great. My biggest complaint so far is that
> there
> is too much that is not "obvious" to us ordinary users. The Help file is
> not
> that enlightening either.
> --
> Old Rebel: Too Old to Rebel; Too Young to just take it!
>
>
> "lonewolf246" wrote:
>
>> Thanks for the reply.
>> It would seem an obvious 'enhancement' to always allow after any scan or
>> other notify action!
>>
>> "Old Rebel" wrote:
>>
>> > It seems that the only items that go into the allowed list are items
>> > allowed
>> > during/after a scan. Items that are allowed following a pop up from
>> > real
>> > time protection go into the history. Check the history screen. There
>> > also
>> > does not seem to be a way to "always allow" under those circumstances.
>> > I
>> > hope they add that function soon.
>> > --
>> > Old Rebel: Too Old to Rebel; Too Young to just take it!
>> >
>> >
>> > "lonewolf246" wrote:
>> >
>> > > I run a program called VersionTracker Pro that runs at system
>> > > startup.
>> > > Defender intercepts this and asks what action to take as it is
>> > > currently 'Not
>> > > Yet Classified'. I allw the action but the entry VersionTracker
>> > > Pro.lnk is
>> > > not placed in the allowed list. In fact this is and remains empty.
>> > > Anyone
>> > > else seen this behaviour?
>> > >
>> > > Phil

The WD Help file states that "you can stop Windows Defender from alerting
you to risks that the software might pose to your privacy or your computer.
The next time Windows Defender alerts you about the software, on the Action
menu, select Always Allow." [I copied this directly from the help file.]
However, my Action menu only has two options: "Allow" or "Block". If there
is no "Always Alow" option in the Action menu, the help file should not state
that there is.

"Steve Dodson [MSFT]" wrote:

> Shoot me a mail if you have some specific topics in the help file which seem
> confusing. We would love to correct those.
>
> --
> -steve
>
> Steve Dodson [MSFT]
> Windows Defender Beta Lead
> MCSE, CISSP
> http://blogs.technet.com/stevedod
> --
>