Issues with Webroot

Avast 4 seriously?!!!

now i understand why the user don't even follow Prevx development to webroot...and you don't find inappropriate that he still use an outdated version...

 

Thank for this latest scathing remark. This one ends up being useful to your cause (see my edit on my previous message).

 

if you mistype don't blame the people that react to it... !

FYI, i don't have any "cause" .

btw you didn't answered my question...(if you turned off avast ); that may help the webroot support team.

 

@guest
Yes, you are right I am shocked at that typo. I could kick myself in the proverbial. I do not criticise that latest scathing post, I thank you for it.

Otherwise no, I did not turn off avast.
As soon as I saw that the problem had been triggered by the install of Webroot by Prevx, I removed Webroot.
I will never keep software that installs itself without telling anyone, this is even more shocking with security software. On this board many people (including you) are committed to Webroot, so they will forgive and forget. I am not married to Webroot, so I don't forgive and forget, even more so since in my case this breach of decent behaviour caused a significant waste of time.

With no intention to keep Webroot, the reason why Webroot was creating problems on that PC (incompatibilities with other stuff, etc..) was of no interest to me, so I did not investigate.
Let the Webroot team find out, they now seem to have a valid lead.

Good-by now, I have done what I could to trace the cause of the issue, I won't be watching this board anymore.

 

One wonders what the reaction would have been had it automatically upgraded to the exact same program (and problems and 'features') calling itself "Prevx 4" instead of "Webroot".

 

Probably less confusion

 

Hi Joe,

Do you think you will get rid of Search Result Annotations all together since most search engines use SSL HTTPS connections? Also in the Mac version?

Thanks,

Daniel

 

The 2014 product will have a different approach which is much more compatible that will avoid these types of issues (and work under HTTPS )

 

That's great thanks.

TH