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

Terminal closes on startup due to "specified command or file was not found" in Powershell #7742

New Issue
Open
opened 2026-01-31 01:11:38 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 01:11:38 +00:00
Owner
Copy Link

Originally created by @izackp on GitHub (Apr 28, 2020).

WindowsTerminal_2020-04-27_23-44-14

Environment

Win32NT 10.0.18363.0 Microsoft Windows NT 10.0.18363.0
I can find no startup scripts for powershell

Steps to reproduce

Open Windows Terminal

Expected behavior

See Terminal and a powershell tab

Actual behavior

Powershell reports an error, returns 0, then instantly closes the entire app. It shows the error:

Could not execute because the specified command or file was not found.
Possible reasons for this include:

  • You misspelled a built-in dotnet command.
  • You intended to execute a .NET Core program, but dotnet-C:\Users\Isaac does not exist.
  • You intended to run a global tool, but a dotnet-prefixed executable with this name could not be found on the PATH.

I think its because there is a space in my windows username. However, I have no idea why powershell is trying to execute a command on start up in the first place. Everything seems to start up fine when I open powershell outside of windows terminal. I'm not really sure how to further diagnose this issue. It took a while just to figure out how to keep windows terminal from closing (running wt.exe with bad parameters let me run it and keep it from closing).

Either way, powershell instantly shutting down the app is a bad user experience.

Originally created by @izackp on GitHub (Apr 28, 2020). ![WindowsTerminal_2020-04-27_23-44-14](https://user-images.githubusercontent.com/2636382/80444976-1f28ad00-88e1-11ea-8284-d313865393e3.png) # Environment Win32NT 10.0.18363.0 Microsoft Windows NT 10.0.18363.0 I can find no startup scripts for powershell # Steps to reproduce Open Windows Terminal # Expected behavior See Terminal and a powershell tab # Actual behavior Powershell reports an error, returns 0, then instantly closes the entire app. It shows the error: Could not execute because the specified command or file was not found. Possible reasons for this include: * You misspelled a built-in dotnet command. * You intended to execute a .NET Core program, but dotnet-C:\Users\Isaac does not exist. * You intended to run a global tool, but a dotnet-prefixed executable with this name could not be found on the PATH. I think its because there is a space in my windows username. However, I have no idea why powershell is trying to execute a command on start up in the first place. Everything seems to start up fine when I open powershell outside of windows terminal. I'm not really sure how to further diagnose this issue. It took a while just to figure out how to keep windows terminal from closing (running wt.exe with bad parameters let me run it and keep it from closing). Either way, powershell instantly shutting down the app is a bad user experience.
claunia added the Issue-QuestionNeeds-Tag-FixResolution-Answered labels 2026-01-31 01:11:38 +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 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#7742
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?