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

Terminal Preview suddenly not working when there are spaces in executables path #19014

New Issue
Closed
opened 2026-01-31 06:31:11 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 06:31:11 +00:00
Owner
Copy Link

Originally created by @alex-sandro92 on GitHub (Dec 5, 2022).

Windows Terminal version

1.16.2642.0

Windows build number

25252.1010

Other Software

No response

Steps to reproduce

Open a profile whose executable contains spaces in its path.
I was not having this issue until yesterday, when I installed latest Windows cumulative update (10.0.25252.1010).

Expected Behavior

I expect to open a profile and launch its command line.

Actual Behavior

I get the following error if the executable contains spaces in its path (PS7 is just an example):

[error 2147942593 (0x800700c1) when launching D:\Program Files\PowerShell\7\pwsh.exe']`

If the executable has no spaces in its path the command line starts correctly.

Originally created by @alex-sandro92 on GitHub (Dec 5, 2022). ### Windows Terminal version 1.16.2642.0 ### Windows build number 25252.1010 ### Other Software _No response_ ### Steps to reproduce Open a profile whose executable contains spaces in its path. I was not having this issue until yesterday, when I installed latest Windows cumulative update (10.0.25252.1010). ### Expected Behavior I expect to open a profile and launch its command line. ### Actual Behavior I get the following error if the executable contains spaces in its path (PS7 is just an example): `[error 2147942593 (0x800700c1) when launching `D:\Program Files\PowerShell\7\pwsh.exe']` If the executable has no spaces in its path the command line starts correctly.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 06:31:11 +00:00
claunia commented 2026-01-31 06:31:12 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Dec 5, 2022):

Thanks for the report! Can you share your settings.json file?

@DHowett commented on GitHub (Dec 5, 2022): Thanks for the report! Can you share your `settings.json` file?
claunia commented 2026-01-31 06:31:12 +00:00
Author
Owner
Copy Link

@alex-sandro92 commented on GitHub (Dec 7, 2022):

Thanks for the report! Can you share your settings.json file?

settings.zip

Profiles affected are the ones with spaces in the executable path:

  1. Powershel 7.3.0 (stable and preview)
  2. Git
  3. Adb (which uses PS7)
  4. Steamcmd
@alex-sandro92 commented on GitHub (Dec 7, 2022): > Thanks for the report! Can you share your `settings.json` file? [settings.zip](https://github.com/microsoft/terminal/files/10175133/settings.zip) Profiles affected are the ones with spaces in the executable path: 1. Powershel 7.3.0 (stable and preview) 2. Git 3. Adb (which uses PS7) 4. Steamcmd
claunia commented 2026-01-31 06:31:12 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Dec 7, 2022):

Hi @alex-sandro92. Do you have a file D:\Program?

We've hit a few of these in the past, so I'm dupping this: /dup #11717

@carlos-zamora commented on GitHub (Dec 7, 2022): Hi @alex-sandro92. Do you have a file `D:\Program`? We've hit a few of these in the past, so I'm dupping this: /dup #11717
claunia commented 2026-01-31 06:31:12 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Dec 7, 2022):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Dec 7, 2022): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
claunia commented 2026-01-31 06:31:13 +00:00
Author
Owner
Copy Link

@alex-sandro92 commented on GitHub (Dec 8, 2022):

Hi @alex-sandro92. Do you have a file D:\Program?

We've hit a few of these in the past, so I'm dupping this: /dup #11717

That was the problem, thanks!
That file was created by a monitoring software for my ups

@alex-sandro92 commented on GitHub (Dec 8, 2022): > Hi @alex-sandro92. Do you have a file `D:\Program`? > > We've hit a few of these in the past, so I'm dupping this: /dup #11717 That was the problem, thanks! That file was created by a monitoring software for my ups
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 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#19014
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?