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

PATH commands not working lonely. #20161

New Issue
Closed
opened 2026-01-31 07:05:25 +00:00 by claunia · 8 comments
claunia commented 2026-01-31 07:05:25 +00:00
Owner
Copy Link

Originally created by @rvneXe on GitHub (Jun 28, 2023).

Windows Terminal version

1.17.11461.0

Windows build number

10.0.19043.0

Other Software

No response

Steps to reproduce

I opened the terminal, typed "ping" command, then got this error:

PS C:\Windows\system32> ping
ping : The term 'ping' is not recognized as the name of a cmdlet, function, script file, or operable program. Check
the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ ping
+ ~~~~
    + CategoryInfo          : ObjectNotFound: (ping:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException


Suggestion [3,General]: The command ping was not found, but does exist in the current location. Windows PowerShell does not load commands from the current location by default. If you trust this command, instead type: ".\ping". See "get-help about_Command_Precedence" for more details.

So, I have to use ".\ping" for it to work.
I've tested it with PowerShell and cmd.exe themselves and PATH commands are working fine, But they have issues in the windows terminal

Expected Behavior

The "ping" command itself (without dot and backslash) should work as a command too.

Actual Behavior

The error that I mentioned it earlier.

Originally created by @rvneXe on GitHub (Jun 28, 2023). ### Windows Terminal version 1.17.11461.0 ### Windows build number 10.0.19043.0 ### Other Software _No response_ ### Steps to reproduce I opened the terminal, typed "ping" command, then got this error: ``` PS C:\Windows\system32> ping ping : The term 'ping' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1 + ping + ~~~~ + CategoryInfo : ObjectNotFound: (ping:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException Suggestion [3,General]: The command ping was not found, but does exist in the current location. Windows PowerShell does not load commands from the current location by default. If you trust this command, instead type: ".\ping". See "get-help about_Command_Precedence" for more details. ``` So, I have to use ".\ping" for it to work. I've tested it with PowerShell and cmd.exe themselves and PATH commands are working fine, But they have issues in the windows terminal ### Expected Behavior The "ping" command itself (without dot and backslash) should work as a command too. ### Actual Behavior The error that I mentioned it earlier.
claunia added the Needs-TriageIssue-BugNeeds-Attention labels 2026-01-31 07:05:25 +00:00
claunia commented 2026-01-31 07:05:26 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Jun 28, 2023):

What does your $env variable in PowerShell contain? You can strip out anything that you consider private data.

@lhecker commented on GitHub (Jun 28, 2023): What does your `$env` variable in PowerShell contain? You can strip out anything that you consider private data.
claunia commented 2026-01-31 07:05:26 +00:00
Author
Owner
Copy Link

@rvneXe commented on GitHub (Jul 1, 2023):

