Shining a Light on the Windows Process Jungle (Part 2)

1 Star2 Stars3 Stars4 Stars5 Stars (3 votes, average: 5.00 out of 5)
Loading ... Loading ...

October 19th, 2011 written by Sandro Villinger in Windows Insights

Last week, I dug deep into Windows  Task Manager and explained the most critical Windows processes, such as “lsass.exe” and “Explorer.exe”. In this second installment, I’m going to explain the more common Windows processes, some of which are important and some of which you can even disable to avoid unusual CPU and hard disk activity.

Seven more common Windows processes

In Windows Task Manager or Process Explorer, you’ll find a handful of entries that don’t say if they’re important or not. Here is a rundown of seven more common ones you may come across.

Alg.exe – the online gateway

Alg.exe (Application Layer Gateway) is part of the Windows firewall and Internet connection-sharing feature in Windows XP. It’s also responsible for handling the secure connection of programs, such as instant messenger clients, Bittorrent, and FTP and other programs that rely on the Internet. Killing this service might also kill your connection and many programs which need to access the web.

Audiodg.exe – all about sound

Behind the cryptic “Windows Audio Device Graph Isolation” description lies a process that helps your PC’s audio driver run in an isolated system area to protect it from changes. If you’re experiencing problems with Audiodg, don’t kill it, instead, follow these steps.

Bttray.exe – your Bluetooth connection

Ever connected a device to your PC via Bluetooth? This process is responsible for the little Bluetooth icon in the tray area of your taskbar.

Never connect anything via Bluetooth? Want to get rid of it? Then just disable Bluetooth support and save a bit of memory and CPU time. Go to your Device Manager, expand the “Bluetooth Radios” section, right-click on all of the listed devices, and select “Disable”.

Then, open up your Start menu, type in “services.msc” and hit ENTER. Double-click on the “Bluetooth Support Service” and select “Disabled” from the drop-down list, where it says “Start type”. Done!

Conhost.exe – the command line host

Conhost.exe is an important Windows process that handles the way the user interface connects to the command line (cmd.exe).This changed drastically with Windows Vista. For probably the most detailed information on why conhost.exe needs to be active, check out this HowToGeeks article.

Chkdsk.exe – your hard disk checker

This process is responsible for the checkup of a local disk, external drive, or plugged-in flash media (such as a USB thumb drive). It should only be active during a scan.

DfrgNtfs.exe/dfrgui.exe – your disk defragmenter

This process handles Windows defragmentation and runs automatically on a schedule. This is why you might see it crop up in Windows Task Manager even when you’re not actively running Disk Defragmentation.

Dwm.exe – your “Aero” interface

On Windows Vista and Windows 7, DWM (Desktop Window Manager) handles the 3D effects of your Aero user interface.

Once disabled, you’ll be looking at the basic Windows user interface.

DWM.exe is quite a resource-heavy process compared to others, especially if you’ve got multiple windows and programs open at the same time. If you’re running Windows Vista or Windows 7 on older machines (before 2005–2006) with just 1 or 1.2 GHz and a low-end (integrated) graphics card, I recommend you turn DWM off. Simply head over to the Service Manager (see the bttray.exe entry above), double-click on “Desktop Windows Manager”, and select “Disabled”.

I’ll shine a light on more important Windows processes in part 3. Stay tuned!

4 Responses to “Shining a Light on the Windows Process Jungle (Part 2)”

Trackbacks/Pingbacks

Comments

  1. > “DWM.exe is quite a resource-heavy process compared to others”

    Is that so? On my computer, it is occupying no more than 15 MB memory. SVCHOST.exe, SearchIndexer.exe and Explorer.exe occupy more memory.

    • Depends on the amount of windows you’re running and your resolution. On my system (10 browsertabs, 9 applications), DWM takes up 133 MB. On another system with no application running, it’s 13 MB.

Leave a commentLogin | Register

*

SDFgvxcvlerRtv
vm-blog02