v5.0.0.174 - cannot complete scans

[ruscitto]

I have v5.0.0.174 which is no better that the previous version 5. I have yet to complete one full scan. Every time I get to Current Scanner: Hosts Scanner it freezes on something called 127.0.0.1.

I have searched my system for 127.0.0.1 and can't find it. A google search tells me that 127.0.0.1 is the standard IP address used for a loopback network connection and that if you try to connect to 127.0.0.1, you are immediately looped back to your own machine.

What the hell does all that mean and how do I stop it so I can complete a scan?

[Bubbba1]

Originally Posted by ruscitto

I have v5.0.0.174 which is no better that the previous version 5. I have yet to complete one full scan. Every time I get to Current Scanner: Hosts Scanner it freezes on something called 127.0.0.1.

I must disagree. Version5.174 is light years ahead of the previous. What you describe above is exactly what I too experienced after v5.174 install. In my case, Avira's suite is configured to "lock" the hosts file. From the SD main screen, click "OnGuard", then click "Network Guard". Ensure that "Host File Protection" is NOT checked. Try that. You too may have another security program that is already monitoring the hosts file for you. Currently, along with the AntiVir suite, I have SuperAntiSpyware Pro, BoClean AND WinPatrol all running with SDv5.174 ... all resident and playing nice with one-another.

I have searched my system for 127.0.0.1 and can't find it.

No, 127.0.0.1 *IS* your system. Don't expend additional effort trying to find it. Please let me know if the above instruction allows you to complete any scan.

[tom.tdw]

Originally Posted by ruscitto

I have v5.0.0.174 which is no better that the previous version 5. I have yet to complete one full scan. Every time I get to Current Scanner: Hosts Scanner it freezes on something called 127.0.0.1.

I have searched my system for 127.0.0.1 and can't find it. A google search tells me that 127.0.0.1 is the standard IP address used for a loopback network connection and that if you try to connect to 127.0.0.1, you are immediately looped back to your own machine.

What the hell does all that mean and how do I stop it so I can complete a scan?

if that does not work try adding 127.0.0.1 to you global exceptions list

[ruscitto]

Hey Bubbba1, many thanks. I tried your suggestion of not checking the "Host File Protection" and I successfully completed a full scan with no problems at all.

Many thanks.

[Bubbba1]

You bet. Glad it worked for you.