Re: Does clean install of XP kill all malware?




"Zadig Galbaras" <tresfjording@xxxxxxxxx> wrote in message
news:dbielc$3d2$1@xxxxxxxxxxxxxxxxx
> Sorry Kerry but the computer was not, I repeat not, connected to the
> internet.
> This OS was Win2000.
> I reinstalled three times, and at the last try I did a format of the
> harddisk. The virus persisted.
> I am no expert, but after three clean installation of an OS I thought any
> virus was gone.
>
> I then learned that this version of the virus only infected Win2000
> computers.
> Therefore I, in the early morning hours, begat a clean install of my
> private WinXP, and then a clean install of Win2k.
> That made the virus go away.
>
> All this with no connection to the web!
> I do not connect to the web before an updated viruskiller service is
> established and working.


There you go. No mention of a firewall. You must install a firewall before
connecting to the Internet. A viruskiller service won't protect against
Sasser. Windows 2000 has no built in firewall. A third party firewall must
be installed.

How do you connect to the Internet? If it is via a network connection the
cable must be physically unplugged while installing. It is possible for a
virus to survive a format. I have not seen any versions of Sasser that
infect the boot sector but it's certainly possible. A format won't help you
with a boot sector virus. You must overwrite track 0. Most hard drive
manufacturers have a utility to do this.

Kerry



> --
>
> Regards
> Zadig Galbaras
> A Perturbed Norwegian Agnostic
> -----
>
>
> "Kerry Brown" <kerry@xxxxxxxxxxxxxxxxxxx*a*m> skrev i melding
> news:u5UkAt%23iFHA.3704@xxxxxxxxxxxxxxxxxxxxxxx
>> "Zadig Galbaras" <tresfjording@xxxxxxxxx> wrote in message
>> news:dbhauo$koi$1@xxxxxxxxxxxxxxxxx
>>> No, some viruses like the Sasser will still prevail after a clean
>>> install.
>>> That I have experienced myself.
>>>
>>> The sasser virus was still there after an clean install with a manual
>>> formatting of the harddisk.
>>>
>>> So a clean install do not necessary take away all viruses.
>>>
>>
>> Sasser did not survive a clean install. What happened was you were
>> reinfected as soon as you connected to the Internet. Sasser is a worm
>> that looks for vulnerable computers on the Internet. The maximum time
>> before infection of an unprotected computer connected to the Internet is
>> around four minutes. Usually you will be infected before Windows is
>> installed if you are connected during the install. You must install SP2
>> or a firewall before connecting to the Internet or any network.
>>
>> Kerry
>
>


.



Relevant Pages

  • Re: Firewall and IP forwarding
    ... But how then I suppose to test connectivity through future FireWall computer ... before I install NAT comming with this FireWall? ... > You cannot route private addresses through the Internet. ... >> interface of FW machine to test the connection from inner LAN to the ...
    (microsoft.public.windows.server.networking)
  • Re: Internet connection lost after 5 min.
    ... before going to the Internet again. ... Enable or Disable Internet Connection Firewall in Windows XP ... Until you can decided what AV you might want, download and install the free ... Regsvr32 Wintrust.dll ...
    (microsoft.public.windows.inetexplorer.ie6.browser)
  • Re: Reformat and reinstallation
    ... commencing the reinstall of XP. ... setup portion of the install. ... included, before you connect to the internet, enable the Internet Connection ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Modem dialing constantly
    ... They are networked through a hub with internet ... >connection sharing installed. ... Install and run HijackThis. ... spyware builds itself into the network software, and its removal may damage your ...
    (microsoft.public.windowsxp.network_web)
  • Re: FIX for ZoneAlarm & KB951748 issue released
    ... "no internet connection available, do you want to work offline or retry." ... My wireless connection doesn't ... I will also install the updates. ... Did you or did you not install WinXP SP3 on or after 08 July 2008? ...
    (microsoft.public.security)