Got a Question?

We are deploying Webroot to our clients and have been running into an issue with users unable to login at a certain point. After testing we found it has to do with Webroot being installed on there but we cant figure out what is causing the issue and we've had to remove Webroot. This seems to only be affecting Server 2008 R2 environments. 

I have a computer that will not boot and is displaying the error "File:windowssystem32driverswrkrn.sys" on windows 10 OS. All searches point to an error with WebRoot. How do I fix this issue?

Webroot recently started showing me a popup at start up of Windows 10 containing the words: “Sign up for MyAccount.” I am already signed up! Yet this braindead program keeps showing me the popup. I am getting tired of clicking the little X. There should be some built-in interaction between the popup and the fact that I am already “signed up.” I have tried just about every suggestion on the internet. Apparently Webroot has gone out of their way to circumvent the normal Windows popup override system. HELP!

The printers connect successfully, however when they try to print to them the jobs seem to disappear. Attempting to print again, the printer shows offline in the session even though the Windows 7 OS can communicate with the printer fine. We disabled all functionality with Webroot and the issue persists, however when we flat out uninstall it printing from Citrix works as expected. We have added exclusions for the spooler folder and the Citrix installation folder with no luck. Any advice or feedback is appreciated as this is holding up a deployment of 2000 seats.   Edited update: The printers are connected via network using a mixture of both TCP/IP ports and HP Proprietary ports.

The latest Webroot release 9.0.15.43 with its updated wrkrn.sys file seems to have caused some BSOD's with 2008r2 after our systems rebooted last night.  I was able to delete the file from a repair command prompt and then reboot into normal operating mode.  I have a ticket in with Webroot support about this issue, but I thought my issue should be shared.   Update:  I have talked with an MSP using Webroot who has had the same problem today.  They also report that if you reboot your machine again after Webroot has a chance to reinstall the wrkrn.sys file it will start throwing up BSOD messages again.

Important update on new release for customers operating Webroot Secure Anywhere on Terminal Servers in a virtualized environment   Issued: 22nd November 2016   Overview of known issue: Webroot has been actively tracking and monitoring an issue that affects some customers operating Terminal Servers in a virtualized environment. During a fault condition, a Winlogin 4005 error occurs where an RDS user is unable to connect to the RDS server, and the event logs display a message indicating that Winlogin has stopped responding.   Interim advice issued by Webroot engineering teams recommended setting the WSAB Self-Protection function to ‘Minimum’ on all Server Policies as this significantly reduced the frequency of Winlogin 4005 errors in most cases.   Update: Further to that advice, Webroot engineering teams developed a new, stabilizing agent release to address causes of the 4005 error and m

Hi,   Has Webroot found a resolution to the problem of duplicate entries in the GSM console when agent systems upgrade to Windows 10?   We're constantly having to deal with going into the GSM and look for and deactivate the older duplicate (the windows 7/8 system) when they are upgraded to 10 in order to prevent being billed extra for endpoint usage. Tsk Tsk...   John

I hate to ask this and please no responses telling me to get off these versions of Windows because they aren't supported by Microsoft. I already know that and I'm pushing for upgrades, but I don't control the budget. My question is, how much longer will Windows XP and Windows Server 2003 be supported. I asked last year on this post and was told April 2019. I had heard previously that might be extended and was wondering if that had been decided yet and if so, for how long? Our subscription is up in January and I wanted to get an idea at what we'd be looking at. Thanks for any help you can provide!   Sincerely, Nic

2 days ago BF2042 updated and in the process updated East Anti Cheat (EAC) which is what SecureEverywhere is blocking. Everyone that is using this AV can no longer launch the game. The EXACT thing happened when they updated Back4Blood and updated EAC in the process. Webroot pushed a patch that fixed it. I have sent a support ticket to Webroot but have heard nothing. Oh, BYW, when you completely uninstall SecureAnywhere, the game runs fine.

I have Webroot on 2 different laptops. My subscription just renewed so I checked both of them to be sure it updated. I discovered that one laptop says subscription 371 day and the other says subscription 255 days. Why is there such a difference, shouldn’t both of them be the same?

Today I have about 20% of my endpoints showing a 9.0.26.50 version of Webroot but can't find any announcement on the version list changes and such.

I know I can do it from the endpoint using "Refresh configuration", but can I use an agent command to achieve the same thing?   If so, what is it?   Thanks

I just discovered that Facebook app on my android phone was tracking my activity on the LastPass app.I find unacceptable that a company that provides security services allows an information hog like Facebook to intrude in something  so sensitive. We pay for a service to keep our information private and secure, not to be used and sold. I cannot trust Webroot or Lastpass anymore, I had the software less than a month, how do I get a refund?

Hi.  We have recently seen a number of individuals running W10 build 1709 and WSA 19.0.19.43.  File shares have become unusable, resulting in a "folder path not found" error in other W10 clients and even from the host PC itself.  In all cases, we have found that the host PC can see its own shares, but gets that error when opening them.  Other clients get that message when trying to connect to the host, before listing the shares.  All of the affected were being managed by the workstation policy with Identity Shield enabled.   We have found that after uninstalling the WR client from the portal, and restarting the host PC, that all sharing/access issues are resolved.  As yet, we have not reinstalled WRSA on any of the affected machines and all of the affected are being managed by an alternative AV until we can identify what is causing this.  

