Skip to main content

Recovering from Windows XP virus annihilation

Recently, several members of the family have had their computers "owned" by viruses or spyware. At my house, I'm more focused on prevention but if all else fails, here's a great write up of using Windows XP Recovery features to repair your down and out home computer.

Also, a correspondence with one of my pals (a conversation I've had many times with lots of folks):

---------------------------------------------------------------------

Nope. I think you're on the right path. Good write-up:

Afterwards, I would recommend the following:

1. Set only 1 person within the household as an Administrator...I've found the Mom is usually best. Disable the ability to install software for all other users (i.e. they only belong to Users group)
2. Install virus scanning software; set to update nightly, scan nightly
3. Update Windows with all patches from www.windowsupdate.com. Set Windows to update automatically. Make sure you install SP2
4. Enable the Windows firewall from SP2
5. Download and install the latest Zone Alarm firewall
6. Run a hardware router with a built-in firewall in front of your cable/DSL modem
7. Install and set to run regularly a spyware checker such as Ad-aware
8. If you/they are using a wireless network, use 128-bit WEP encryption with a 13-bit passcode.
9. Enable the pop-up blocker within IE6, Windows SP2
10. Don't use Outlook Express but rather a standard browser for email
11. Don't use file sharing programs
12. Don't use chat programs like AIM or Yahoo messenger without a scanner

Also, from my blog:
http://effectivethoughts.blogspot.com
http://effectivethoughts.blogspot.com/2005/01/preventing-spyware.html
http://effectivethoughts.blogspot.com/2005/03/security-guide-for-smb.html
http://effectivethoughts.blogspot.com/2005/06/avoiding-phishing-attacks.html
http://effectivethoughts.blogspot.com/2005/04/michael-howard-keeping-home-computer.html

Jeff...

On 6/14/05, wrote:

no luck...won't even boot up in Safe Mode...just loops through and says Windows could not start, please choose a mode to boot up in...any option you choose loops back around to same screen. couldn't find his rescue CD to boot from, so I need to order one from HP today. Any other advice? (besides using it as a boat anchor)



-----Original Message-----
From: Jeff Hunsaker [mailto:]
Sent: Tuesday, June 14, 2005 9:19 AM
To:
Subject: WinXP repairs

How did you fare?

--
Jeff Hunsaker

Comments

Popular posts from this blog

Get Your Team Foundation Server Hate On!

[Google ranking skyrockets... ;-)] I'm a big fan of TFS/VSTS. However, there are a good pocket of folks who take issue with the way TFS handles or implements a certain feature. Well this is your chance to vent! I'm planning a presentation around the "Top 10 TFS/VSTS Hates and How to Alleviate Them"...or something along those lines. But I need your help. Post a comment below detailing your dislike. If it's legitimate, I'll highlight it in the presentation and [hopefully] provide an alternative, resolution, or work-around. Thanks in advance! Update 7/19/2008: Version Control and Microsoft

Rollback a Ooops in TFS with TFPT Rollback

Rhut roe, Raggie. You just checked in a merge operation affecting 100's of files in TFS against the wrong branch. Ooops. Well, you can simply roll it back, right? Select the folder in Source Control Explorer and...hey, where's the Rollback? Rollback isn't supported in TFS natively. However, it is supported within the Power Tools leveraging the command-line TFPT.exe utility. It's fairly straightforward to revert back to a previous version--with one caveot. First, download and install the Team Foundation Power Tools 2008 on your workstation. Before proceeding, let's create a workspace dedicated to the rollback. To "true up" the workspace, the rollback operation will peform a Get Latest for every file in your current workspace. This can consume hours (and many GB) with a broad workspace mapping. To work around this, I create a temporary workspace targeted at just the area of source I need to roll back. So let's drill down on our scenario... I'm worki

Installing the .Net Framework 3.0 SP1 on Windows 2003 Server

I'm building an [automated] build server requiring the .Net 2.0 and 3.0 runtime. Unfortunately, at my client, they leverage a proxy server. The standard .Net 3.0 SP1 framework redist is really just a bootstrapper. Logged in as a local admin on the box, I didn't have the opportunity to authenticate the installation EXE with my domain credentials. So, the install kept timing out. Finally, I found this helpful post from Aaron Ruckman on how to download the very elusive, full framework package. It's here , BTW (x86). I finally get the full installation EXE downloaded to a fileshare, re-run the install and wham--" XPSEPSC: XPS must be installed..." Excuse you? This isn't an XPS ...it's a VM. I found a few MSDN posts here and here outlining the problem. I'm still not clear on what XPSEPSC does (Google yielded little) but you can download it here (x86) . After installing XPSEPSC, the framework installed without issue. Update : Somewhat related, there i