Open in Terminal / Windows Terminal context menu cleanup

Published September 2026, Windows 11 24H2 / 25H2

“Open in Terminal” is useful until you have three of them, a dead “Open PowerShell window here,” and a desktop right-click that hesitates before listing anything. Windows Terminal, the inbox Windows 11 integration, and leftover Windows Console Host entries can stack on the same folder background menu.

This guide cleans duplicates, removes handlers you do not use, and keeps a fast way to open wt.exe without Explorer tax.

Where Terminal hooks live

Windows does not only use classic shellex\ContextMenuHandlers for Terminal. Modern packages also register under:

• Directory and Directory\Background shell verbs
• Store package identity for Windows Terminal
• Extended context menu entries that appear under Show more options on Windows 11

You may also still have older entries:

• Open PowerShell window here
• Open command window here (legacy)
• Third-party consoles (ConEmu, Cmder, FreeCommander tools, etc.)

Duplicates are a clutter problem first. They become a performance problem when a registered package is broken, updating, or blocking while it resolves AppX state.

General menu lag background: Windows 11 context menu slow fix.

Step 1: Inventory what you see

1. Right-click empty space inside a folder (not on a file).
2. Note every terminal-related item on the compact menu and under Show more options.
3. Right-click the desktop background and compare. Desktop uses Directory\Background paths; some Terminal entries appear only there.
4. Write down exact labels (Open in Terminal, Open in Windows Terminal, Open PowerShell window here).

If lag exists only on empty background, you are in desktop/folder background handler territory. See also the desktop-only lag guide in this series.

Step 2: Prefer Windows Terminal settings

Current Windows Terminal builds expose context menu / default profile options:

1. Open Windows Terminal.
2. Open Settings (Ctrl+,).
3. Check interaction / defaults for options that add Explorer integration (wording changes across releases).
4. Set your default profile (PowerShell 7 vs Windows PowerShell vs cmd) so one “Open in Terminal” does what you expect.
5. Update Terminal from Microsoft Store so package registrations are healthy.

If the Store package is mid-update, context menu verbs can stall. Finish updates, reboot once, retest before deleting registry keys.

Step 3: ShellExView for classic handlers

Some leftovers still show as shell extensions:

1. Run ShellExView as Administrator.
2. Search for Terminal, PowerShell, Console, cmd.
3. Disable non-Microsoft console tools you do not use (F7).
4. For Microsoft entries, only disable if you confirmed they are redundant and you have another launch method.
5. Restart Explorer and retest.

Unfamiliar DLLs: DLL checker.

When many third-party tools are present, binary-search context menu handlers as described in Disable shell extensions on Windows 11.

Step 4: Clean duplicate shell verbs (advanced)

Only if duplicates remain after settings and ShellExView. Export a .reg backup first.

Inspect:

HKEY_CLASSES_ROOT\Directory\shell
HKEY_CLASSES_ROOT\Directory\Background\shell
HKEY_CLASSES_ROOT\Drive\shell

Look for keys clearly named for Windows Terminal, PowerShell, or cmd. Valid inbox keys often include package identifiers. Do not delete random CLSID folders under shellex unless ShellExView mapped them.

Safer approach than guessing:

1. Rename a suspect key by prefixing backup_ instead of deleting.
2. Restart Explorer.
3. Retest menu.
4. If something breaks that you need, rename back.

On 64-bit Windows, avoid mixing up WOW6432Node leftovers from old 32-bit console tools.

Step 5: Remove obsolete “Open command window here” hacks

Old guides added cmd keys under Directory\Background\shell to replace PowerShell. On Windows 11 those hacks collide with Terminal verbs.

1. If you added custom keys years ago, remove or rename those custom keys only.
2. Prefer wt.exe -d . from a shortcut if you want cmd-like behavior in Terminal.

Fast launch without context menu

After cleanup, use any of these:

• Win + X then Terminal or Terminal (Admin)
• Pin Windows Terminal to the taskbar; File Explorer → open folder → Ctrl+L, type wt and Enter in some builds, or use address bar tricks you already know
• Create a desktop shortcut to wt.exe with arguments -d "%V" for “here” behavior when dropped on folders
• PowerToys or your launcher to bind a hotkey to Terminal

You do not need three Explorer verbs for one binary.

24H2 / 25H2 specific notes

• Compact menu may show a single Open in Terminal while Show more options still lists legacy PowerShell entries. Clean both layers if clutter bothers you.
• After Feature updates, Microsoft may restore default Terminal verbs. Re-check once; do not fight Store repairs by deleting package files.
• If Explorer freezes only when Terminal is updating, wait for the update; do not chase shell extensions mid-Store install.

PowerShell vs Terminal vs cmd labels

Expect some mix of these strings on upgraded PCs:

• Open in Terminal
• Open in Windows Terminal
• Open PowerShell window here
• Open in Terminal Preview (if Preview is installed beside stable)
• Open command window here (old tweak)

Pick one launch path. For most people on 24H2/25H2 that is inbox Windows Terminal. Disable or rename the rest so Explorer is not resolving multiple package verbs on every background click.

If both Terminal stable and Terminal Preview are installed, remove Preview unless you actively test it. Two Store packages mean two chances for duplicate verbs.

If cleanup does not fix lag

Terminal was not the bottleneck. Continue with binary search across non-Microsoft handlers, and check cloud/archiver DLLs. For crashes when right-clicking background, use Find which shell extension is crashing Explorer. Desktop-only lag after Terminal cleanup belongs in the empty desktop handler guide in this series.

Related guides

• Disable shell extensions on Windows 11
• Windows 11 context menu slow fix
• Find which shell extension is crashing Explorer
• ShellExView download
• DLL checker