C
Chris Barnes
I suspect this might be a Defender issue and not an Outlook issue, but
I'm going to try it here.
I have a shortcut to Outlook.exe in the Startup folder of my windows
profile. It's in MY profile (not All Users). It works perfectly
(meaning OL starts when I logon).
When Defender starts, it sees that there is an outlook.lnk and flags it
as a possible item to be protected against. Every morning, I click on
the "allow" (which succeeds).
Wouldn't you think that Defender would know that OL in the startup group
is not an unwanted behavior?
I'm going to try it here.
I have a shortcut to Outlook.exe in the Startup folder of my windows
profile. It's in MY profile (not All Users). It works perfectly
(meaning OL starts when I logon).
When Defender starts, it sees that there is an outlook.lnk and flags it
as a possible item to be protected against. Every morning, I click on
the "allow" (which succeeds).
Wouldn't you think that Defender would know that OL in the startup group
is not an unwanted behavior?