Changing process priority can help an important foreground task stay responsive while the system is busy. Think a video encode you need finished, a large compile, a workstation application processing a time-sensitive job, or a browser tab hosting a critical web app. But it cannot create CPU capacity that is not there, cure a memory shortage, speed up a slow drive, or turn a poorly behaved application into a model citizen.
The safe approach is simple: raise one application modestly, observe the result, and put it back when the job is done.
Microsoft Defender: No threats detected
Scan details
What process priority actually changes
Windows schedules individual threads—not simply whole applications—for processor time. A process priority class influences the baseline priority of the threads inside that program. When multiple runnable tasks compete for CPU time, higher-priority work is generally scheduled ahead of lower-priority work.
Microsoft’s Windows scheduling documentation identifies these process priority classes:
| Task Manager option | Practical meaning |
|---|---|
| Low | Runs only when the PC has spare processing time; suitable for non-urgent background work. |
| Below normal | Gives an app less scheduling preference than ordinary software. |
| Normal | The default for most desktop applications. |
| Above normal | A modest boost over ordinary apps; usually the first setting worth trying. |
| High | A strong boost that can noticeably reduce the responsiveness of other software. |
| Real time | The highest class; can preempt important Windows work and should normally be avoided. |
The key word is scheduling. Priority affects who gets CPU time first when there is contention. If the app is waiting on storage, the network, a remote server, GPU rendering, or its own internal bottleneck, raising CPU priority may do little or nothing.
In other words: this is a traffic signal, not an engine swap.
Before you change anything
A few sensible guardrails will save you from turning a minor slowdown into a desktop that feels like it has wandered into a swamp.
- Change priority only for an application you recognize and intentionally started.
- Avoid altering Windows processes, security software, driver-related services, or anything with an unfamiliar name.
- Start with Above normal, not High.
- Treat the change as temporary troubleshooting or workload management.
- Save work in the application before experimenting, particularly if it is already unstable.
Task Manager’s priority setting applies to the currently running process. When that process closes, the setting is gone with it. If the app has several related processes—common with browsers, development tools, launchers, and modern desktop apps—you must identify the process doing the actual work. Raising the priority of a helper process may achieve precisely nothing, apart from providing an exciting new mystery.
Set an app’s CPU priority in Task Manager
These steps apply to Windows 11 and Windows 10.
- Open the application first.
Start the program whose responsiveness or processing job you want to improve. - Open Task Manager.
Press Ctrl + Shift + Esc.
Alternatively, right-click the Start button and choose Task Manager. - Find the app under Processes.
In Windows 11, use the left navigation pane to select Processes if it is not already open. In Windows 10, select the Processes tab. - Jump to the executable in Details.
Right-click the application and select Go to details. This takes you to the underlying process in the Details tab—the place where Windows exposes the priority control. - Set the priority.
Right-click the highlighted process, select Set priority, then choose one of these:- Above normal for a restrained, sensible boost
- High only for a short, genuinely time-sensitive task
- Below normal or Low when you want a background job to get out of the way
- Confirm the warning.
Windows will ask you to confirm the change. Read the warning and select Change priority only if you are certain you selected the correct process. - Test the workload.
Return to the app and see whether it has become more responsive. Also check whether the rest of Windows remains usable.
That is the whole trick. No registry edit, no “PC optimizer,” no downloadable miracle tonic in a suspiciously neon button.
Which setting should you choose?
For most people, the choice should be boring—and boring is good in performance tuning.
Best default: Above normal
Use Above normal when one application needs a little more attention during a busy period. It is the most reasonable first step for:
- A time-sensitive compile or local build
- A large archive extraction
- Video, audio, or image rendering
- A business application calculating a report
- A browser or remote-desktop session needed for active work
This setting does not guarantee a speed increase, but it is less likely than High to make other apps, background services, or Windows itself feel neglected.
Use High only briefly and deliberately
High is not a general “performance mode.” Microsoft warns that high-priority CPU-bound processes can consume nearly all available processor cycles, reducing the time available to normal and idle-priority work.
That can be acceptable if you understand the workload and need the task to finish or respond promptly. For example, an IT administrator may temporarily prioritize a local deployment task on a dedicated workstation. But on a PC that must remain interactive, High can make the rest of the experience distinctly less charming.
If the app does not improve at Above normal, jumping straight to High is not automatically the answer. The constraint might be RAM, disk throughput, a cloud service, an overloaded server, thermal throttling, or software that simply cannot use additional CPU time effectively.
Lower priority for the noisy background jobs
Below normal and Low are valuable when the goal is protecting the rest of the PC from an unimportant but hungry task.
Examples include:
- A long file compression job
- A secondary video transcode
- A non-urgent local scan
- Batch image conversion
- Data processing that can take its sweet time
Lowering a batch job’s priority can preserve responsiveness for the app you are actively using. This is often a better strategy than repeatedly boosting everything else. If every process is declared important, Windows has merely been handed a seating chart with no chairs.
Why Real time priority is a bad idea
Avoid Real time priority for ordinary desktop applications.
This label is dangerously flattering. It does not mean “extra smooth,” “ultra performance,” or “the good kind of fast.” In Windows scheduling terms, a real-time process can take precedence over virtually all normal system activity, including work related to input and background disk operations.
Microsoft’s documentation specifically cautions that a real-time process running for more than a very short time can leave the mouse unresponsive or prevent disk caches from flushing promptly. That is not a productivity feature. That is a very efficient route to regretting a click.
Real-time priority exists for specialized scenarios, such as carefully designed hardware-facing or soft real-time workloads. Those uses involve application design, controlled hardware conditions, and typically more planning than a right-click in Task Manager. For normal apps on Windows 10 or Windows 11, leave it alone.
How to undo the priority change
To restore the default behavior while the app is still running:
- Open Task Manager with Ctrl + Shift + Esc.
- Go to Details.
- Locate the process.
- Right-click it and choose Set priority.
- Select Normal.
- Confirm the change.
You can also close the application completely and start it again. Since the setting was applied to that running process, a newly launched instance normally starts with its usual priority behavior.
If Task Manager will not let you change it
Occasionally, Windows may deny a priority change. Common explanations include:
- The process belongs to another user account.
- The software is running with elevated permissions while Task Manager is not.
- The process is protected or managed by Windows.
- You selected a service, system component, or security-sensitive process that Windows does not want casually reconfigured.
Do not respond by blindly changing random system processes or disabling protections. If the target is a work-managed application, an enterprise endpoint may have policy or security controls that limit process management by design.
For a normal desktop application, first verify that you selected the correct executable. The Details tab shows the actual process name, which is often more revealing than the friendlier label shown in the Processes view.
When process priority is the wrong tool
If performance remains poor after a modest Above normal adjustment, inspect the actual bottleneck rather than escalating the priority war.
In Task Manager, look at:
- CPU: Is the processor already near 100% utilization?
- Memory: Is available memory low, or is Windows heavily paging?
- Disk: Is storage activity saturated, particularly on an older hard drive?
- GPU: Is the app limited by graphics or hardware acceleration?
- Network: Is the application waiting on downloads, a VPN, or a remote service?
A priority change may help an interactive task contend with other CPU-heavy software. It will not fix a laptop running hot and throttling, a nearly full system drive, inadequate RAM, or an application stalled on a network request.
For related Windows performance troubleshooting, useful next stops include Task Manager’s Performance and App history views, Startup app management, storage-health checks, and reviewing Windows 11 updates or Windows 10 updates for known reliability fixes.
The practical rule
Use Above normal for a short-lived, important task; restore Normal afterward. Use Below normal or Low to keep background work polite. Reserve High for narrowly understood jobs, and leave Real time for specialized software that was designed—and tested—to use it.
Task Manager gives Windows users a sharp tool. Used carefully, it can make a busy PC feel more responsive exactly when it matters. Used recklessly, it can make the operating system compete with itself like a band where every musician has decided to play the solo at once.