Does seem like that. For a good test, open a command prompt & ping microsoft i.e "ping www.microsoft.com" It should resolve to something like: 65.55.12.2491 - when I was affected by something last week, all addresses involving microsoft and many anti-virus vendors were being resolved to 127.0.0.1 I got around this by doing a dns lookup on www.microsoft.com, then substituting that ip for any part of the url that was www.microsoft.com (Same with avg and avira, etc) e.g I want www.microsft.com/downloads/somefile.zip www.microsoft.com is being resolved to my loopback address, so I insert the ip that this should resolve to into the address bar --> 65.55.12.2491/downloads/somefile.zip The problem lay in a registry key contained within HKLM/Software/Microsoft/Windows NT/CurrentVersion/Winlogon it was UIShell, or something like that. (it was NOT UIHost, that is a neccessary entry) The key points to an executable file that is run on start-up and proceeds to hide itself from directory searches, as well as hiding the registry key needed to remove it! The solution? Use a program that uses direct registry access - The registry keys can't be hidden then since we're not using the wnidows api Registry calls that the virus has already hooked. You should have a look for GMER - that's all I needed to access and repair the registry (make sure you get a new version from the author's website). Oh, and btw - it wasn't conficker, dunno what it was - AVG reckons that the file is clean :mad: