# WindowsTerminal.exe

Application Process: Microsoft Corporation

Also called windows terminal, wt, windowsterminal

Windows, Application

Windows Terminal UI. It is the tabbed window from Microsoft.WindowsTerminal. It is not OpenConsole.exe and it is not pwsh.exe.

## What you need to know

This is the Terminal window, not OpenConsole and not pwsh.

WindowsTerminal.exe is the tab UI. OpenConsole.exe hosts the console buffer. The command line you typed runs in pwsh.exe, powershell.exe, cmd.exe, or wsl.exe. Ending the UI closes tabs. A scheduled pwsh can keep running without this window.

- **Safe?**: Yes, from Windows Terminal

  **Is it the shell?**: No. The shell is pwsh, cmd, or wsl

  **Can I end it?**: All Terminal windows close

Feex says

If Windows Terminal is the row, I am looking at the frame. I read the tab profile when I want the shell, and I do not call this process pwsh.

## What is WindowsTerminal.exe?

This is the Terminal window, not OpenConsole and not pwsh. The package is Microsoft.WindowsTerminal under WindowsApps. OpenConsole is the console host. pwsh is PowerShell 7 inside a tab.

## What does it do?

It draws tabs, panes, and settings. It does not interpret PowerShell cmdlets and it is not the classic conhost for Win+R cmd.

## Why is it running?

You opened Windows Terminal, wt.exe, or a profile shortcut. A hidden WindowsTerminal at logon is a Startup or task you added.

## Is it safe?

Usually safe

The WindowsApps Microsoft.WindowsTerminal UI is Microsoft. A WindowsTerminal.exe in Downloads is not. This is still not pwsh.exe and not OpenConsole.exe.

A legitimate copy normally runs from:

`C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_*\WindowsTerminal.exe`

- Package: Microsoft.WindowsTerminal
- Console host sibling: OpenConsole.exe
- Shell siblings: pwsh, powershell, cmd, wsl

## Can I end it?

Closes Terminal

Ending WindowsTerminal.exe closes the tabbed UI. OpenConsole and the shell for those tabs usually exit. A pwsh started by Task Scheduler can remain.

## Can I remove it?

Uninstall the app

Uninstall Windows Terminal from Apps. Do not delete OpenConsole from another package by hand. Do not delete System32\conhost.exe.

## Should it start with Windows?

You can pin Terminal or add a Startup shortcut. That starts this UI, not pwsh by itself unless the profile says so.

## Normal resource behavior

These are contextual labels, not universal averages.

- **CPU**: UI plus whatever the tabs run

  **Memory**: Moderate for the frame, plus each shell

  **GPU**: Terminal rendering can use the GPU

  **Disk**: Settings and logs, not the Linux VHDX

## File information

| Executable name        | WindowsTerminal.exe                                                            |
| ---------------------- | ------------------------------------------------------------------------------ |
| Common legitimate path | C:\Program Files\WindowsApps\Microsoft.WindowsTerminal\_\*\WindowsTerminal.exe |
| Publisher              | Microsoft Corporation                                                          |
| Signature expectation  | Signed by Microsoft Windows                                                    |

## Common problems

### People end pwsh to close Terminal and leave a ghost window

Close this UI process or the window. Killing one shell tab does not always exit WindowsTerminal.exe.

### GPU use blamed on OpenConsole only

The frame renders here. The buffer host is OpenConsole. Check both before you reset the GPU driver.

## Troubleshooting

Diagnose before you change anything destructive.

### wt.exe or the Start item, then check Settings > Startup

A Terminal window at logon is this exe. A PowerShell 7 task without a window is pwsh, not this UI.

### Reset Windows Terminal from Apps if the UI will not open

That repairs Microsoft.WindowsTerminal. Replacing conhost.exe does not restore this frame.

## Technical details

Technical details

| Image name | WindowsTerminal.exe       |
| ---------- | ------------------------- |
| Package    | Microsoft.WindowsTerminal |

## Related

These entities connect to this article. Type is shown on every link.

[OpenConsole.exe: Application Process](https://feex.it/wiki/process/openconsole.exe)[pwsh.exe: Application Process](https://feex.it/wiki/process/pwsh.exe)[conhost.exe: Windows Process](https://feex.it/wiki/process/conhost.exe)

## Sources and verification

Reviewed by Feex editorial. Last verified August 2026 Status: Feex Reviewed. [How we research](https://feex.it/wiki/research).

- [Microsoft Learn: install Windows Terminal ](https://learn.microsoft.com/windows/terminal/install)· WindowsTerminal.exe is the Store / inbox Terminal UI
- [Microsoft Store: Windows Terminal ](https://apps.microsoft.com/detail/9n0dx20hk701)· Package Microsoft.WindowsTerminal
- [Foxhole process map ](https://foxhole.feex.it/)· 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.

Quick facts

The short identity of this page. Specs, sources, and the full story stay in the article.

- **Type**: Application Process

  **Publisher**: Microsoft Corporation

  **Executable**: WindowsTerminal.exe

  **Typical path**: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal\_\*\WindowsTerminal.exe

  **Mapped by Feex**: Seen on Windows PCs in Foxhole

Feex Reviewed: Last verified August 2026

---

Source: [Canonical Feex Wiki page](https://feex.it/wiki/process/windowsterminal.exe/)

[Developer guide](https://feex.it/wiki/developers/) | [API policy](https://feex.it/developers/api-policy/) | [Agent guidance](https://feex.it/wiki/llms.txt)