NoVirusThanks Process Lister is a sort-of task manager which displays running processes, their key data, and provides various ways to manipulate them.

The program opens with a familiar list of processes and their details: PID, name, session, command line, 32/ 64-bit, parent PID/ process/ command line, description, company, signer, user/ domain and more.

The display scores highly for detail, but fails in several other ways. You can't display processes as a tree; you can't click a column header to sort by that field; you can't hide a particular column; you can't reorder columns; the process name is displayed as a full path, which means you often can't see the executable name.

Right-clicking a process displays multiple options. Some are familiar - Properties, Open Containing Folder, Terminate - but there's more. You're able to suspend and resume a process, terminate and delete it on reboot, view a file hash, dump process memory, inject a module, or view associated windows, handles or modules.

These functions are more interesting, but we still noticed problems. Choosing the "List Object Handles" option displayed absolutely nothing for every process we tried.

Process Lister also includes a Tools menu with a host of bonus extras. "Search Handle" and "Search DLL" should allow you to locate open objects or loaded files; File Hasher calculates various hashes for the files you specify; Dos Device Inspector displays Dos Device names and their path (\Device\Video0); Driver Loader and Unloader allows manually loading or unloading kernel drivers; Raw File Copy copies a file using direct disk access, which means it works even if the file is locked or you don't have the security rights to access it; IPv4 blocker enables blocking specific IP addresses; System Restore Point creates a restore point; and there are simple displays of page files, loaded kernel modules, running services and basic system information.

While this sounds great, the individual modules are often very basic, and we found the "Search Handle" option didn't work at all (maybe the same issue as the "List Object Handles" dialog).

The dialogs were modal, too. Once we opened the Running Services list, for instance, we couldn't do anything else in the program until we closed it again. Lame? Yes. It surely is.