Webroot Mobile

​@Guillaume_Pscl I have an issue with the latest Webroot for Android as it says it’s using to much CPU? I did send in a Support Ticket! Thanks!   

I seen this a couple of days ago but we still can use Google Chrome Secured!  

Someone left me a voice message regarding my Webroot account.  I don’t recognize this person.  Is it a good idea to call back these numbers? 

I bought Webroot Essential last year, it will expired February 2027, and i bought Webroot Other earlier this year so i can use it on more devices, but recently my Webroot Mobile app doesn’t work anymore, and it keep saying my subscription has ended, i checked and both of my Keycode still active until 2026/2027, can someone help me?

When I choose remove, the wheel spins as it tries, then a red x appears and the webroot warning is still there. 4-25-25This occurred after phone update.What to do?

Webroot on Android informed me of the following potential threat. I assume “Terminal” is a CLI, but didn’t think Android would have an app for it.  I did not download an app with this name, nor have I recently installed new apps in the last few months.  Never happened in all the years I have used Webroot. I requested the incident be reviewed. Any suggestions?  Thank you.ATTENTION NEEDEDBenign Detected App: TerminalWebroot has determined that this app is malicious. The application or file is benign. 

I had to hard reset my Android cell phone. Tried to set up protection again, and can't get mobile support because it’s stuck in a login loop. See below.   

New to Webroot;  I have 3 subscriptions (laptop/desktop/android) but when I log into my account, only 2 subscriptions are recorded.  I can do a scan on all 3.  I need to feel confident that I have coverage on all 3.  Where/How do I go to find this info.  Thanks.

Hi Webroot Team,Any Major upgrade coming to webroot mobile security??

Loaded on tablet and gave it permission to access all files and then to do a complete scan.  Finished in 3 - 5 seconds and said no problems.  Didn’t show any progress or any detail of how many files it scanned, no way did it scan all files I have on this tablet.  Wasted that license!  

My Android cell has been attacked by a nasty aggressive Trojan!!! It also has access  to my personal email address & sends me emails demanding money. I think I have 'badic' Webroot protection. How do I get Rid of this Trojan??

Over the past month I have been getting a warning from the Samsung  S10e system (Android 12) that Webroot is consuming too much CPU and to disable it.  I’ve also noticed that the phone get very hot even when not charging.  It has 59.5 of 128 GB of Storage available.  Also has 2.7 of 6GB of memory available.  Should I just remove Webroot?

I’ve just renewed my Webroot sub but I cant tell if my mobile and my wife’s are protected. They seem to be working as usual, but but but.When I go to myaccount/security, I can see that my laptop is protected, but nothing else. At the bottom of the page it states, “*Mobile and Chromebook devices aren't displayed for the moment.” That moment has actually lasted months.Any idea who/how to get it working? Alasdair

As far as I can tell I only have 1 connection going. I see there was a solution, can I get that? Thanks. 

I see that I have the same problem as everyone else who has the Samsung S22 Ultra cell.  I can not load Webroot on my cell as there is a bug.  The program works fine on my husband’s S19 and it worked fine on my S18.  These are the 2 screens I get.  Is there a resolution for this?  It doesn’t do me much good to have antivirus protection on my tablet and laptop but not on my cell.  HELP PLEASE!  I tried to get this resolved with GeekSquad and they couldn’t resolve it either.  This isn’t good that the latest, greatest cell update can’t get Webroot protection.  PLEASE HELP!Here is the screen I get.   When I click on GO, this is what I get.When I click on Learn More, I get an AW SNAP! screen.  Then when I click on Reload I get the following message:“Something went wrong with Webroot.  Webroot closed because this app has a bug.  Try updating this app after its developer provides a fix for this error”. So DO WE HAVE A RESOLUTION YET?

I’ve had Webroot on my android for the past few years. About six months ago, it quit working (but the same Webroot account on my laptop is working fine). Whenever I open the app, I get the “Information has not been verified yet” page. I contacted Webroot and was told “this is a problem from their end and they’re working on a fix. Six months later, still no fix. Do I have to ditch Webroot?

Webroot Secure Anywhere was working on my Samsung android until this morning. I received a message saying “information has not been verified yet”. When I clicked on it, the message said “can’t open this page”. After trying to restore my phone and  uninstalling/reinstalling Webroot, the problem still exists - basically I cannot sign on/activate it on my phone. I also checked Webroot on my laptop and it works fine. Any help would be appreciated.

Yesterday, both of my Android phones had foainting/transparent/Webroot banner / pop -up. I thought it was a Webroot Update Reminder.This led to a message that said “Product Tampering,,Security Risk, Download from Google Play Store.But is no Update for phones on Play. IHas someone hacked my phones or is this some sort of idiot spam from an idiotic Bad Actor ? I have received mocking messages from BAs in the past that were nothing once I talked about the FBI 's ic3.gov site and here is your Proxy Address, here is what domain it is maintained in and here is what Nation you come from, here are your GPS coordinates, etc. I have opened a Support Ticket with WB. How do I get rid of this floating icon if everything is okay ? I am VERY security  Cautious!Finally, what is everyone's opinion on WB's VPN ? I do not use a router or modem to get WI-FI and I may try to use a third party route to get Ethernet.Thank you ...

I downloaded the webroot app on my Google Pixel 4a(5G) running Andoird 13 I go to create an account but it wants a keycode to create an account. How do I get a keycode before creating an account. Typically software works like this… Create account → Purchase Product → Get keycode → Enter keycode → Activate product. This app is asking me for what normally happens in step four but wants it in step one before I even have an account. Where do I get this keycode to create an account? There are no instructions in the app.

Webroot mobile used to have a security app and a browser app.  I never used the browser since everything I have is synced to Vivladi.  Webroor security was alwys running on my phone.  Now it appears that the security and the browser have been merged into one app and my android phone is only secure when I use the Webroot Browser. Since everything I have is synced to Vivaldi, I don’t want the Webroot browser.  Now this once useful app is useless.  Since Webroot was gobbled up by Carbonite it has ceased to be what it once was.  After over ten years when my subscription expires I will sadly being saying good bye to Webroot. 

Sent a support ticket 9 days ago...no response. After a long wait on hold today I finally got through to someone that verified what I suspected. There is a BUG they are working on specifically with Android Version 12 UI Version 4.1. There is no information on when this BUG will be fixed. I hope this post will help or save you some time if you are encountering the same issues. 

I enabled webroot to use Lastpass authenticator. When I got a new phone webroot info did not transfer in the Lastpass authenticator app.  I do not have a secret code to start over because I can not access my webroot account.  Where do I go from here?

How can I completely close my account and so that I can stop getting upgrade notices on my phone that don’t work?  I literally get a notice every 5 or 6 minutes and following the upgrade instructions goes to a broken link. If WebRoot cannot get a simple upgrade to work then how can I trust them to provide security for my devices? I’m not the only one with problems because numerous people have left one star reviews of the phone app over the last few weeks and Webroot has obviously not addressed the issue.