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.


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:

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.


Popular posts from this blog

Recreating a missing VMFS datastore partition in VMware vSphere 5.x and 6.x

    Symptoms A datastore has become inaccessible. A VMFS partition table is missing.   Purpose The partition table is required only during a rescan. This means that the datastore may become inaccessible on a host during a rescan if the VMFS partition was deleted after the last rescan. The partition table is physically located on the LUN, so all vSphere hosts that have access to this LUN can see the change has taken place. However, only the hosts that do a rescan will be affected.   This article provides information on: Determining whether this is the same problem Resolving the problem   Cause This issue occurs because the VMFS partition can be deleted by deleting the datastore from the vSphere Client. This is prevented by the software, if the datastore is in use. It can also happen if a physical server has access to the LUN on the SAN and does an install, for example.   Resolution To resolve this issue: Run the  partedUtil  command on the host with the issues and verify if your output

ما هى ال FSMO Roles

  بأختصار ال FSMO Roles هى اختصار ل Flexible Single Operation Master و هى عباره عن 5 Roles فى ال Active Directory و هما بينقسموا لقسمين A - Forest Roles 1- Schema Master Role و هى ال Role اللى بتتحكم فى ال schema و بيكون فى Schema Master Role واحد فى ال Forest بيكون موجود على Domain Controller و بيتم التحكم فيها من خلال ال Active Directory Schema Snap in in MMC بس بعد ما يتعمل Schema Register بواسطه الامر التالى من ال Cmd regsvr32 schmmgmt.dll 2-Domin Naming Master و هى ال Role المسئوله عن تسميه ال Domains و بتتأكد ان مفيش 2 Domain ليهم نفس الاسم فى ال Forest و بيتم التحكم فيها من خلال ال Active Directory Domains & Trusts B- Domain Roles 1-PDC Emulator و هى ال Role اللى بتتحكم فى ال Password change فى ال domain و بتتحكم فى ال time synchronization و هى تعتبر المكان الافتراضى لل GPO's و هى تعتبر Domain Role مش زى الاتنين الاولانيين و بيتم التحكم فيها من خلال ال Active directory Users & Computers عن طريق عمل كليك يمين على اسم الدومين و نختار operations master فى تاب ال PDC Emu

Unlock the VMware VM vmdk file

  Unlock the VMware VM vmdk file Kill -9 PID Sometimes a file or set of files in a VMFS become locked and any attempts to edit them or delete will give a device or resource busy error, even though the vm associated with the files is not running. If the vm is running then you would need to stop the vm to manipulate the files. If you know that the vm is stopped then you need to find the ESX server that has the files locked and then stop the process that is locking the file(s). 1. Logon to the ESX host where the VM was last known to be running. 2.  vmkfstools -D /vmfs/volumes/path/to/file  to dump information on the file into /var/log/vmkernel 3.  less /var/log/vmkernel  and scroll to the bottom, you will see output like below: a. Nov 29 15:49:17 vm22 vmkernel: 2:00:15:18.435 cpu6:1038)FS3: 130: <START vmware-16.log> b. Nov 29 15:49:17 vm22 vmkernel: 2:00:15:18.435 cpu6:1038)Lock [type 10c00001 offset 30439424 v 21, hb offset 4154368 c. Nov 29 15:49:17 vm22 vmkernel: gen 664