How to fix high CPU usage by Conhost.exe (Console Window Host)?

Console Window Host (conhost.exe) is the Windows process that serves every command-line program. When it uses a lot of CPU, it is almost always working for another app: a script, a console window full of scrolling text or a background helper of a driver tool. Find that parent app first, then close, update or remove it.

Facts checked on 15 October 2026. Steps written for Windows 11 (25H2 and 26H2) and Windows 10 22H2, with the role of conhost.exe read from Microsoft's Windows Console documentation.

What Console Window Host (conhost.exe) is and why it shows up in Task Manager

Console Window Host, file name conhost.exe, is a built-in part of Windows. Microsoft's console documentation describes it as both the server for all of the Windows Console APIs and the classic window that shows command-line programs. Those programs, such as cmd.exe, PowerShell, scripts and many small helper tools, do not draw their own window: they hand their text to conhost.exe, and conhost.exe answers their console calls and shows the result.

This is why Console Window Host appears in Task Manager even when you did not open a command prompt. Drivers, game launchers and peripheral tools often run small console helpers in the background, and each one gets its own conhost.exe. With Windows Terminal, the window itself is drawn by the terminal, but conhost.exe still runs behind it to translate the program's console calls.

Why Console Window Host uses high CPU, from most to least common

Most often the console app behind it is busy: a command or script prints a flood of text, or a helper loops. Less often a background helper of a driver or peripheral tool keeps restarting, or a scheduled task starts a console program again and again. Rarely the file is a fake copy, or Windows system files are damaged. Microsoft publishes no statistics, so this order comes from how conhost.exe works and from user reports we read.

How to fix Console Window Host (conhost.exe) high CPU usage

Fix 1 takes three minutes and tells you which program the busy conhost.exe works for. Fix 2 to Fix 5 deal with that program and solve most cases. Fix 6 is the check for a fake copy. Fix 7 and Fix 8 are the general repairs for when no parent stands out.

Fix 1. Find which program the busy conhost.exe is working for

3 minutesNo riskEveryone, before changing anything. It tells you which program to deal with and shows the file path for the check in Fix 6.

conhost.exe only does what its console program asks. Task Manager does not show the parent of a process, so a short PowerShell command lists every conhost.exe with its CPU time, its own path and the path of the program that started it.

1. Press Ctrl + Shift + Esc to open Task Manager. On Windows 10, select More details if you see a short list.
2. On the Processes tab, select the CPU column header so the busiest process is on top.
3. If Console Window Host sits under an app group, expand that group: the app's name is the parent. If it stands alone under Background processes, go on.
4. Open the Details tab and note the PID of the busy conhost.exe.
5. Right-click Start, select Terminal (Admin) on Windows 11 or Windows PowerShell (Admin) on Windows 10.
6. Paste the command below and press Enter.
7. Find the PID you noted. The Parent column names the program behind it; CPU is its total CPU time in seconds.

PowerShell (administrator)

Get-CimInstance Win32_Process -Filter "Name='conhost.exe'" | Select-Object ProcessId, @{n='CPU';e={[int](Get-Process -Id $_.ProcessId -ErrorAction SilentlyContinue).CPU}}, ExecutablePath, @{n='Parent';e={(Get-Process -Id $_.ParentProcessId -ErrorAction SilentlyContinue).Path}} | Sort-Object CPU -Descending | Format-Table -AutoSize

Fix 2. Close the console window or stop the command that floods it with text

2 minutesLow riskFix 1 shows cmd.exe, PowerShell or a tool with a visible window, or you left a command, log or server running.

Every line a console program prints passes through conhost.exe. A command that prints thousands of lines a second, or a window that keeps a very long history, keeps conhost.exe busy for as long as it runs. Stopping the command ends the work.

