-
Notifications
You must be signed in to change notification settings - Fork 8.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No telnet in cmd.exe pane #6735
Comments
Can you share the output of |
Command Prompt (working) says AMD64 I've put a new pane in WT with "telnet.exe" as the "commandline" - that works |
OIC WT is running 32 bit cmd.exe |
Wow, okay, this is really strange. 1.0.1811 switched to hardcoding the location of CMD in such a way as to make this impossible. Can you share...
|
yeah, that's the weird part. That shouldn't be happening by default! 😁 |
PS C:\Users\celvi> get-appxpackage microsoft.windowsterminal Name : Microsoft.WindowsTerminal PS C:\Users\celvi> $Env:PATH |
Thanks! So, this might be weird, but can you delete |
telnet now works. Welcome to Microsoft Telnet Client Escape Character is 'CTRL+]' Microsoft Telnet> exit Invalid Command. type ?/help for help Microsoft Telnet> quit
And the dir command now finds 16 files - OK |
That line "commandline" : "cmd.exe" doesn't get refreshed when terminal closes |
Unfortunately, yeah, we have a bit of a blind spot there. I can't determine why Terminal was finding a 32-bit Can you run (from powershell): |
Windows PowerShell Try the new cross-platform PowerShell https://aka.ms/pscore6 PS C:\Users\celvi> get-command cmd.exe -all CommandType Name Version Source Application cmd.exe 10.0.18... C:\WINDOWS\system32\cmd.exe PS C:\Users\celvi> |
I have a 32-bit installation of Win10 on D: drive. Running D:\Windows\System32\cmd.exe gives processor architecture = x86 |
Thanks for all the info. I'm gonna close this as a /dupe of #6684 (PR) with a note that we need to figure out how to migrate people who are missing the updated locations. |
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! |
Environment
Steps to reproduce
type telnet in cmd.exe pane
Expected behavior
telnet prompt
Actual behavior
Microsoft Windows [Version 10.0.18363.900]
(c) 2019 Microsoft Corporation. All rights reserved.
30/06/2020@19:47:44.00 C:\Users\celvi
30/06/2020@19:47:51.46 C:\Users\celvi
Directory of C:\Windows\System32
15/05/2018 16:55
te-IN19/03/2019 05:46 107,520 telephon.cpl
19/03/2019 05:45 70,656 TempSignedLicenseExchangeTask.dll
10/06/2020 12:26 361,472 termmgr.dll
19/03/2019 05:45 61,440 tetheringclient.dll
12/09/2019 11:45 531,464 TextInputFramework.dll
12/09/2019 11:45 1,101,312 TextInputMethodFormatter.dll
6 File(s) 2,233,864 bytes
1 Dir(s) 439,855,341,568 bytes free
30/06/2020@19:48:14.31 C:\Users\celvi
In windows command prompt:
Microsoft Windows [Version 10.0.18363.900]
(c) 2019 Microsoft Corporation. All rights reserved.
30/06/2020@19:58:24.77 C:\Users\celvi
Directory of C:\Windows\System32
15/05/2018 16:55
te-IN19/03/2019 05:45 109,056 telephon.cpl
13/05/2020 18:57 138,240 TelephonyInteractiveUser.dll
21/03/2020 16:38 2,560 TelephonyInteractiveUserRes.dll
14/06/2019 03:34 130,560 telnet.exe
19/03/2019 05:44 73,728 TempSignedLicenseExchangeTask.dll
10/11/2015 07:31 85,120 tepeqapo64.dll
10/06/2020 12:26 426,496 termmgr.dll
13/05/2020 18:59 1,060,352 termsrv.dll
10/10/2019 10:47 75,264 tetheringclient.dll
10/10/2019 10:47 52,224 tetheringconfigsp.dll
19/03/2019 05:43 13,312 TetheringIeProvider.dll
21/03/2020 16:38 231,936 TetheringMgr.dll
10/10/2019 10:47 236,032 tetheringservice.dll
19/03/2019 05:43 222,208 TetheringStation.dll
21/03/2020 16:38 642,216 TextInputFramework.dll
12/02/2020 12:16 1,841,152 TextInputMethodFormatter.dll
16 File(s) 5,340,456 bytes
1 Dir(s) 439,851,257,856 bytes free
30/06/2020@19:58:47.27 C:\Users\celvi
Notice: telnet.exe is there.
In powershell pane, telnet works
The text was updated successfully, but these errors were encountered: