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

cmd.exe "START" cannot find file since upgrade to 1903 #6322

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

Originally created by @LRiba on GitHub (Feb 6, 2020).

I just upgraded my Windows 10 Pro system to 1903 (build 18362.356) and began experiencing a similar problem to #271, which was reported in 1809.
(The description of duplicate issue #345 is closer to what I'm seeing).

I have a batch file containing multiple commands executed as
START "" /MIN /I /D ...
Since the upgrade, they all now return

The system cannot find the file ...

Removing the /MIN does not resolve the problem.

#271 was fixed in KB4501371 for 1809; is there an update for 1903 with a similar fix?

Environment

Microsoft Windows [Version 10.0.18362.356]

Previous Environment

1803 (build 17134.1246)

Originally created by @LRiba on GitHub (Feb 6, 2020). I just upgraded my Windows 10 Pro system to 1903 (build 18362.356) and began experiencing a similar problem to [#271](https://github.com/microsoft/terminal/issues/271), which was reported in 1809. _(The description of duplicate issue [#345](https://github.com/microsoft/terminal/issues/345) is closer to what I'm seeing)._ I have a batch file containing multiple commands executed as `START "" /MIN /I /D ...` Since the upgrade, they all now return > The system cannot find the file ... Removing the `/MIN` does **not** resolve the problem. #271 was fixed in KB4501371 for 1809; is there an update for 1903 with a similar fix? # Environment Microsoft Windows [Version 10.0.18362.356] ### Previous Environment 1803 (build 17134.1246)
claunia commented 2026-01-31 00:35:46 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Mar 6, 2020):

Sorry for the delay. Are you seeing the problem in 1809 with KB4501371? I'd like to figure out if we broke this between the code we serviced to 1809 and 1903.

@DHowett-MSFT commented on GitHub (Mar 6, 2020): Sorry for the delay. Are you seeing the problem in _1809_ with KB4501371? I'd like to figure out if we broke this between the code we serviced to 1809 and 1903.
claunia commented 2026-01-31 00:35:46 +00:00
Author
Owner
Copy Link

@LRiba commented on GitHub (Mar 23, 2020):

This system never had 1809, corporate updates went directly from 1803 to 1903.
System has since updated from build 18362.356 to 18362,657, and is still expieriencing this problem.
Could/should I try installing KB4501371 anyway?

@LRiba commented on GitHub (Mar 23, 2020): This system never had 1809, corporate updates went directly from 1803 to 1903. System has since updated from build 18362.356 to 18362,657, and is still expieriencing this problem. Could/should I try installing KB4501371 anyway?
claunia commented 2026-01-31 00:35:46 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Mar 24, 2020):

KB4501371 will not help, unfortunately. We'll take up the investigation on our side.

@DHowett-MSFT commented on GitHub (Mar 24, 2020): KB4501371 will not help, unfortunately. We'll take up the investigation on our side.
claunia commented 2026-01-31 00:35:47 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Dec 6, 2021):

Sorry to be that guy, but @LRiba - is this still happening for you? I'm mot sure we ever made any code changes on our side to address this, but there also shouldn't be any cmd.exe changes at all, so it's a little troubling that this regressed in the first place.

It's been a few months, so it's entirely possible this has been fixed in the meantime. If this is still happening, we'll take another look.

Thanks!

@zadjii-msft commented on GitHub (Dec 6, 2021): Sorry to be that guy, but @LRiba - is this still happening for you? I'm mot sure we ever made any code changes on our side to address this, but there also shouldn't be any `cmd.exe` changes at all, so it's a little troubling that this regressed in the first place. It's been a few months, so it's entirely possible this has been fixed in the meantime. If this is still happening, we'll take another look. Thanks!
claunia commented 2026-01-31 00:35:47 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Dec 10, 2021):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Dec 10, 2021): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
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-Author-Feedback Needs-Tag-Fix No-Recent-Activity Priority-1 Product-Cmd.exe
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#6322
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?