Skip to main content
To Customer Support To Customer Support
I got a pop up today from Webroot saying that this file was trying to connect to the internet. It was recommended that I block it if I didn't know what it was, so I blocked it. Then I looked it up onlline (I didn't have time before it was going to allow it.) and I found that this process belongs to Windows. So is that going to cause problems?

 

And how do you unblock something if you need to? I thought if you blocked something that it would add an entry under Applications in Identity protection?

 

And why is Webroot flagging so many things for the past month or so?

 

I've had at least 8 programs that Webroot will flag. These programs have all existed on my PC for a long time. But I updated to the lastest version and then they become untrusted. I have been in contact with Support and they told me what to add under Identity protection to fix the issue. And they fixed some of them somehow without me doing anything. But at least one of those programs started popping up the warning again when I applied the latest update.

 

So my biggest question is...how do fix it if you block or allow something that you shouldn't have? And should SettingsSyncHost be allowed?
Hi Kev914

 

Hope that yo are well?

 

How to unblock a process for which you have blocked Internet access? Relatively straight forward; click on the gear/cog symbol to the right of 'PC Security' > under the 'Scan & Shields' tab click on the 'View Active Connections' button on the right handside of the panel. In the next panel displayed scan down the list pf processes displayed in the top half, and all being well you should find the relevant process listed...then just change the status from 'Block' to 'Allow'...and that should do it!

 

EDIT: Apologies...I missed replying to the 2nd part...which is that most likely what you are seeing (and what we all see occasionally from time to time) is as a result of there having been an update of software; in this case Windows, and not all of the changed components have been registered in the Webroot Cloud, hence a scan and/or actually using the 'new' file version causes what you are seeing.

 

All AMs suffer to some extent from FPs (False Postives) even WSA.

 

You can Open a Support Ticket to let the Support Team know about this and they will then review & whitelist the 'new' file, and then that will also take care of the issue.

 

Hope that helps?

 

Regards, Baldrick
Thanks, Baldrick.

 

I have a related question. Not the same file, but still the same concept.

 

I have had at least 7 programs that recently started getting Webroot alerts whenever I run them. I contacted Webroot about all of them and they came back and told me they were all fine and that I should add the files they gave me to the Application Protection list so that Webroot wouldn't warning me every time I used them.

 

I did that. And it worked.

 

For a time.

 

But some of the programs have what they call continuous updates. (Instead of just releasing a new version once a year, some programs have gone to a concept where they push out updates when they become available. Some software venders offer both concepts. A few have converted to the continuous updates only.

 

And it seems that when they update the program, then it goes back to Webroot alerting you that the program is trying to connect to the internet and is untrusted. It's weird because sometimes it seems like the file name is exactly what is already listed in Application Protection.

 

So that was the background.

 

Here's my question.

 

When you add a program to Application Protection, does Webroot still protect against it trying to transfer personal infomation, etc. or does Webroot not even monitor it anymore since you added it to the Application Protection panel?

 

It seems like some programs need to be added there, but I just want to feel safe that I am still protected against keyloggers and such.

 

 
Well, I know one vendor who operates as you describe...our very own Webroot...:D

 

The reason for the "because sometimes it seems like the file name is exactly what is already listed" you speak of is due to the fact that the checking is done on far more than just the file or process name; I do not have the details of all that is checked (Webroot would not want to divulge that so the miscreant get to know it)  but one of the details is the MD5 signature that has been generated for the file (and new versions of the same named file will have different MD5 signatures, i.e., a unique signature).

 

Now to answer your question...it is precisely the adding of a program to Application Protection that causes Webroot to protect it against keyloggers, etc., from accessing personal infomation. So make sure that you have all such files/programs defined there if not automatically detected.

 

Regards, Baldrick
Thanks, Baldrick. That's reasurring to hear.

Reply


Terms & Conditions