Skip to main content

I have asked this question at least twice before and never had a response. Why do trainers get zapped even when they have been whitelisted etc on secureanywhere? I have to disable Webroot before using a trainer. A dangerous situation to be forced into, particularly when no explanation for it is offered.

It seems very obvious that Webroot is still running in some way or another after, supposedly, disabling it. This is simply dishonest and demands an explanation

Hello @meditek10 

I do see where you did ask this question a few times and the first being 9 months ago and was not answered.

https://community.webroot.com/tech-talk-7/odd-behaviour-with-a-trainer-336829

 

https://community.webroot.com/tech-talk-7/continuing-irritating-problem-339602

Let me ping our Forum Manager @freydrew Maybe he can give some input on this situation.

 

Dave.


Thanks from an old gamer (80) who finds playing with these aids essential.


It looks like the Forum Manager @freydrew is not answering the ping I sent 6 days ago.

@meditek10 please submit a  Support Ticket  or  Contact Webroot Support  to sort this problem. This service is FREE with a Paid Subscription.

Support Ticket System is Open 24/7

 

Note: When submitting a Support Ticket, Please wait for a response from Support. Putting in another Support Ticket on this problem before Support responses will put your first Support Ticket at the end of the queue.

 

HTH,

Dave.


Thanks. In fact I made a mistake in my first post. If I use the “Shut down protection” tab then most trainers work fine. The shutting down trainers I mentioned were simply faulty. The first part of my mail mentioning whitelisting is correct.


Reply