@ wrote:

I don't understand the methodology employed.  I am warned of an infection but then a scan must happen.   Scans, removal, then re-scans run as long as 45 minutes on my  Dell Windows XP machine.  Why isn't the infection killed while inbound if Webroot knows that an infection is present???            v,t,y      C H J

Hello sonofleon,

 

Welcome to the Webroot community.

 

Can you please start a Support Ticket so we can take a look at the case through our support department?

 

Thanks,

John A.

Frontline Engineer

Webroot Support

---

I dont have the full details of your PC but there are a number of reasons why

 

1) File may have been inactive on your PC before Webroot was installed. When it attempted to run it was caught

2) WSA has to rescan in order to verify that the file was succesfully removed

3) The file may be user added file so it unknown on the PC until the user changed the local determination

4) The file may have been unknown in our database but then was classified as bad. Then it gets removed.

---

@ wrote:

I dont have the full details of your PC but there are a number of reasons why

 

1) File may have been inactive on your PC before Webroot was installed. When it attempted to run it was caught

2) WSA has to rescan in order to verify that the file was succesfully removed

3) The file may be user added file so it unknown on the PC until the user changed the local determination

4) The file may have been unknown in our database but then was classified as bad. Then it gets removed.

Another reason is that we are blocking the child that is getting dropped but haven't found the parent. This is my original thought but would have to look at the PC for more details.

 

Thanks,

John A.

Frontline Engineer

Webroot Support

---