Is there any way to uninstall Web Threat Shield from FireFox without using GPO? I have Windows 10 home and there is no GPO on the home version.

Webroot is self aborting on scan. Happens most often at startup but not always. Also occurs on some initiated scans but not all. Webroot has been removed and reinstalled - no change. Two different Webroot tech have remotely logged into my system to check operation, inspect logs etc - no change.Problem was “elevated” to tech department and message received for available times. I responded with a wide range of times available (I’m retired).  Nothing has happened. Multiple follow up messages with no response. Webroot continues to regularly abort scan.

Hello,   Discovered today that the latest build of Webroot on windows 10 computers don’t block any outgoing traffic, no matter what the settings are (allow or block). Also, the advanced settings the of firewall to block programs has no effect as well (I usually have it set to block all traffic unless explicitly allowed). Feel free to test yourself. Would love to know I’m not the only one (tested and broken on three different win 10 machines, works fine on two win 7 machines).    You been warned...

Hi   Since I upgraded a few machines to 1709 last week I noticed some major issues. The most obvious one was group policies with client side extensions failing to apply. I noticed that some Windows folders were denying me access too such as C:ProgramDataMicrosoftGroup PolicyHistory{GUID}. After looking into this further I found this thread and further down mentioned general permissions/access issues. Uninstalling Webroot completely cleared up the issues I was having. I spoke with support who acknowledge (vaugley) that there was a known issue and offered a couple of work arounds with a fix on the horizion. The work around was to turn off "Realtime Shield - Scan files when written or modified". This has worked! A couple of things I would love to know:   1. What exactly is the iss

We have Sality infections spreaded over 350+ endpoints. Webroot support simply suggested to re-image endpoints - which is obviously the latest thing we want to do.   Some endpoints (the file servers and some clients) we cleaned with ESET/Kaspersky boot CDs. ESET/Kaspersky found 100-600 infected files per endpoint, one files server had 68.000+ infected files that Webroot did not find!   but still the company cannot work as infected endpoints reinfect file shares, and then from file shares even cleaned PCs got reinfected again. We use Webroot on the servers, too, and it does not stop reinfection of shared folders!   We think maybe we should do a full scan with Webroot on all endpoints, but we cannot see any agent commandfor that in the console. How could we command Webroot to do a FULL scan on all endpoints in the Management Console?   Any other idea how to get rid of Sality?

Hi folks - Could I ask, the Secure Anywhere application / subscription of course has a built-in firewall. I am running Windows 11 which has its own Windows defender also with a firewall. Currently I have both enabled but is this necessary and could it cause performance degradation in respect of internet speed or possible conflicts?? Is it better to have one or the other live rather than both running at the same time.To date I don't believe I have had any conflicts, but my system does sometimes have issues with internet connectivity which could be due to having x2 firewalls running at once.Thank you - Ben

The Scans on my Webroot have been doing something weird the last week and a half. Every four or five days I notice a scan occurred that I did not initiate nor was it a scheduled scan. I also notice that every time it happens the number of scans done is reduced to 2. I’ve already bee in contact with Customer support and uninstalled and reinstalled Webroot like they told me to do and this is still happening. I’m getting kind of paranoid now that some sort of virus is somehow messing with my Webroot. Has anyone else ever had a problem like this, I’m getting worried. I sent a support ticket on July 4th understanding that it’s a holiday and they wouldn’t get to me immediately but it’s been two days since then. 

In May, someone posted that Windows Server 2016 would be supported by WR Endpoint Protection sometime in late summer or earlier.   We are about to install a brand new server with that operating system.  We really don't want to install a downgrade to 2012 just to be able to install antivirus.  Is there an update on that timing?  I assume that we can't run it at all on Windows Server 2016, or does the console just not recognize it as different from 2012?

I do not know what's different and it's not every update, but often when Opera updates and I go to run it I get this error message. The error message "fixes" were useless as it turns out Webroot is somehow blocking the program. I have confirmed that Webroot is the offender as I can run Opera just fine when I shut down protection. Michael

Hey guys this is my first post… After a Webroot update,  task manager is showing 2 more processes , WRCoreService.x64 and WRSkyClient.x64.I know someone already posted about it but i still don’t have any info on those 2 and what they are for. Also as a customer who likes lightweight software, watching 2 extra processes from my AV without any info is not the best.I would love to see all those processes (4 in my case) grouped into 1. Cheers

My website got hacked about 10 days ago.  I thought it had been totally fixed (restored from backups), but apparently there were remnants of the infection that were on the backup. So, Webroot (and one other) detection was triggered when I used the VirusTotal website.  Now, the infection has been completely removed, but despite doing a fresh scan on VirusTotal, Webroot is still showing the site as being malicious. How do I get Webroot to take another look at the site?The url is https://amherstburghomehealth.ca (a health care facility in Amherstburg, Ontario, Canada) This is my first post on Webroot, so please forgive me if I chose the wrong subforum. Thank you.