conhost.exe
Also called conhost, console window host
Console Window Host. It draws the window for Command Prompt, PowerShell, and other console apps.
What you need to know
This is the window around Command Prompt, not a hidden virus by default.
conhost.exe hosts the console UI. You see it when cmd, PowerShell, or another console app is running. Close that app instead of ending conhost first.
- Safe?
- Usually yes
- Should I close it?
- Close the console app instead
- Why is it here?
- A console app is open or just ran
What is conhost.exe?
conhost.exe is Console Window Host. It is the Windows-owned window and input path for console applications.
What does it do?
It renders text, handles resize, and connects a console app to the desktop. Windows Terminal can sit in front of the same idea.
Why is it running?
A console app started. Installers, scripts, and developer tools do this often.
Why are there multiple copies?
Each console session can have its own host. Several copies mean several consoles, not several infections by default.
Is it safe?
Usually safe
The legitimate host is in System32. A conhost.exe from a random folder is not the Windows console host.
A legitimate copy normally runs from:
C:\Windows\System32\conhost.exe
- Expected publisher: Microsoft Corporation
- Expected path: System32
Can I end it?
Close the console app first
Ending conhost can kill the console session. Close Command Prompt or PowerShell if you meant to stop the work.
Can I remove it?
No
Do not delete conhost.exe. Console apps need a host.
Should it start with Windows?
It starts with a console app. It is not a startup leftover you should remove.
Normal resource behavior
These are contextual labels, not universal averages.
- CPU
- Follows the console app
- Memory
- Usually modest
- Disk
- Low
- Network
- None by itself
File information
| Executable name | conhost.exe |
|---|---|
| Common legitimate path | C:\Windows\System32\conhost.exe |
| Publisher | Microsoft Corporation |
| Signature expectation | Signed by Microsoft Windows |
Common problems
Stays after a script
A script window may still be open. Close that window. If a host remains with no window, sign out and back in before you delete files.
High CPU
Look at the child command. A looping script is a better suspect than the host name.
Troubleshooting
Diagnose before you change anything destructive.
Confirm the path and signature
Open the process properties and check that conhost.exe runs from the expected folder and is signed by the expected publisher. This is the first check, not a Registry edit.
See what the process is doing
Task Manager can show CPU, memory, disk, and GPU. High use during an obvious job is often normal. High use when the PC is idle needs a closer look at the related app or service.
Avoid destructive first steps
Do not delete conhost.exe, disable critical services without knowing the effect, or edit the Registry as the first move.
Technical details
Technical details
| Image name | conhost.exe |
|---|---|
| Friendly name | Console Window Host |
Sources and verification
Reviewed by Feex editorial. Last verified August 2026 Status: Feex Reviewed. How we research.
- Microsoft Learn: Console host · Console host documentation
Was this article useful?
A yes or no is enough. Pick a reason if you want, or add a short note.
Thanks. That helps us improve this page.