Bits and Bytes

We’ve all experienced it. That pc you know should be zipping along but isn’t. You add more memory, but it’s still barely chugging. Fortunately, it’s fairly easy to troubleshoot those ailing machines. Here are steps you can take to help your machines run much faster.

Defragment
this one should go without saying. However, I am always surprised at how few people regularly do this — or how many it admins neglect to set up machines to do this regularly. Regardless of which windows desktop os you use, make sure you either manually defragment or set the machine up to automatically defragment. When machines get too fragmented, they suffer serious performance degradation. Usually, the built-in windows defrag tool works fine. If you are looking for something a little better, try defraggler. It can work on a whole disk or just a part of one.

Clean up the disk
have you ever filled up a disk to 100%? If that disk contains both your os and your data files, your machine is going to come to a screeching halt. One of the first things to check on a machine that’s running slowly is how much of the hard disk has been used. If there isn’t roughly 10% of the hard disk free, it’s time to clean house. One of the tools I like is ccleaner. It quickly clears out all temp files for you. Once that’s done, it’s time to attack the obvious locations: recycle bin, pictures, music, and videos. Once you have cleared those out, you can remove old restore points and shadow copies (from system restore) and installed programs from your downloads directory. If that doesn’t clear up enough space, it’s time to start removing unused applications.

Clean up the registry
I’ve seen plenty of machines get bogged down simply because of errors in the registry. Of course, the registry isn’t something just any old user (or administrator) should attack. Instead, you want to use an application whose purpose is to clean up the registry. One of my favorite tools for that task is, again, ccleaner. When you run ccleaner, make sure you back up your registry (it will prompt you to do this). Then, run it a few times. The first time through, it won’t catch all the errors. It usually takes about three times before all errors are removed. Once you’ve removed those errors, you might want to reboot to ensure the process is complete (and the machine is back to speed).

Remove spyware/malware
this one always shocks me. If you are using a windows operating system you better have anti-malware on board or your machine is sure to get bogged down in the muck and mire of spyware. I tend to lean toward malwarebytes for this. But don’t just use the free version. It’s good, but it doesn’t include any sort of scheduler. And we know end users are horrible about running maintenance applications. For this, you will want to spend the money to make sure your anti-spyware is up to date and running on a schedule.

Check the disk for errors
With a machine that’s aging or whose hard drive has seen excessive use, sectors on that drive can wind up bad. To remedy this, you’ll need to issue a command and reboot your machine. The command i generally use is chkdsk x: /f /r (where x is the drive letter you want to check). The f switch tells the command to automatically fix errors and the r switch locates bad sectors and recovers readable data.

Check what’s running at start-up.
You can use the built in microsoft configuration utility (start->run-> msconfig), or a third party tool, like ccleaner already mentioned. Get rid of those things that run automatically that you don’t need, such as quicktime, adobe acrobat, instant messengers. They don’t have to run at startup, since you only need them running when you are actually using them.

Restart the computer.
So often, when we get these calls for a slow machine, the user hasn’t restarted in 3-4 weeks. Not restarting regularly can leave old processes hanging in memory, using up resources, thereby slowing your system. A restart will clear all of that out.