"Scan with Webroot" Always stops working!

No on the current computer that I am seeing this issue I only have 1 user account on it. I always just leave it on my deskop when not in use. Also I do not use sleep mode or hibernate mode. It was working last night when I went to bed and then when I came on the computer this morning "Scan with Webroot" was broken again. The only thing I did was turn off the monitor last night and then tuirn it on this morning.

Sometimes when using my computer I have lots and lots of IE tabs running which does use up a lot of my 4GB's of ram. At the same time I sometimes play some HD video clips among doing others things. Could this issue be because my memory is running low and "Scan with Webroot" can't run?However when the memory is running low I close a lot of programs to lower the memory a lot but when doing this "Scan with webroot" still does not work until I restart the computer or Webroot Secure Anywhere.

The only thing I know for sure is no other item in the right click context menu has ever stopped working besides "Scan with webroot" Not even once.

So what ever the issue is it only affects "Scan with webroot"

I have used a lot of different programs over the years that add an item to the right click context menu and never have I had this kind of issue before.

 

They do! WSALogs. Support issues requests for that. I'd post a link to it here, but I think when I did before, I got scolded (a little) and told that support should ask people for it, so I won't. ^.^

 

Bill Alcorn a Escalation Engineer contacted me by e mail and will be setting up a time hopefully today where he will remote access my computer and try and see whats going on with this issue .

This issue is so stange I restarted my computer this morning and of course the "Scan with webroot" starting working again. So I go away from the computer for maybe 1 hour or so to eat breakfast. then go on a different computer and try running "Scan with webroot" from that computer and of course "Scan with webroot" is not working but I knew that already because that computer was not restarted. So then I go back on the other computer where "Scan with webroot" was working before I had breakfast and now "Scan with webroot" is not working again.

So what in the world could have happend in the hour or so that I was away from the computer?

The only thing I did besides eating breakfast lol was I tried to run "Scan with webroot" from another computer and like I said that was not working either but I already knew that from the night before as I had not restarted it yet to fix it.

Is there any possibility that when I used "Scan with webroot" on one of my computers to scan files on a networked computer could be what is breaking "Scan with webroot"?

It looks like this issue is going to be a hard one to fix.

 

I have been reading this thread since it's conception and now feel that I must comment. I am runnings WSA Essentials on three Win7 x64 systems, and on these three systems, "Scan with Webroot" works flawlessly every single time. I have been trying different folders to scan just to see if I can reproduce the reported problem, and so far, I am unable to do so.

I am commenting on this simply to let casual readers know that while "Scan with Webroot" is apparenly ill on some systems, on other systems it works just fine and dandy...

 

Same here with Win 7 x64!

TH

 

I had Bill Alcorn a Escalation Engineer from Webroot remote access my computer this afternoon. And he got all the info he needed from the logs and he did see that something was crashing and then restarting in the Webroot Secure Anywhere software which is causing the "Scan with Webroot" to not work. But he said the hard part is going to be to figure out why its happening in the first place. Apparently what ever is crashing is restarting however the "Scan with Webroot" remians disabled until I restart either the Secure Anywhere software or the computer.

Bill does seem to think they can fix this by maybe changing some code around in the software or something like.

Bill will keep me updated on this issue and I will let you all know when it has beed fixed