1. Switch to the console window. Look at what it is doing: text scrolling fast, a progress bar, a server log.
2. If the work is not needed, press Ctrl + C to stop the command, then type exit and press Enter.
3. If the work is needed, let it finish, or run it with its output sent to a file instead of the screen, for example yourcommand > log.txt.
4. If the window does not respond, open Task Manager, right-click the app group that holds Console Window Host and select End task.
5. Watch the CPU column for a minute.

Closing a stuck program in Task Manager, step by step: Close a frozen app (Task Manager, Force Quit).

Fix 3. Update, repair or remove the tool behind a background conhost.exe

10 minutesLow riskFix 1 names a program from a driver, mouse, keyboard, RGB, audio, VPN, network or game launcher maker, and no window is visible.

Many vendor tools run console helpers in the background. A Microsoft Q&A user traced 13 conhost.exe copies to Razer, NVIDIA, SteelSeries, MSI and Killer software. A helper that loops or crashes and restarts keeps its conhost.exe busy; a newer version of the tool usually replaces it.

1. Note the full path from the Parent column in Fix 1. The folder name usually tells you the maker and the product.
2. Open that program and use its own update check, or download the newest version from the maker's website.
3. Restart the PC and run the Fix 1 command again.
4. If the load stays and you do not need the tool, press Win + I and open Apps > Installed apps (Windows 10: Apps > Apps & features).
5. Find the program, select ... (Windows 10: select it) and choose Modify or Repair if it is offered; otherwise Uninstall.
6. Restart and check Task Manager.

How to remove a program completely: Uninstall a program or app in Windows.

Fix 4. Stop the program from starting with Windows

5 minutesLow riskThe busy conhost.exe belongs to a tool that starts with Windows and you only need it now and then.

A tool that starts with Windows brings its console helpers and their conhost.exe with it. Turning the startup entry off stops the load without removing the tool; you can still open it when you need it.

1. Open the Startup settings. Select Start > Settings > Apps > Startup.
2. Turn apps off. Set the switch of each app you do not need at sign-in to Off. Use Sort by to put the apps with the highest impact first.
3. Or use Task Manager. Right-click Start, select Task Manager, then Startup apps. Select an app and select Disable. Task Manager shows the same list with more detail, such as the publisher.
4. Restart to check. Restart the PC. The apps you turned off no longer open by themselves.

These steps were written for Windows 11 24H2, 25H2 and 26H2. The full page with the other versions and what each result means: Stop apps from opening at startup

Fix 5. Find the scheduled task that starts cmd.exe or PowerShell

10 minutesLow riskThe parent in Fix 1 is cmd.exe or powershell.exe that you did not open, the load comes in waves, or a black window flashes.

A scheduled task that runs a command every few minutes starts a new console program each time, and each one gets a conhost.exe. Task Scheduler shows what runs, when and which file it starts.

1. Press Win + R, type taskschd.msc and press Enter.
2. Select Task Scheduler Library on the left.
3. Select the column header Next Run Time or Last Run Time and look for tasks that run every few minutes.
4. Select a task and open the Actions tab below. Note the program, for example cmd.exe or powershell.exe, and its arguments.
5. If the task belongs to a program you no longer use, right-click it and select Disable. Do not delete it yet.
6. Restart the PC and check Task Manager again.

Our guide to a cmd.exe window that keeps popping up shows more ways to find which program starts it, including Autoruns and process auditing.

Fix 6. Check that conhost.exe is the real Windows file, then scan for malware

5 minutes, plus 15 minutes or more for the scanNo riskThe path in Fix 1 is not C:\Windows\System32\conhost.exe, the parent sits in a Temp or AppData folder, or the CPU stays high with nothing open.

Malware sometimes uses familiar process names so it blends into Task Manager; coin miners in particular want steady CPU. The real conhost.exe has only one home and a Microsoft signature, so the location and the signature tell you more than the name.

