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

Bug Report - RunAs / CPAU opens separate CMD window outside of Terminal #2291

New Issue
Open
opened 2026-01-30 22:51:39 +00:00 by claunia · 0 comments
claunia commented 2026-01-30 22:51:39 +00:00
Owner
Copy Link

Originally created by @jricha34 on GitHub (Jun 26, 2019).

Environment

Windows build number: [10.0.18362.175]
Windows Terminal version (if applicable): 0.2.1715.0

Any other software?
None

Steps to reproduce

runas /user:someuser cmd
enter password of someuser

Expected behavior

Open another CMD within Terminal

Actual behavior

Opens CMD outside of Terminal in CMD standalone window.

In general I was trying to figure out how to open a terminal window from the command line in alternate creds and couldn't sort it out. I got access denied when trying to launch.

Something I regularly do is use runas /netonly or cpau (www.joeware.net) to launch CMD with alternate creds which locally is whatever user I am logged into the PC with but remotely is the alternate credentials. For example I will open up CMD windows in creds from say 5-10 different disconnected AD Forests. Then as I need to manage the different forests I jump to the proper CMD window and run the commands I need to run.

As an aside, I am thrilled to see all of this work being done for command line access. There are quite a few of us who have been managing Windows and eventually AD from the command line since NT4 in the late 90s.

joe (joe@joeware.net)

Originally created by @jricha34 on GitHub (Jun 26, 2019). # Environment Windows build number: [10.0.18362.175] Windows Terminal version (if applicable): 0.2.1715.0 Any other software? None # Steps to reproduce runas /user:someuser cmd enter password of someuser # Expected behavior Open another CMD within Terminal # Actual behavior Opens CMD outside of Terminal in CMD standalone window. In general I was trying to figure out how to open a terminal window from the command line in alternate creds and couldn't sort it out. I got access denied when trying to launch. Something I regularly do is use runas /netonly or cpau (www.joeware.net) to launch CMD with alternate creds which locally is whatever user I am logged into the PC with but remotely is the alternate credentials. For example I will open up CMD windows in creds from say 5-10 different disconnected AD Forests. Then as I need to manage the different forests I jump to the proper CMD window and run the commands I need to run. As an aside, I am thrilled to see all of this work being done for command line access. There are quite a few of us who have been managing Windows and eventually AD from the command line since NT4 in the late 90s. joe (joe@joeware.net)
claunia added the Issue-FeatureResolution-DuplicateProduct-TerminalArea-Interop labels 2026-01-30 22:51:39 +00:00
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 Area-Interop Issue-Feature Product-Terminal Resolution-Duplicate
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#2291
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?