Click here to Skip to main content
13,251,760 members (88,414 online)
Click here to Skip to main content
Add your own
alternative version


112 bookmarked
Posted 26 Mar 2007

How To: (Almost) Everything In WMI via C# Part 2: Processes

, 19 Oct 2007
Rate this:
Please Sign up or sign in to vote.
A C# Wrapper for WMI Win32_Process Class
Screenshot - WIN32_Process.jpg


This is the second article in the series of articles How To: (Almost) Everything In WMI via C#.

This article focuses on the Win32_Process class within the root\CIMV2 namespace. This library exposes all the properties and methods encapsulated in this namespace to your application (and there are quite a few). Using this library, you can enumerate properties of the processes on your machines, kick off processes, terminate processes, enumerate processes, and gather significant details regarding your processes. The library facilitates running any of these tasks on local or remote workstations.


Please do not send me emails with instructions on how to perform these tasks using .NET native classes. That is not the point of these articles. I'm composing these articles for the purpose of demonstrating how to use WMI within C#.NET with the System.Management namespace. Also note that WMI is a bit slower than the .NET classes so if you have no specific need to use WMI, you should probably be using System.Diagnostics.Process instead.

Using the Attached Code

Methods (Local Machine or Remote Machine)

  • CreateProcess(string processPath) - Starts a process
  • GetProcessOwner(string processName) - Gets the user name of the process owner
  • GetProcessOwnerSID(string processName) - Gets the SID of the process owner
  • ProcessProperties(string processName) - Gets the 60+ property values of the process
  • RunningProcesses() - Gets the names of all the running processes (can be changed)
  • SetPriority(string processName, ProcessPriority.priority priority) - Changes the process priority
  • TerminateProcess(string processName) - Kills the process

Instantiate the Local Provider

//using baileysoft.Wmi.Process; *must include
ProcessLocal processObject = new ProcessLocal(); 

Walkthrough All the Methods

//Get Running Processes
Console.WriteLine("Fetching Running Processes: ");
foreach (string eachProcess in processObject.RunningProcesses())
   Console.WriteLine("Process: " + eachProcess);

//Start Process
string processName = "notepad.exe";
Console.WriteLine("Creating Process: " + processName);

//Change the Priority
Console.WriteLine("Setting Process Priority: Idle");
processObject.SetPriority(processName, ProcessPriority.priority.IDLE);

//Get the Owner of a Process
Console.WriteLine("Process Owner: " + processObject.GetProcessOwner(processName));

//Get the Process Owner's SID
Console.WriteLine("Process Owner SID: " +

//Get a collection of all the Properties of a Process (Memory Usage, etc, etc)
Console.WriteLine("Properties of Process: " + processName);
foreach (string property in processObject.ProcessProperties(processName))

 //Terminate a Process
 Console.WriteLine("Killing Process: " + processName);
 Console.WriteLine("Process Terminated");


Remote System Processes

In order to run the code above against a remote machine, you must instantiate the ProcessRemote class. During this instantiation, you need to either send in explicit credentials or you can send in null values if you're running this on a workstation on a domain, logged in with a domain account with the appropriate permissions to perform these tasks against the remote workstation.

Instantiating the Remote Provider

//using baileysoft.Wmi.Process; *must include
ProcessRemote processObject = 
              new ProcessRemote(userName,

Connecting to a Remote Machine Where You Want to Use The Domain Credentials from the LoggedIn User

ProcessRemote processObject = 
                    new ProcessRemote(null,

Using a Service Account to kick off a Remote Process

ProcessRemote processObject = 
                    new ProcessRemote("neal.bailey",


The WMI (Windows Management Instrumentation) provider is considerably slower than the native .NET classes. At first it may seem pointless to use WMI for process management tasks considering the ease of use of the .NET System.Diagnostics.Process classes, however a lot of developers out there spent a lot of time learning WMI and would like to have it available in their toolbox.


  • Originally submitted on 26th March, 2007


This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


About the Author

Software Developer
United States United States
I'm a typical 30 year old generation X guy that likes video games, NFL football, and comic style art. I have an insatiable passion for programming and doing what ever it takes to become a better programmer.

You may also be interested in...


Comments and Discussions

GeneralMy vote of 5 Pin
homestar8519-Mar-13 1:25
memberhomestar8519-Mar-13 1:25 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

Permalink | Advertise | Privacy | Terms of Use | Mobile
Web01 | 2.8.171114.1 | Last Updated 19 Oct 2007
Article Copyright 2007 by thund3rstruck
Everything else Copyright © CodeProject, 1999-2017
Layout: fixed | fluid