Name                           Value
----                           -----
ACSetupSvcPort                 23210
ACSvcPort                      17532
ALLUSERSPROFILE                C:\ProgramData
APPDATA                        C:\Users\Raven\AppData\Roaming
CommonProgramFiles             C:\Program Files\Common Files
CommonProgramFiles(x86)        C:\Program Files (x86)\Common Files
CommonProgramW6432             C:\Program Files\Common Files
COMPUTERNAME                   DESKTOP-FAU54K4
ComSpec                        C:\Windows\system32\cmd.exe
DriverData                     C:\Windows\System32\Drivers\DriverData
HOMEDRIVE                      C:
HOMEPATH                       \Users\Raven
INTEL_DEV_REDIST               C:\Program Files (x86)\Common Files\Intel\Shared Libraries\
JAVA_HOME                      X:\Program Files\jdk-17.0.2
LOCALAPPDATA                   C:\Users\Raven\AppData\Local
LOGONSERVER                    \\DESKTOP-FAU54K4
MIC_LD_LIBRARY_PATH            C:\Program Files (x86)\Common Files\Intel\Shared Libraries\compiler\lib\mic
NUMBER_OF_PROCESSORS           8
OS                             Windows_NT
Path                           C:\Users\Raven\AppData\Local\Microsoft\WindowsApps;C:\Users\Raven\AppData\Local\GitHu...
PATHEXT                        .COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC;.PY;.PYW;.CPL
PROCESSOR_ARCHITECTURE         AMD64
PROCESSOR_IDENTIFIER           Intel64 Family 6 Model 165 Stepping 3, GenuineIntel
PROCESSOR_LEVEL                6
PROCESSOR_REVISION             a503
ProgramData                    C:\ProgramData
ProgramFiles                   C:\Program Files
ProgramFiles(x86)              C:\Program Files (x86)
ProgramW6432                   C:\Program Files
PSModulePath                   C:\Users\Raven\Documents\WindowsPowerShell\Modules;C:\Program Files\WindowsPowerShell...
PUBLIC                         C:\Users\Public
RlsSvcPort                     22112
SystemDrive                    C:
SystemRoot                     C:\Windows
TEMP                           C:\Users\Raven\AppData\Local\Temp
TMP                            C:\Users\Raven\AppData\Local\Temp
USERDOMAIN                     DESKTOP-FAU54K4
USERDOMAIN_ROAMINGPROFILE      DESKTOP-FAU54K4
USERNAME                       Raven
USERPROFILE                    C:\Users\Raven
windir                         C:\Windows
WSLENV                         WT_SESSION::WT_PROFILE_ID
WT_PROFILE_ID                  {61c54bbd-c2c6-5271-96e7-009a87ff44bf}
WT_SESSION                     43d8e0e5-7679-43f3-9943-1654f11e5fc9
@rvneXe commented on GitHub (Jul 1, 2023): ``` Name Value ---- ----- ACSetupSvcPort 23210 ACSvcPort 17532 ALLUSERSPROFILE C:\ProgramData APPDATA C:\Users\Raven\AppData\Roaming CommonProgramFiles C:\Program Files\Common Files CommonProgramFiles(x86) C:\Program Files (x86)\Common Files CommonProgramW6432 C:\Program Files\Common Files COMPUTERNAME DESKTOP-FAU54K4 ComSpec C:\Windows\system32\cmd.exe DriverData C:\Windows\System32\Drivers\DriverData HOMEDRIVE C: HOMEPATH \Users\Raven INTEL_DEV_REDIST C:\Program Files (x86)\Common Files\Intel\Shared Libraries\ JAVA_HOME X:\Program Files\jdk-17.0.2 LOCALAPPDATA C:\Users\Raven\AppData\Local LOGONSERVER \\DESKTOP-FAU54K4 MIC_LD_LIBRARY_PATH C:\Program Files (x86)\Common Files\Intel\Shared Libraries\compiler\lib\mic NUMBER_OF_PROCESSORS 8 OS Windows_NT Path C:\Users\Raven\AppData\Local\Microsoft\WindowsApps;C:\Users\Raven\AppData\Local\GitHu... PATHEXT .COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC;.PY;.PYW;.CPL PROCESSOR_ARCHITECTURE AMD64 PROCESSOR_IDENTIFIER Intel64 Family 6 Model 165 Stepping 3, GenuineIntel PROCESSOR_LEVEL 6 PROCESSOR_REVISION a503 ProgramData C:\ProgramData ProgramFiles C:\Program Files ProgramFiles(x86) C:\Program Files (x86) ProgramW6432 C:\Program Files PSModulePath C:\Users\Raven\Documents\WindowsPowerShell\Modules;C:\Program Files\WindowsPowerShell... PUBLIC C:\Users\Public RlsSvcPort 22112 SystemDrive C: SystemRoot C:\Windows TEMP C:\Users\Raven\AppData\Local\Temp TMP C:\Users\Raven\AppData\Local\Temp USERDOMAIN DESKTOP-FAU54K4 USERDOMAIN_ROAMINGPROFILE DESKTOP-FAU54K4 USERNAME Raven USERPROFILE C:\Users\Raven windir C:\Windows WSLENV WT_SESSION::WT_PROFILE_ID WT_PROFILE_ID {61c54bbd-c2c6-5271-96e7-009a87ff44bf} WT_SESSION 43d8e0e5-7679-43f3-9943-1654f11e5fc9 ```
claunia commented 2026-01-31 07:05:26 +00:00
Author
Owner
Copy Link

