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

powershell.exe starts a new console rather than attaching to current when not elevated #21799

New Issue
Closed
opened 2026-01-31 07:55:12 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 07:55:12 +00:00
Owner
Copy Link

Originally created by @SteveL-MSFT on GitHub (Jun 1, 2024).

Windows Terminal version

1.20.11381.0

Windows build number

10.0.22631.3593

Other Software

No response

Steps to reproduce

In non-elevated cmd.exe within WT, run: powershell.exe

Note: this repros with conhost

Expected Behavior

powershell.exe uses the current console and starts within cmd.exe

Actual Behavior

powershell.exe is spawned in a new window

Note: if cmd.exe is elevated, then powershell.exe DOES start within the same console. This also seems to only repro to domain joined systems and doesn't repro with a clean system in a workgroup so might be related to some GPO?

Originally created by @SteveL-MSFT on GitHub (Jun 1, 2024). ### Windows Terminal version 1.20.11381.0 ### Windows build number 10.0.22631.3593 ### Other Software _No response_ ### Steps to reproduce In non-elevated cmd.exe within WT, run: `powershell.exe` Note: this repros with conhost ### Expected Behavior `powershell.exe` uses the current console and starts within cmd.exe ### Actual Behavior `powershell.exe` is spawned in a new window Note: if `cmd.exe` is elevated, then `powershell.exe` DOES start within the same console. This also seems to only repro to domain joined systems and doesn't repro with a clean system in a workgroup so might be related to some GPO?
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 07:55:12 +00:00
claunia commented 2026-01-31 07:55:13 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 1, 2024):

There's definitely something to the idea that it being domain-joined breaks it.

My home laptop:
image

my work VM:
image

Same Windows builds. Different results. Yikes.

@zadjii-msft commented on GitHub (Jun 1, 2024): There's definitely something to the idea that it being domain-joined breaks it. My home laptop: ![image](https://github.com/microsoft/terminal/assets/18356694/e614bddc-ee4f-4d4a-bcde-bad43f2e4c5f) my work VM: ![image](https://github.com/microsoft/terminal/assets/18356694/c20e623b-547e-402a-8967-c2682102ee57) Same Windows builds. Different results. Yikes.
claunia commented 2026-01-31 07:55:13 +00:00
Author
Owner
Copy Link

@yaozhenhua commented on GitHub (Jun 2, 2024):

I noticed this problem too. It breaks our build process since we run powershell scripts in MSBuild. Now before the execution is completed the build has already moved forwarded which ends up an empty file.

@yaozhenhua commented on GitHub (Jun 2, 2024): I noticed this problem too. It breaks our build process since we run powershell scripts in MSBuild. Now before the execution is completed the build has already moved forwarded which ends up an empty file.
claunia commented 2026-01-31 07:55:13 +00:00
Author
Owner
Copy Link

@MichalStrehovsky commented on GitHub (Jun 3, 2024):

This is related to some bad InTune policies that were rolled out Microsoft-wide. Opening Terminal as an administrator works around. Tickets with Microsoft IT have been raised internally.

@MichalStrehovsky commented on GitHub (Jun 3, 2024): This is related to some bad InTune policies that were rolled out Microsoft-wide. Opening Terminal as an administrator works around. Tickets with Microsoft IT have been raised internally.
claunia commented 2026-01-31 07:55:14 +00:00
Author
Owner
Copy Link

@joon612 commented on GitHub (Jun 3, 2024):

This is related to some bad InTune policies that were rolled out Microsoft-wide. Opening Terminal as an administrator works around. Tickets with Microsoft IT have been raised internally.

Same issue here. Could you provide more information about this? Our team and our services have been greatly affected by this issue, thanks!

@joon612 commented on GitHub (Jun 3, 2024): > This is related to some bad InTune policies that were rolled out Microsoft-wide. Opening Terminal as an administrator works around. Tickets with Microsoft IT have been raised internally. Same issue here. Could you provide more information about this? Our team and our services have been greatly affected by this issue, thanks!
claunia commented 2026-01-31 07:55:14 +00:00
Author
Owner
Copy Link

@MichalStrehovsky commented on GitHub (Jun 3, 2024):

This is related to some bad InTune policies that were rolled out Microsoft-wide. Opening Terminal as an administrator works around. Tickets with Microsoft IT have been raised internally.

Same issue here. Could you provide more information about this? Our team and our services have been greatly affected by this issue, thanks!

I don't have more information, sorry. Several of my Redmond-based coworkers were hitting this in the past 24 hours and at least two of them have a case number with MSIT. I can't refer you to the case number since Redmond is sleeping now but the issue started showing up after an Intune policy rollout. I recommend opening a case with MSIT as well.

@MichalStrehovsky commented on GitHub (Jun 3, 2024): > > This is related to some bad InTune policies that were rolled out Microsoft-wide. Opening Terminal as an administrator works around. Tickets with Microsoft IT have been raised internally. > > Same issue here. Could you provide more information about this? Our team and our services have been greatly affected by this issue, thanks! I don't have more information, sorry. Several of my Redmond-based coworkers were hitting this in the past 24 hours and at least two of them have a case number with MSIT. I can't refer you to the case number since Redmond is sleeping now but the issue started showing up after an Intune policy rollout. I recommend opening a case with MSIT as well.
claunia commented 2026-01-31 07:55:14 +00:00
Author
Owner
Copy Link

@SteveL-MSFT commented on GitHub (Jun 3, 2024):

Closing this as it appears to be Microsoft internal policy issue

@SteveL-MSFT commented on GitHub (Jun 3, 2024): Closing this as it appears to be Microsoft internal policy issue
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 Issue-Bug Needs-Triage
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#21799
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?