How Windows Priority Classes Work

Every Windows process has a priority class. It sets the base priority of the process’s threads, and the scheduler always runs the highest-priority thread that is ready to run. Priority only matters when threads compete for the same CPU: If a core is free, a Normal thread runs just as fast as a High one.

The Six Priority Classes

Windows schedules threads on priority levels from 0 to 31. The class sets a thread’s base level, and each thread can sit a few levels above or below it with its own thread priority.

ClassBase LevelNotes
Idle4Runs when nothing else needs the CPU. Suits work that can wait.
Below Normal6Good for background work you still want to finish, like an encode or a backup.
Normal8The default for almost every process.
Above Normal10A small step ahead of Normal.
High13Ahead of all ordinary software. Windows uses it for a few system processes, such as the Desktop Window Manager.
Real-time24Ahead of many system threads, including some that handle mouse and keyboard input. Needs administrator rights; without them, Windows sets High instead.

How Windows Adjusts Priorities on Its Own

  • Temporary boosts: Threads in the Idle to High classes get short priority boosts, for example when they receive input, finish waiting on I/O, or belong to the foreground window. Real-time threads never get boosts.
  • Starvation relief: A ready thread that hasn’t run for about four seconds is boosted briefly, so a low priority slows a process down but doesn’t stop it completely.
  • Inheritance: A new process starts at Normal, unless the process that started it is Idle or Below Normal; then it gets the same class.

Lower Background Work Instead of Raising Everything Else

Raising a program’s priority helps only while something else is competing with it, and it pushes that program ahead of parts of Windows too. Lowering the priority of the background work does the same job with less risk: The program you are using wins the CPU, and nothing important is pushed aside. If several programs are raised to High, none of them gains anything over the others.

Avoid Real-time for ordinary programs. A busy Real-time process can starve input handling and drivers, and the PC can stop responding until it finishes.

This is also how Process Lasso’s ProBalance works: When a background process takes too much CPU, it lowers that process’s priority for a moment, then restores it.

How to Change a Priority Class

  • Process Lasso: Right-click a process and choose CPU Priority > Always to set a rule that applies every time the process starts, or CPU Priority > Current to change only the running instance. Options > CPU > CPU Priorities lists every rule. For processes Process Lasso can’t change, such as games protected by anti-cheat, Enforce by Windows Registry has Windows apply the priority at start-up. See Priorities in the documentation, which also covers I/O, memory and GPU priorities. For what GPU priority classes actually change, see GPU Priorities.
  • Task Manager: On the Details tab, right-click the process and choose Set priority. The change lasts only until the process exits.
  • The command line: start /belownormal program.exe starts a program in that class. The other switches are /low (Idle), /normal, /abovenormal, /high and /realtime.

Priority decides who goes first; it doesn’t decide where a process runs. To keep a process on particular cores, see Using Process Lasso to Manage CPU Affinities.

Bitsum Technologies

Independent Windows software since 2002. We build novel solutions to software performance and automation challenges.