Skip to main content
At Webroot, we continually strive for excellence. We're very excited to unveil our latest improvements to SecureAnywhere:

 


  • New interface that's even easier to use
  • Features and protection information at your fingertips
  • Set it and forget it – continuous protection without interruptions or slowdowns
  • Stronger identity protection with real-time anti-phishing to block fake websites that trick you into entering your personal information
  • A seamless update process – product improvements are continually added in the background, with no action required
For a quick recap of what's changed, please take a look at this video, featuring @, our lead developer:

 

 



 

Additional screenshots and explanations are available on this page.

 

So, what are your initial thoughts?  We love feedback!
Hello TEXPHIL and Welcome the Webroot Community Forums.

 

Please look at my post here as WSA is compatible with Win 8.1 both 32bit & 64bit! https://community.webroot.com/t5/Webroot-SecureAnywhere-Internet/Windows-8-1-upgrade/m-p/62825#M1898

 

And there is no need to YELL!

 

Thanks,

 

TH
Thanks TH. :robothappy:

 

TEXPHIL - Please let me know if this resolved your issue so I know whether this issue requires gathering logs and more investigation on our part.

 

Did the fresh uninstall/reinstall that TH suggested work?
No...  I uninstalled and re-installed a couple times. The problem isn't whether Webroot Secure aAnywhere is compatible or works in W8.1. The app seems compatible. The problem is with the Password Management Toolbar. It is NOT compatible with Internet Explorer 11. I even tried the "toolbar Fix" app and that did not work. It works fine in my Chrome however. By the admission of a Webroot Tech, the toolbar is not compatible and they are aware of this issue and supposedly working on a resolve. Again, why would Webroot release an app knowing that part of it is not compatible with the new IE 11 and not mentioning that in any of it's release notes......
Thank you for your response and patience. The issue should be fixed in the next version update of the extention. 

Reply