Skip to main content

How to use ISO images of Linux to remove a Windows virus.

 

How to use ISO images of Linux to remove a Windows virus.

Source http://www.linuxforums.org/articles/...unix-_733.html


How to use ISO images of Linux to remove a Windows virus.

Every time I get asked to remove a virus from a panicked Windows users computer, I think it will be the last. I continue to be wrong, and I see the same viruses appear over and over again on different computers. Since my days in PC boot camp, new technologies have changed the way I remedy a Windows virus. This is how I eradicate those stubborn viruses on todays Windows machines.
First, I Google the Windows virus message and write down the virus details and files associated with the virus.

Second, I insert a bootable Puppy Linux CD into the machine and power on and boot into Puppy. I then use file manager in Puppy Linux to navigate the hard drive of the effected computer, locate the virus files and delete the offending virus files (from the notes I took above during my Google search). I remove the Puppy CD and reboot back into Windows. This works EVERY time.

To create a Puppy Linux CD you need to download an ISO image from the Puppy site and burn a bootable CD. If you run an Ubuntu operating system you will find this the easiest way to make a bootable CD, you simply right mouse click on the ISO image once it is on your hard drive and select make CD. For creating a bootable CD in Windows youll need to read your CD Burning software instructions as they all do it differently.

A bootable Puppy Linux CD allows me to mount the windows drive in Unix, open a unix based file manager, find and delete the virus executable files (.exe). (identified in my Google research on the virus)

In my experience infected Windows computers ALWAYS have outdated virus software (AVG is good and free), have not received regular windows updates from Microsoft and have Microsoft Defender either disabled or not installed. Those are the three keys to healthy Windows laptops and PCs: Anti-Virus (AVG is free), MS Updates (enable auto-update, its free) and Microsoft Defender (Free). After I delete the virus files it can take another 60-90 minutes todownload and install all of the updates.

I realize that these instructions are geared for someone who has spent some time with different flavors of Unix, but with Puppy Linux you don't have to be a Linux genius. In fact once you boot into Puppy you will notice it looks a lot like any Windows system you have ever used. I have had computer novices use Puppy to grab a web browser and balance their check book on-line during lunch break.

As an IT Professional I keep the Puppy Linux CD in a safe location so I always have it ready when the next panicked Windows user calls me because they are missing deadline due to a virus that has crippled their computer.

To fix broken Windows use Unix. Puppy Linux (and Google) is all you need!

To be fair to the hard working Linux distribution community, you can achieve the same results with any one of at least eight different Linux distributionsClick here for more cool Linux options and reviews

And for the smallest of all Linux distributions:

Dont forget BasicLinux:
http://distro.ibiblio.org/pub/linux/...ions/baslinux/

Download is 2.8 megs and runs on 386 in 3 megs of Ram. Thats what powers the OSULRC-1 with a touch screen, Stylistic, Fujitsu 1000, booting to a pcmcia hard drive.
http://osulrc.com

Comments

Popular posts from this blog

Integration with vCloud Director failing after NSXT upgrade to 4.1.2.0 certificate expired

  Issue Clarification: after upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Issue Verification: after Upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Root Cause Identification: >>we confirmed the issue to be related to the below KB NSX alarms indicating certificates have expired or are expiring (94898)   Root Cause Justification:   There are two main factors that can contribute to this behaviour: NSX Managers have many certificates for internal services. In version NSX 3.2.1, Cluster Boot Manager (CBM) service certificates were incorrectly given a validity period of 825 days instead of 100 years. This was corrected to 100 years in NSX 3.2.3. However any environment originally installed on NSX 3.2.1 will have the internal CBM Corfu certs expire after 825 regardless of upgrade to the fixed version or not. On NSX-T 3.2.x interna...

Calculate how much data can be transferred in 24 hours based on link speed in data center

  In case you are planning for migration via DIA or IPVPN link and as example you have 200Mb stable speed so you could calculate using the below formula. (( 200Mb /8)x60x60x24) /1024/1024 = 2TB /per day In case you have different speed you could replace the 200Mb by any rate to calculate as example below. (( 5 00Mb /8)x60x60x24) /1024/1024 =  5.15TB  /per day So approximate each 100Mb would allow around 1TB per day.

Device expanded/shrank messages are reported in the VMkernel log for VMFS-5

    Symptoms A VMFS-5 datastore is no longer visible in vSphere 5 datastores view. A VMFS-5 datastore is no longer mounted in the vSphere 5 datastores view. In the  /var/log/vmkernel.log  file, you see an entry similar to: .. cpu1:44722)WARNING: LVM: 2884: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device shrank (actual size 18424453 blocks, stored size 18424507 blocks) A VMFS-5 datastore is mounted in the vSphere 5 datastores view, but in the  /var/log/vmkernel.log  file you see an entry similar to: .. cpu0:44828)LVM: 2891: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device expanded (actual size 18424506 blocks, stored size 18422953 blocks)   Purpose This article provides steps to correct the VMFS-5 partition table entry using  partedUtil . For more information see  Using the partedUtil command line utility on ESX and ESXi (1036609) .   Cause The device size discrepancy is caused by an incorrect ending sector for the VMFS-5 partition on the ...