Opening repository in command prompt results in catastrophic error

Description

Unable to open repository in command prompt from the desktop app. Restarting the app results in the same error every time.

Version

1.0.12

GitHub Desktop version: 1.0.12

OS version: Windows 6.1.7601 (Windows 7 Ultimate SP1 64-bit)

Steps to Reproduce

Expected behavior: Opened in command prompt

Actual behavior: Error on the desktop app

Reproduces how often: 100%

Logs

Error: spawn where ENOENT at exports._errnoException (util.js:1050:11) at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32) at onErrorNT (internal/child_process.js:367:16) at _combinedTickCallback (internal/process/next_tick.js:80:11) at process._tickCallback (internal/process/next_tick.js:104:9)

Version: 1.0.12 OS: Windows 6.1.7601

Additional Information

[gilmae]

I’m seeing the same issue as the OP. Actually, I’ve seen it no matter what shell I opt for - Git Bash, Powershell, or Command Prompt.

Microsoft Windows [Version 10.0.16299.192] © 2017 Microsoft Corporation. All rights reserved.

C:\Users\username>where cmd ‘where’ is not recognized as an internal or external command, operable program or batch file.

C:\Users\username>echo %PATH% C:\OpenSSL-Win64\bin;C:\Program Files\Git\cmd;C:\Program Files\Git\mingw64\bin;C:\Program Files\Git\usr\bin;C:\Users\username\AppData\Local\Microsoft\WindowsApps;C:\Users\username\AppData\Local\GitHubDesktop\bin

Manual check confirms, cmd.exe is in c:\Windows\System32

The exact error message received is

Error: spawn where ENOENT at exports._errnoException (util.js:1050:11) at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32) at onErrorNT (internal/child_process.js:367:16) at _combinedTickCallback (internal/process/next_tick.js:80:11) at process._tickCallback (internal/process/next_tick.js:104:9)

Version: 1.0.13 OS: Windows 10.0.16299

[shiftkey]

@laZaru5ap thanks for the report.

The code to launch cmd is rather straightforward:

const cp = spawn('START', ['cmd'], { shell: true, cwd: path })

My gut feeling is that your PATH value isn’t configured as expected.

Could you open a command prompt, run these two commands and attach the output here:

> echo %PATH%
> where cmd

This is what it looks like on one of my developer VMs:

Microsoft Windows [Version 10.0.16299.192]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\Users\shiftkey>echo %PATH%
C:\Program Files (x86)\Parallels\Parallels Tools\Applications;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\; ...

C:\Users\shiftkey>where cmd
C:\Windows\System32\cmd.exe