Skip to content
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

Windows: Command Prompt is renamed "Jack Command" on installation of JACK #303

Open
shoogle opened this issue Oct 30, 2017 · 4 comments
Open
Labels
build un/install Related to building releases on several platforms Windows Bug or feature related to using JACK on Windows

Comments

@shoogle
Copy link

shoogle commented Oct 30, 2017

I'm also getting this issue, which @thejsa accidentally reported at jackaudio/jack1#48.

Hiya,
I installed JACK 1.9.10 x64 on Windows 10 Pro x64 (Build 14393 / Anniversary Update) but was quite shocked to discover that the Command Prompt had been replaced by Jack Command (including on my Start menu and Start tiles), and that the default working directory was changed to the JACK installation folder.
Instead of userping CMD, could you instead change the shortcut to point to a batch script which sets the working directory and PATH, etc.?

I'm running Jack 1.9.10 on fully up-to-date Windows 10 Home x64 with Fall Creators Update.

@shoogle
Copy link
Author

shoogle commented Dec 26, 2017

UPDATE: This appears to be a Windows 10 issue rather than a JACK issue. All JACK does is create a shortcut to cmd.exe that's set to start in "C:\Program Files\Jack". The original "Command Prompt" shortcut is still there, but it is no longer displayed in the Start menu because of this issue with Windows 10.

Workaround:
Until Microsoft fixes the underlying issue, the best thing to do is simply delete (or hide) the "Jack Command" shortcut in Windows 10:

  1. Open the Start menu and search for "cmd"
  2. If the result is "Command Prompt" or "cmd.exe" then the bug is fixed - you can stop here!
  3. If the result is "Jack Command" then right-click on it and go to "Open file location".
  4. Delete the "Jack Command" shortcut (or set it to hidden via right-click Properties).

This will restore access to CMD. The Jack developers may want to consider disabling the creation of the "Jack Command" shortcut on Windows 10 until Microsoft fixes the bug.

@7890 7890 added Windows Bug or feature related to using JACK on Windows build un/install Related to building releases on several platforms labels Jan 14, 2019
@tobygf
Copy link

tobygf commented May 11, 2019

I also noticed this issue: I figured it was nothing to worry about, and indeed it has been resolved after I uninstalled Jack for unrelated reasons. I have noticed, though, that when I search for "jack" in Start it now comes up with Command Prompt—is there any way to remove this association?

@shoogle
Copy link
Author

shoogle commented May 11, 2019

I'm afraid I can't help there @tobygf, but this SuperUser answer gives possible way for Jack to avoid the problem arising in the first place: create a symlink or hard link to CMD and then create a shortcut to the symlink. (Of course, it would be nice if Microsoft would just fix the issue with the Start Menu so that it wouldn't be necessary to use workarounds like this.)

@danellisuk
Copy link

I had "Jack Command" showing instead of "Command" in my start menu. After updating to Windows 10 release 1909, the original "Command" shortcut has been restored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build un/install Related to building releases on several platforms Windows Bug or feature related to using JACK on Windows
Projects
None yet
Development

No branches or pull requests

4 participants