1. In Task Manager, open the Details tab and right-click the busy conhost.exe.
2. Select Open file location. File Explorer must open C:\Windows\System32 with conhost.exe selected.
3. Right-click that file, select Properties and open the Digital Signatures tab. The signer must be Microsoft Windows.
4. Check the parent path from Fix 1 as well. A random name in %TEMP% or %AppData% is a warning sign even when conhost.exe itself is real.
5. If anything does not match, run a full scan with Microsoft Defender: How to scan for malware with Microsoft Defender.
6. If Defender finds a threat, or you still have doubts, run Microsoft Defender Offline scan, which restarts the PC and scans before Windows loads.

Fix 7. Find a conflicting program with a clean boot

15 minutesLow riskThe load keeps coming back and Fix 1 shows no clear parent, or the parent closes too fast to catch.

A clean boot starts Windows with only Microsoft services and no startup apps. If Console Window Host stays quiet then, one of the programs you turned off starts the busy console helper, and you can find it by turning them back on in halves.

1. Open System Configuration. Select Search on the taskbar, type msconfig and select System Configuration from the results.
2. Hide Microsoft services. On the Services tab, select the Hide all Microsoft services check box. Only services from other companies stay in the list.
3. Disable the remaining services. Select Disable all, then select Apply.
4. Open Task Manager. On the Startup tab of System Configuration, select Open Task Manager.
5. Disable the startup apps. On the Startup apps tab in Task Manager, select each item whose status is Enabled and select Disable. Write down or take a screenshot of the items you disable: you need the list to turn them back on.
6. Confirm the changes. Close Task Manager. On the Startup tab of System Configuration, select OK.
7. Restart and test. Restart the PC. Windows now starts in a clean boot environment: try again the thing that failed (run the app, install the update, uninstall the program).

These steps were written for Windows 11 25H2 and 26H2. The full page with the other versions and what each result means: How to perform a clean boot in Windows

Fix 8. Repair Windows system files with SFC and DISM

20 minutesNo riskOther Windows processes misbehave too, or the parent in Fix 1 is a Windows component that keeps failing.

conhost.exe and the console parts of Windows are system files. If they or the component store are damaged, console programs can fail and restart in a loop. SFC and DISM replace damaged system files with good copies.

1. Open an elevated command window. Right-click Start and select Terminal (Admin), or type cmd in the search box, right-click Command Prompt and select Run as administrator. Select Yes when Windows asks for permission.
2. Run DISM first. Type the command below and press Enter. DISM downloads clean copies of damaged components from Windows Update, so it can take several minutes. Wait until it says The operation completed successfully.

   DISM.exe /Online /Cleanup-Image /RestoreHealth

3. Run System File Checker. In the same window, type the command below and press Enter. Do not close the window until the verification reaches 100%.

   sfc /scannow

4. Read the result and restart. Compare the last message with the table below this guide, then restart the PC so that repaired files are loaded.

These steps were written for Windows 11 24H2 and 25H2. The full page with the other versions and what each result means: Run DISM and SFC to repair Windows system files

Console Window Host still uses high CPU: what to check next

If conhost.exe is genuine, the scan is clean and the load still returns, collect evidence before you reinstall anything. conhost.exe writes no log of its own; what matters is which program starts it and when.

• The parent path: run the Fix 1 command while the load is high and save the output. It is the single most useful fact for the maker of that program or a support forum.
• Reliability Monitor: type reliability in Start and open View reliability history. A red cross on the day the load began often names the app or update behind it.
• Event Viewer: press Win + R, type eventvwr.msc and open Windows Logs > Application. Repeated Application Error entries for the parent program show that it crashes and restarts.
• Repair install: as a last step, reinstall Windows over itself and keep your files and apps: Reinstall Windows without losing files.

How to keep Console Window Host from using high CPU again

• Close console windows when the work is done, instead of leaving logs, servers or watch commands running in the background.
• Send long command output to a file (> log.txt) rather than to the screen.
• Keep driver, peripheral and launcher tools up to date, and remove the ones you no longer use. Each brings its own background console helpers.
• Review Settings > Apps > Startup now and then and turn off tools you do not need at every start.
• Do not end, delete or replace conhost.exe. Windows needs it for every command-line program, and a copy from a download site is a risk.

