8.0.1.229 now live

For the CCC item, get a message into Webroot Support and mark it as a FP report. They take care of those very swiftly. Best result is it's an FP and you're good to go in a few hours or less in most cases. Worst case it's got a real virus sneaking in. :\

 

Haven't noticed any CPU usage issues with identity shield disabled yet. Was working normally last night and this morning.

 

Interesting...

So the ID shield silently causes things to not "fail" but actually return nothing at all. Some programs don't handle this very well. They start a thread to do something that technically should just work unless Windows itself is completely broken. Since it should either Just Work or return an error, they don't build in any handling for timing out or what to do if it returns nothing at all. Then the thread just sits and loops. Then a new one at the next instance. And another... And so on. It's technically not WSA's fault, as it's actually sloppy programming on the part of whoever didn't handle the silence in return.

Does your ID shield have anything set to "Block" in the processes list? If so, try setting it to allow. If not, you can try setting browsers to Allow one at a time as well and see what impact that has and which one is having the issue.

 

WSA isnt detecting CCC , the removing problem is making it crash , see the problem with Eicar test ( any sample makes that).

http://i.imgur.com/SjgI3.jpg

 

This could be ATI opening handles to files as they're created. It would be worth writing into support to see if they can get crash dumps from the ATI processes.

Thanks!

 

Could also be a globally-loaded DLL opening handles. Would be weird, but possible. I know because my wife uses an ATI card with CCC and there is zero problem from any test files. So it comes down to determining what is unique about that computer that is causing an issue.