I've been struggling with a user's system via email trying to recover from an incomplete KazaaLite and Kazaa Resurrection removal plus a damaged HOSTS file where 127.0.0.1 localhost as the first entry was non-existent and the first entry was 127.0.0.1 desktop.kazaa.com. That's been straightened out. KazaaBeGone has been run and other things done to complete the removal of Kazaa. The user has been using SpyBot V1.4. The HOSTS file was damaged at the time the user installed SpyBot V1.4. Is there any protection lock in SpyBot that would have picked up 127.0.0.1 desktop.kazaa.com from the HOSTS file and is now making the system think localhost is desktop.kazaa.com? When running X-Netstat, it is showing multiple connections to desktop.kazaa.com and none to localhost.