Typo there - the file should be wininet.dll and should be in your WINDOWS\system32\dllcache folder. Some web notes: wininet.dll is an essential Windows system file, however, some viruses replace this file with their own version so that they are very hard to detect. I just fixed one of these for a client this morning. You need to replace the file with a genuine copy. I used a copy from one of the other machines on the network but if you can't do that you should be able to find it in the i386 setup folder. The fake version will create other virus/spyware files and put them in startup lists. Make sure you get rid of these too or you'll be back to square one. and: This may help? # Find wininet.dll and rename it to wininet.dl # Wait a few moments. A new, clean version of wininet.dll should appear # Reboot the system and disinfect or delete the infected wininet.dl file http://www.viruslist.com/en/viruses/encyclopedia?virusid=84462 Updating Windows to SP2 if you don't have it will restore a good wininet.dll file. bones -----Original Message----- From: jhb-bounce@xxxxxxxxxxxxx [mailto:jhb-bounce@xxxxxxxxxxxxx] On Behalf Of bones Sent: 30 January 2008 17:10 To: jhb@xxxxxxxxxxxxx Subject: [jhb] Re: Emergency In Ward Ten Wininit.DLL is a core file for IE7 - it sets the locations in the Registry for temp files.. It's a prime target for viruses and I'm surprised your AV software let it get infected. Can't you just copy it from the CD? bones -----Original Message----- From: jhb-bounce@xxxxxxxxxxxxx [mailto:jhb-bounce@xxxxxxxxxxxxx] On Behalf Of Gerry Winskill Sent: 30 January 2008 16:38 To: jhb@xxxxxxxxxxxxx Subject: [jhb] Emergency In Ward Ten I mentioned Virus attacks this morning, after which I set Avast to seek and destroy. It found a Trojan Horse type in the Windows associated locations and I accepted Delete. That was the last I saw of Windows! Windows now fails to boot, with an error message about missing Wininit.dll. I've tried booting with the Windows XP Home Edition CD, after setting BIOS to look for bootup in the CD drive, but that produces the same error message. I've managed to access Thunderbird via the Task Manager, to get in touch with what masquerades as the living world. Any suggestions much appreciated. Gerry Winskill