starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Choosing command prompt pop up a new window #12204

New Issue
Closed
opened 2026-01-31 03:08:57 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 03:08:57 +00:00
Owner
Copy Link

Originally created by @remygrandin on GitHub (Jan 26, 2021).

Environment

Windows build number: 10.0.19042.0
Windows Terminal version (if applicable): 1.4.3243.0

Any other software?
The workstation is managed by intune with default win 10 security baseline
My account is tenant admin and by extension local admin of the workstation

Steps to reproduce

Install windows terminal and launch it.
Select in the tab dropdown "Command Prompt"
the cmd pop up a a separate cmd window (not integrated as a tab)

Expected behavior

We expect the cmd to be created as a tab in the windows terminal app

Actual behavior

The cmd is created as an external, separate window

Originally created by @remygrandin on GitHub (Jan 26, 2021). <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: 10.0.19042.0 Windows Terminal version (if applicable): 1.4.3243.0 Any other software? The workstation is managed by intune with default win 10 security baseline My account is tenant admin and by extension local admin of the workstation ``` # Steps to reproduce Install windows terminal and launch it. Select in the tab dropdown "Command Prompt" the cmd pop up a a separate cmd window (not integrated as a tab) <!-- A description of how to trigger this bug. --> # Expected behavior We expect the cmd to be created as a tab in the windows terminal app <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior The cmd is created as an external, separate window <!-- What's actually happening? -->
claunia added the Needs-TriageResolution-ExternalNeeds-Tag-FixNeeds-Attention labels 2026-01-31 03:08:57 +00:00
claunia commented 2026-01-31 03:08:58 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 26, 2021):

Fascinating. I don't think I've heard of anything like that before.

Does the same thing happen with powershell? Or only cmd.exe?

@zadjii-msft commented on GitHub (Jan 26, 2021): Fascinating. I don't think I've heard of anything like that before. Does the same thing happen with powershell? Or only `cmd.exe`?
claunia commented 2026-01-31 03:08:59 +00:00
Author
Owner
Copy Link

@remygrandin commented on GitHub (Jan 27, 2021):

Only cmd.
Powershell or wsl is oppening a new tab as expected.

However, I just tested and the same thing happened in a standard standalone powershell windows if I run cmd.

@remygrandin commented on GitHub (Jan 27, 2021): Only cmd. Powershell or wsl is oppening a new tab as expected. However, I just tested and the same thing happened in a standard standalone powershell windows if I run cmd.
claunia commented 2026-01-31 03:08:59 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 27, 2021):

Fascinating. That raises more questions. Could you share the output of where cmd (from any command prompt)? Do you have anything installed that might be hooking cmd.exe? Maybe something like yori, cmder, clink, conemu?

@zadjii-msft commented on GitHub (Jan 27, 2021): Fascinating. That raises more questions. Could you share the output of `where cmd` (from any command prompt)? Do you have anything installed that might be hooking cmd.exe? Maybe something like yori, cmder, clink, conemu?
claunia commented 2026-01-31 03:08:59 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jan 27, 2021):

In addition to answering that, would you mind running...

reg query "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\cmd.exe"
@DHowett commented on GitHub (Jan 27, 2021): In addition to answering that, would you mind running... ```powershell reg query "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\cmd.exe" ```
claunia commented 2026-01-31 03:09:00 +00:00
Author
Owner
Copy Link

@remygrandin commented on GitHub (Jan 29, 2021):

I think i have tracked donw the source. It seem to be the local admin access solution that we use (Admin By Request) that was causing the behavior (once remove, cmd operate as expected)

It was futher proven by @DHowett command :

C:\Windows\system32>reg query "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\cmd.exe"

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\cmd.exe
    VirtualizerType    REG_SZ    1
    Debugger    REG_SZ    "C:\Program Files (x86)\FastTrack Software\Admin By Request\AdminByRequest.exe" /Block

We will contact them to know if the behavior is expected and if so if they can do anything about it.

@remygrandin commented on GitHub (Jan 29, 2021): I think i have tracked donw the source. It seem to be the local admin access solution that we use (Admin By Request) that was causing the behavior (once remove, cmd operate as expected) It was futher proven by @DHowett command : ``` C:\Windows\system32>reg query "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\cmd.exe" HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\cmd.exe VirtualizerType REG_SZ 1 Debugger REG_SZ "C:\Program Files (x86)\FastTrack Software\Admin By Request\AdminByRequest.exe" /Block ``` We will contact them to know if the behavior is expected and if so if they can do anything about it.
claunia commented 2026-01-31 03:09:01 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 29, 2021):

Ah good to know. Thanks for following up!

@zadjii-msft commented on GitHub (Jan 29, 2021): Ah good to know. Thanks for following up!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Needs-Attention Needs-Tag-Fix Needs-Triage Resolution-External
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#12204
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?