OpenConsole.exe

Application ProcessMicrosoft Corporation

Also called openconsole, open console, terminal console host

WindowsApplication

Console host used by Windows Terminal. It is the ConPTY / console-host piece from the Terminal package, not conhost.exe of a classic console.

What you need to know

OpenConsole is Terminal's console host, not conhost.exe of classic consoles.

OpenConsole.exe hosts the console for Windows Terminal tabs. conhost.exe still hosts classic consoles (Win+R cmd, older attach). WindowsTerminal.exe is the tabbed window. pwsh.exe or cmd.exe is the shell inside. Ending OpenConsole drops that Terminal console, not every conhost on the PC.

Safe?: Yes, with Windows Terminal
Same as conhost?: No. This is Terminal's console host
Same as WindowsTerminal?: No. That is the tab UI

Feex says

If a Terminal tab died and OpenConsole vanished, I restart the tab. I do not kill conhost for every cmd window on the machine.

What is OpenConsole.exe?

OpenConsole is Terminal's console host, not conhost.exe of classic consoles. The inbox host stays conhost.exe. This file lives with Microsoft.WindowsTerminal. It is not the Terminal window chrome.

What does it do?

It owns the console buffer and PTY for a Terminal tab. WindowsTerminal.exe paints tabs. The shell is still pwsh, powershell, cmd, or wsl.

Why is it running?

A Windows Terminal tab is open. A Win+R cmd that never opened Terminal should show conhost.exe instead.

Is it safe?

Usually safe

An OpenConsole in the Windows Terminal package is Microsoft. An OpenConsole.exe on the desktop is not. This is still not conhost.exe.

A legitimate copy normally runs from:

C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_*\OpenConsole.exe

Package: Microsoft.WindowsTerminal
Classic sibling: System32\conhost.exe
UI sibling: WindowsTerminal.exe

Can I end it?

That Terminal console drops

Ending OpenConsole.exe can kill the shell attached to that tab. Other conhost.exe windows can stay. Ending WindowsTerminal.exe closes the whole UI.

Can I remove it?

Uninstall Terminal, not conhost

Uninstall Windows Terminal from Apps if you want OpenConsole gone. Do not delete System32\conhost.exe. Do not delete System32.

Should it start with Windows?

Opening Windows Terminal starts it. Classic cmd at logon still uses conhost, not this host.

Normal resource behavior

These are contextual labels, not universal averages.

CPU: Follows the attached shell output rate
Memory: Small next to the shell
Disk: Low
Network: None by itself

File information

OpenConsole.exe file information
Executable name	OpenConsole.exe
Common legitimate path	C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_*\OpenConsole.exe
Publisher	Microsoft Corporation
Signature expectation	Signed by Microsoft Windows

Common problems

People end conhost to fix a stuck Terminal tab

This tab's host is OpenConsole. conhost belongs to classic consoles. End the right host or close the tab.

A "console host" CPU spike they blame on pwsh only

The shell does the work. This process only hosts the buffer. Check which tab is attached.

Troubleshooting

Diagnose before you change anything destructive.

Process Explorer: which shell is attached to this OpenConsole

pwsh, cmd, or wsl is the command story. WindowsTerminal.exe is only the frame.

Settings > Apps > Windows Terminal > Reset if tabs will not spawn

That repairs the package host. Replacing conhost.exe does not fix OpenConsole.

Technical details

OpenConsole.exe technical details
Image name	OpenConsole.exe
Role	Windows Terminal console host

Sources and verification

Reviewed by Feex editorial. Last verified August 2026 Status: Feex Reviewed. How we research.

Microsoft Learn: console host · Classic consoles use conhost.exe
Microsoft Learn: Windows Terminal · Terminal ships OpenConsole as its console host
Foxhole process map · First-party samples on Windows PCs. Not a lab benchmark.

Was this article useful?

A yes or no is enough. Pick a reason if you want, or add a short note.