Changing Windows process priority via command line

Question

I want to change Windows process priority via command line.

How can I do that?

Answer 1

The command line syntax:

wmic process where name="AppName" CALL setpriority ProcessIDLevel

Example:

wmic process where name="calc.exe" CALL setpriority 32768

or

wmic process where name="calc.exe" CALL setpriority "above normal"

Priority:

• idle: 64 (or "idle")
• below normal: 16384 (or "below normal")
• normal: 32 (or "normal")
• above normal: 32768 (or "above normal")
• high priority: 128 (or "high priority")
• real time: 256 (or "realtime")

Answer 2

A small addition.

You can also use string values instead of integers (easier to memorize) like that:

 wmic process where name="calc.exe" CALL setpriority "idle"

Possible values: "idle", "low", "below normal", "normal", "above normal", "high priority", "realtime"

PS. Don't forget the quotes, especially if using multiple words in a string value

Answer 3

From batch command line I would simply use PowerShell. This example starts calc.exe, finds its process and adjusts its priority class to "IDLE", aka LOW:

start /b /wait powershell.exe -command "calc.exe;$prog = Get-Process -Name calc;$prog.PriorityClass = [System.Diagnostics.ProcessPriorityClass]::IDLE"

Specify one of the following enumeration values: "Normal, Idle, High, RealTime, BelowNormal, AboveNormal"

Here is the same thing from PowerShell with split lines:

calc.exe
$prog = Get-Process -Name calc
$prog.PriorityClass = [System.Diagnostics.ProcessPriorityClass]::IDLE

Answer 4

In addition to existing answers, the question Windows Equivalent of 'nice' lists some more solutions:

1. Using the command START in the command-prompt (CMD).
2. Using the free ProcessTamer to set up a rule on the .exe that is automatically enforced whenever that process is started.
3. Using a PowerShell script contained here.
4. Using a VBScript script contained here.

Additionally, the old SetPriority utility might still work, but I haven't tried it for many years now.

Some of these solutions may not work on system services or may need to be Run as Administrator.

Answer 5

I am running Windows 7 64-bit.

The wmic command is not reliable. In my considerable experience, it fails unexpectedly for too many (mostly inexplicable) reasons.

The best possible command, because of its reliability, is the START command. The syntax is very simple (this is the 3-line run command for a batch file):

::  Boost thread priority
SET command=<program.exe> <options>
start "" /REALTIME /B /W  %command%

In my opinion its high degree of reliability stems from the fact that it sets the priority level with which the .exe program is launched, rather than trying to meddle with priority after the program has begun running with a different priority.

Answer 6

https://sites.google.com/site/prioclick

Fixed priorities and automatic controls.