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

cmd.exe start /d not working with /min #1186

New Issue
Closed
opened 2026-01-30 22:18:22 +00:00 by claunia · 1 comment
claunia commented 2026-01-30 22:18:22 +00:00
Owner
Copy Link

Originally created by @eeflores on GitHub (May 17, 2019).

Environment

Windows build number: 10.0.17763.475

Other software: Elasticsearch 6.7.0 using Java 1.8.0_172, but the behavior was 
confirmed with a test batch file and executable.

Steps to reproduce

When testing the functionality of the start command within the cmd.exe shell, I found that having the /min parameter would affect the /d parameter: the path provided to the /d parameter did not seem to be acknowledged, and the command passed to the start command would not be found.

Test example:

  • Command shell with prompt at C:\temp
  • A test batch file at C:\temp\testdir\test.bat, with the content
@echo hello
pause
  • Running the following command would succeed:
    C:\temp>start /d c:\temp\testdir test.bat
  • The following command would not succeed:
    C:\temp>start /min /d c:\temp\testdir test.bat
  • If the path is set to C:\temp\testdir the following command would succeed:
    C:\temp\testdir>start /min test.bat

The use of the /d and /min parameter together was previously working, and was required functionality for a commercial product.

I'm wondering if this problem is related to #271 .

Expected behavior

The /d parameter to be parsed when the /min parameter is also included to the start command.

Actual behavior

If the /min parameter is used with the /d parameter, the path used with the /d parameter does not seem to be used, and the program contained in the path referenced by the /d parameter is not found.

Originally created by @eeflores on GitHub (May 17, 2019). <!-- 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. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: 10.0.17763.475 Other software: Elasticsearch 6.7.0 using Java 1.8.0_172, but the behavior was confirmed with a test batch file and executable. ``` # Steps to reproduce When testing the functionality of the `start` command within the `cmd.exe` shell, I found that having the `/min` parameter would affect the `/d` parameter: the path provided to the `/d` parameter did not seem to be acknowledged, and the command passed to the `start` command would not be found. Test example: * Command shell with prompt at `C:\temp` * A test batch file at `C:\temp\testdir\test.bat`, with the content ``` @echo hello pause ``` * Running the following command would succeed: `C:\temp>start /d c:\temp\testdir test.bat` * The following command would not succeed: `C:\temp>start /min /d c:\temp\testdir test.bat` * If the path is set to `C:\temp\testdir` the following command would succeed: `C:\temp\testdir>start /min test.bat` The use of the `/d` and `/min` parameter together was previously working, and was required functionality for a commercial product. I'm wondering if this problem is related to #271 . # Expected behavior The `/d` parameter to be parsed when the `/min` parameter is also included to the `start` command. # Actual behavior If the `/min` parameter is used with the `/d` parameter, the path used with the `/d` parameter does not seem to be used, and the program contained in the path referenced by the `/d` parameter is not found.
claunia added the Resolution-DuplicateProduct-Cmd.exe labels 2026-01-30 22:18:22 +00:00
claunia commented 2026-01-30 22:18:23 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 17, 2019):

This is a duplicate of #271.

@DHowett-MSFT commented on GitHub (May 17, 2019): This is a duplicate of #271.
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 Product-Cmd.exe 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#1186
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?