Webroot SecureAnywhere Discussion & Update Thread

Awesome and I'm testing both settings as well as it's been awhile since I did!

Also got a reply about: I passed along your observation about the documentation . I think it is sufficient to replace “websites” with “applications” to get to the desired meaning.

 

Yeah, exactly

I think WRSA's concept is similar to Comodo's.

Comodo:
Good=allow
Bad=block & quarantine
Unknown=sandbox

WRSA
Good=allow
Bad=block & quarantine
Unknown=monitor, journal & get ready to revert actions

If you set heuristics to "warn when any new program executes that is not specifically whitelisted", any unknown will generate an alert, then the user can choose to either block or allow.
Like this there won't be any monitoring and, as a good side effect, the size of WRdata folder shouldn't increase too much.

What do you think?

 

Well lets say you updated a program and you Allow it but it's still unknown to the Webroot Cloud Database then it will start monitoring. What I do for some not well known programs I send in a ticket and ask them to whitelist the unknown files.

 

Yes, you are right
Actually, if you get a warning because an unknown program wanna run and you choose "allow always", WRSA will add that program to the "block/allow file" list and set it under "monitor". So, to avoid monitoring, you have to manually click on "allow" under "PC Security --> block/allow file"

 

If it's still unknown and you do that it will still be monitored as it's not known to the Webroot Cloud Database but you just allowed it locally.

 

Has anyone been able to install WSA v9.0.27.49 on 32-bit Windows?

 

I can't help you, sorry. I'm on Windows 10 64bit

 

Same here, but my friend is on Win7 32-bit and is unable to update his WSA to this latest version?

 

It should be v9.0.27.64 and here is the link to the installer and it should install on 32bit systems: http://anywhere.webrootcloudav.com/zerol/wsainstall.exe

Could your friend have a Best Buy Subscription? If so he will need this link to download but it's still at v9.0.26.61: http://anywhere.webrootcloudav.com/zerol/wsabbs2.exe

 

Hmm, my copy of WSA has been on v9.0;27.49 for a few months now without having received any update? I got my copy of WSA from the bank where I do my banking.

Edit: Using your top link, I was able to update my copy without a problem, BUT why isn't it updating on its own?

 

I had this same issue when I used WSA. I sometimes had to submit a support request in order to get updated.

Hmmm.... If some WSA users don't check here at Wilders or some other source of update info, I wonder how long they could be using a superseded version without knowing it?

 

You could look here as well: https://www.webroot.com/us/en/support/support-consumer-release-notes

 

As you can see the one for Best Buy Subscriptions is still at v9.0.26.61 and they have others as I assume the one from your bank is a different download link? In time all download links will be at the same version at this time v9.0.27.64 is via the standard download link: http://anywhere.webrootcloudav.com/zerol/wsainstall.exe see here for more info: https://www.webroot.com/us/en/home/products/wsa-installer-download

https://answers.webroot.com/Webroot/ukp.aspx?pid=12&app=vw&vw=1&login=1&json=1&solutionid=1098 Webroot now does a gradual rollout method for releases. As such, not everyone will receive the update at the same time.

 

Great link, TH. 10Q to the nth!

 

@Triple Helix - thanks for those links and the suggestions! I have another question regarding WSA threat alerts...

WSA alerts that 'atapi.sys' is a threat when Shadow Defender is scheduled to enable Shadow Mode on bootup! While I believe this alert may be a false positive I am concerned, so what's the appropriate action for me to take?

 

I had problems with the bank version of WSA and had to reinstall it after having manually updated it with the non-bank version link. The bank version is slightly different, despite having the same version number.

 

I would advise checking the file for a Microsoft signature and uploading it to Virus Total just to make sure it's OK. (Frequent false positives was ultimately why I stopped using WSA.)

 

The best thing to do is Submit a Support Ticket and they will sort it out for you.

 

A weird question I've had for a while: Does anyone know how well identity shield still works with Chrome blocking injection into the Chrome process? Has this impacted Webroot's cornerstone protection feature at all?

 

I would assume that if Webroot was being blocked, you wouldn't see the padlock when opening Chrome. I don't have Webroot so I can't test myself, but Webroot users should be able to use Process Explorer to see if Webroot dll is being injected in any Chrome process.

 

I'm never removed Webroot on my back-up computer. Webroot is still running & up-to-date on that computer. I checked it just now. NO padlock when running Chrome.

 

I have the padlock when running Chrome. You have to go into id setting and add app of Chrome.

 

No issues here.

 

Chrome should add itself but I had to add the new Chrome based Edge to the ID Shield.

 

I sometimes see the padlock and sometimes don't. Chrome is added in the ID shield section but it doesn't always show the lock...