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

Integrated PowerShell not working properly #10426

New Issue
Closed
opened 2026-01-31 02:21:18 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 02:21:18 +00:00
Owner
Copy Link

Originally created by @anshdhinhgra47 on GitHub (Aug 31, 2020).

Environment

Windows build number: [run OS Version: Windows_NT x64 10.0.18362 for powershell]
Windows Terminal version (if applicable):

Any other software?

Steps to reproduce

Stop the server using Ctrl +C

Expected behavior

On entering n/N as input, the server should not stop running.

Actual behavior

The integrated PowerShell stops the server even after accepting n/N as an input. An image for reference is attached below.

windows_powershell_error

Originally created by @anshdhinhgra47 on GitHub (Aug 31, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- 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: [run OS Version: Windows_NT x64 10.0.18362 for powershell] Windows Terminal version (if applicable): Any other software? ``` # Steps to reproduce Stop the server using Ctrl +C # Expected behavior On entering n/N as input, the server should not stop running. # Actual behavior The integrated PowerShell stops the server even after accepting n/N as an input. An image for reference is attached below. ![windows_powershell_error](https://user-images.githubusercontent.com/56676059/91756221-04957600-ebea-11ea-9f1c-ae27351944dc.png)
claunia added the Issue-QuestionNeeds-Tag-FixResolution-Answered labels 2026-01-31 02:21:18 +00:00
claunia commented 2026-01-31 02:21:19 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Sep 1, 2020):

Did you file also with VSCode (which you didn't mention but is clearly shown in the screenshot)?

@WSLUser commented on GitHub (Sep 1, 2020): Did you file also with VSCode (which you didn't mention but is clearly shown in the screenshot)?
claunia commented 2026-01-31 02:21:19 +00:00
Author
Owner
Copy Link

@anshdhinhgra47 commented on GitHub (Sep 1, 2020):

Yes, but they closed the issue and asked me to file here.

@anshdhinhgra47 commented on GitHub (Sep 1, 2020): Yes, but they closed the issue and asked me to file here.
claunia commented 2026-01-31 02:21:19 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Sep 1, 2020):

Ok, then try using Windows Terminal. Also please link back the VS Code issue in case there are more details worth looking at. It comes with a newer conhost known as OpenConsole. If this works, you can either

  1. Continue to use Windows Terminal (recommended)
    or
  2. Disclaimer: Completely unsupported, not endorsed, here be dragons :
    Locate OpenConsole.exe, copy it to system32, rename to conhost.exe (backup the original first). now you'll be running a newer console by default for the OS. If new problems occur, you'll be on your own.
@WSLUser commented on GitHub (Sep 1, 2020): Ok, then try using Windows Terminal. Also please link back the VS Code issue in case there are more details worth looking at. It comes with a newer conhost known as OpenConsole. If this works, you can either 1) Continue to use Windows Terminal (recommended) or 2) **Disclaimer: Completely unsupported, not endorsed, here be dragons** : Locate OpenConsole.exe, copy it to system32, rename to conhost.exe (backup the original first). now you'll be running a newer console by default for the OS. If new problems occur, you'll be on your own.
claunia commented 2026-01-31 02:21:19 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Sep 1, 2020):

Please also note you can configure VS Code to launch Windows Terminal as an external terminal in Settings for VS Code. Also would suggest a backport of the particular fix (once a bisect between conhost and openconsole is done) for this issue if it is indeed resolved using OpenConsole.

@WSLUser commented on GitHub (Sep 1, 2020): Please also note you can configure VS Code to launch Windows Terminal as an external terminal in Settings for VS Code. Also would suggest a backport of the particular fix (once a bisect between conhost and openconsole is done) for this issue if it is indeed resolved using OpenConsole.
claunia commented 2026-01-31 02:21:19 +00:00
Author
Owner
Copy Link

@anshdhinhgra47 commented on GitHub (Sep 1, 2020):

Alright.

@anshdhinhgra47 commented on GitHub (Sep 1, 2020): Alright.
claunia commented 2026-01-31 02:21:20 +00:00
Author
Owner
Copy Link

@KalleOlaviNiemitalo commented on GitHub (Sep 1, 2020):

AFAIK, the "Terminate batch job (Y/N)?" question comes from cmd.exe, rather than PowerShell. For example, if you have an progs.bat file that contains two lines

prog1.exe
prog2.exe

and you run progs.bat and press Ctrl+C while prog1.exe is running, then prog1.exe is first terminated; after that, cmd.exe asks whether you want to terminate progs.bat as a whole or proceed to run prog2.exe.

So, I suspect that:

  • Your npm start command runs some npm.bat or npm.cmd file, which then runs npm from its installation directory.
  • Your Ctrl+C has already terminated npm before the "Terminate batch job (Y/N)?" question appears.
  • The behavior would be the same even if VSCode, PowerShell, and Windows Terminal had not been installed.
@KalleOlaviNiemitalo commented on GitHub (Sep 1, 2020): AFAIK, the "Terminate batch job (Y/N)?" question comes from cmd.exe, rather than PowerShell. For example, if you have an `progs.bat` file that contains two lines ``` prog1.exe prog2.exe ``` and you run `progs.bat` and press Ctrl+C while `prog1.exe` is running, then `prog1.exe` is first terminated; after that, `cmd.exe` asks whether you want to terminate `progs.bat` as a whole or proceed to run `prog2.exe`. So, I suspect that: * Your `npm start` command runs some `npm.bat` or `npm.cmd` file, which then runs npm from its installation directory. * Your Ctrl+C has already terminated npm before the "Terminate batch job (Y/N)?" question appears. * The behavior would be the same even if VSCode, PowerShell, and Windows Terminal had not been installed.
claunia commented 2026-01-31 02:21:20 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 2, 2020):

@KalleOlaviNiemitalo is correct.

@WSLUser’s suggestion will not change this reality, and he should not be suggesting it to people who are not having console problems 😄

@DHowett commented on GitHub (Sep 2, 2020): @KalleOlaviNiemitalo is correct. @WSLUser’s suggestion will not change this reality, and he should not be suggesting it to people who are not having _console problems_ 😄
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-Question Needs-Tag-Fix Resolution-Answered
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#10426
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?