Frequently asked questions

What is Console Window Host in Task Manager?

It is conhost.exe, a built-in Windows process. Microsoft describes the Windows Console Host as the server for all Windows Console APIs and the classic window for command-line programs. Programs such as cmd.exe, PowerShell and many background helpers hand their text to it, and it answers their console calls and shows the result. That is why it appears in Task Manager even when you have no command prompt open: some program on the PC is a console program, and conhost.exe runs for it. It used to be part of csrss.exe and was split out for security and isolation.

Why is Console Window Host running when I did not open a command prompt?

Because many programs use the console without showing a window. Drivers, mouse and RGB tools, audio and network utilities, launchers and scheduled tasks often run small console helpers in the background, and each one gets its own conhost.exe. A Microsoft Q&A user who found 13 copies traced them to Razer, NVIDIA, SteelSeries, MSI and Killer software, a wireless helper and similar tools. Fix 1 shows which program each copy belongs to. Several copies are normal; the question is only whether one of them stays busy.

Why does Console Window Host use high CPU?

Because the program it serves keeps it busy. Every line a console program prints and every console call it makes goes through conhost.exe, so a script printing a flood of text, a looping helper or a tool that crashes and restarts shows up as Console Window Host CPU. Most often the cure is to close, update or remove that program, not to touch conhost.exe. Rarely the file is a fake copy using the name; Fix 6 shows the check for that.

Is conhost.exe a virus?

The real conhost.exe is not. It lives in C:\Windows\System32 and is digitally signed by Microsoft Windows. Malware can use the same name to hide in Task Manager, so check the copy that worries you: on the Details tab, right-click it, select Open file location and look at the folder, then check the Digital Signatures tab in its Properties. A conhost.exe anywhere else, or one without a Microsoft signature, is not the Windows file. Scan the PC with Microsoft Defender, then run a Defender Offline scan as in Fix 6.

Can I end or disable conhost.exe?

You can end one copy, but it ends the console program it serves as well, and Windows starts a new conhost.exe the next time that program runs. You cannot disable it: every command-line program in Windows needs it. Ending the parent program in a controlled way is the better choice, as in Fix 2. Never delete conhost.exe from System32 or replace it with a downloaded copy; that breaks every command prompt, script and console tool on the PC.

Why are there so many Console Window Host processes?

Each console program gets its own conhost.exe. If five background tools and two scripts run, Task Manager shows seven Console Window Host lines. Many copies are not a problem by themselves; each one usually uses almost no CPU and a few MB of memory. Use the command in Fix 1 to see which program owns each copy. If one copy belongs to a program you do not know, check its path and run the malware check in Fix 6.

Is it a problem when conhost.exe uses a lot of memory?

Usually it means the console window keeps a very long history, or the program behind it prints without a break. Closing that window frees the memory. If the memory keeps growing with no window open, the parent program is the one to update or remove, as in Fix 3. If no single program stands out and other Windows processes misbehave too, run SFC and DISM as in Fix 8, and check that the file is genuine as in Fix 6.

Does Windows Terminal replace conhost.exe?

Not fully. Microsoft's console documentation says terminals take over the window through a pseudoconsole, while conhost.exe stays in charge of the console API calls and their translation. So with Windows Terminal you still see Console Window Host or conhost.exe in Task Manager for each tab. Windows Terminal can be set as the default terminal application on all versions of Windows 11, and on Windows 10 22H2 after the May 23, 2023 update KB5026435.

Where is conhost.exe located?

The Windows file is C:\Windows\System32\conhost.exe, signed by Microsoft Windows. To check a running copy, open Task Manager, go to the Details tab, right-click conhost.exe and select Open file location. The ExecutablePath column of the command in Fix 1 shows the path of every copy at once. A conhost.exe in a Temp, AppData, Downloads or other user folder is not the Windows file: scan the PC as in Fix 6.