@zadjii commented on GitHub (Jul 1, 2023):

Can you try the 1.18 Preview build? That fairly substantially changed up how Terminal loads the environment

@zadjii commented on GitHub (Jul 1, 2023): Can you try the 1.18 Preview build? That fairly substantially changed up how Terminal loads the environment
claunia commented 2026-01-31 07:05:27 +00:00
Author
Owner
Copy Link

@anuraghit commented on GitHub (Jul 1, 2023):

it's not working also

@anuraghit commented on GitHub (Jul 1, 2023): it's not working also
claunia commented 2026-01-31 07:05:27 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 5, 2023):

What does the output of $env:Path look like/? Weird that this works in pwsh in conhost but not Terminal. My only theory is that Terminal's launching with different env vars.

(but also if 1.18 doesn't work then that doesn't seem likely either.... hmm...)

@zadjii-msft commented on GitHub (Jul 5, 2023): What does the output of `$env:Path` look like/? Weird that this works in pwsh in conhost but not Terminal. My only theory is that Terminal's launching with different env vars. (but also if 1.18 doesn't work then that doesn't seem likely either.... hmm...)
claunia commented 2026-01-31 07:05:27 +00:00
Author
Owner
Copy Link

@ALERTua commented on GitHub (Jul 5, 2023):

Same here.
C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.18.1462.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe

C:\Users\alexe>set
ALLUSERSPROFILE=C:\ProgramData
APPDATA=C:\Users\alexe\AppData\Roaming
ChocolateyInstall=C:\ProgramData\chocolatey
ChocolateyLastPathUpdate=133327802124098935
ChocolateyToolsLocation=C:\tools
CommonProgramFiles=C:\Program Files\Common Files
CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files
CommonProgramW6432=C:\Program Files\Common Files
COMPUTERNAME=ALERT_WHITE
ComSpec=C:\WINDOWS\system32\cmd.exe
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.JS;.WS;.MSC
PROMPT=$P$G

C:\Users\alexe>

In the meantime: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.17.11461.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe displays the environment variables in full scale, correcty.

@ALERTua commented on GitHub (Jul 5, 2023): Same here. `C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.18.1462.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe` ``` C:\Users\alexe>set ALLUSERSPROFILE=C:\ProgramData APPDATA=C:\Users\alexe\AppData\Roaming ChocolateyInstall=C:\ProgramData\chocolatey ChocolateyLastPathUpdate=133327802124098935 ChocolateyToolsLocation=C:\tools CommonProgramFiles=C:\Program Files\Common Files CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files CommonProgramW6432=C:\Program Files\Common Files COMPUTERNAME=ALERT_WHITE ComSpec=C:\WINDOWS\system32\cmd.exe PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.JS;.WS;.MSC PROMPT=$P$G C:\Users\alexe> ``` In the meantime: `C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.17.11461.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe` displays the environment variables in full scale, correcty.
claunia commented 2026-01-31 07:05:27 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Jul 9, 2023):

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.

@microsoft-github-policy-service[bot] commented on GitHub (Jul 9, 2023): 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**.
claunia commented 2026-01-31 07:05:28 +00:00
Author
Owner
Copy Link

@rvneXe commented on GitHub (Jul 12, 2023):

Can you try the 1.18 Preview build? That fairly substantially changed up how Terminal loads the environment

Yeah, It Works.
Thanks

@rvneXe commented on GitHub (Jul 12, 2023): > Can you try the 1.18 Preview build? That fairly substantially changed up how Terminal loads the environment Yeah, It Works. Thanks
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-Attention Needs-Triage
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#20161
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?