1

I installed the Windows telnet client (telnet.exe) on Windows 8 Enterprise Edition (RTM - fresh install) via Turn Windows features on or off. However I can't seem to launch it from an Administrator command prompt.

I did a full search of the C: drive and can see the executable residing in C:\Windows\System32:

telnet search result

I can also see the executable in explorer:

telnet in explorer

In both of the above cases I can launch the client by double clicking but for some reason it's not visible in my Administrator cmd.exe command prompt (or PowerShell for that matter):

run telnet in cmd result

Also, as you can see in the above screenshot, C:\Windows\system32 is present and correct in my PATH environment variable. Other system executables launch just fine (tasklist.exe for example).

For reasons that are too long winded to explain I can't use a third party telnet client such as PuTTY.

Can anyone shed any light on why this is happening?

I also tried a reboot but that's not helped either.

phuclv
  • 30,396
  • 15
  • 136
  • 260
Kev
  • 2,339

3 Answers3

2

This is because of the file system redirector. A 32-bit process won't see the real Windows\System32 folder but get the content of the substituted Windows\SysWOW64 instead

To get it work on 32-bit cmd.exe or any 32-bit shells you can run

cd %windir%\Sysnative\

to change the working directory to that real System32 folder and then run telnet normally. Or just run %windir%\Sysnative\telnet directly to open 64-bit telnet.exe

Another way is to force open 64-bit cmd.exe from a 32-bit process (like ViStart) by modifying the invoking command or shortcut to %windir%\Sysnative\cmd.exe

Alternatively just copy (or create a hardlink) the telnet.exe file from System32 to SysWOW64

You can also add %windir%\Sysnative to the %PATH% environment variable after %windir%\System32 so that after checking that the file doesn't exist in System32 it'll continue looking in Sysnative

phuclv
  • 30,396
  • 15
  • 136
  • 260
1

This is most likely a side effect of PendingRenames, Windows Explorer is so new that it makes sure it shows you the latest state taking pending renames int account whereas Command Prompt is so old that it natively reads the drive and thus does not see the renamed files yet. Usually they are first installed to a temporary unpacked location and then later renamed to be at the actual location.

My guess is that you have done Turn Windows features on or off. without rebooting your computer, thus it still has to finish off the installation of the features by doing the actual renames such that you can actually use telnet from the command prompt.

Thus, the simple "have you tried to turn it on and off again?" approach should solve this.

Tamara Wijsman
  • 57,881
1

I finally got to the bottom of this. I had installed ViStart after becoming increasingly frustrated with the new Windows 8 Modern UI and which is particularly tricky to use over a Remote Desktop Connection.

I was using ViStart to do my usual muscle memory Start->Run->cmd.exe as I would on Windows 7. However, it turns out that ViStart is a 32-bit application and launches a 32-bit command prompt. Of course, this command prompt being 32-bit can't see telnet.exe because it's a 64-bit exe etc.

I have since given up on ViStart as a bad idea and have resigned myself to learn to navigate Modern UI instead.

Kev
  • 2,339