Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • 3
    Does your PATH directory contain the System32 folder? If it does, is the path really really long with other stuff too? I personally have had problems where a too long path can cause problems. Commented Jun 8, 2013 at 17:48
  • Variable "Path" contains %SystemRoot%\System32, along with a few other directories, separated by ';'. (Example: %SystemRoot%;%SystemRoot%\System32;C:\Program Files (x86)\Common Files\Ulead Systems\MPEG;etc.) Hope this helps.
    – Sampaio
    Commented Jun 8, 2013 at 19:03
  • which directory occurs in your path first? system32 or syswow64? the first element in PATH that contains an exe with the name you specify should be the instance executed. Commented Jun 8, 2013 at 19:41
  • From those two, the first would be system32, since syswow64 is not there at all. The absolute first is some "Windows Live" directory, with system32 being the second directory listed
    – Sampaio
    Commented Jun 8, 2013 at 19:56
  • 1
    What does where telnet.exe say? I just enabled the Telnet Client under Windows Features. Telnet.exe, a 64-bit program, was duly added to Windows\System32. No 32-bit version was to be found in Windows\SysWOW64. Typing telnet at the cmd prompt worked perfectly as expected. Don't know what the problem is at your end.
    – Karan
    Commented Jun 8, 2013 at 22:59