-
Notifications
You must be signed in to change notification settings - Fork 2k
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
"The system cannot find the path specified" #121
Comments
Do you get the same error when it's not in your dropbox folder? (on your Win8 PC) |
I actually always get the error on windows 8.1, regardless of whether I have cmder on dropbox or somewhere else. Many thanks for your help. |
Hi could you retry downloading cmder.7z and extract it to a folder on your desktop and let me know what happens? |
Hi, Unfortunately the same message - twice- saying that the system cannot find the path specified. Many thanks for your help. |
Have you tried running cmder.exe as Administrator? |
I installed cmder in C:\cmder on Win 8.1 Pro and I've the same problem. My Path is : |
I have the exact same Issue on Win 8.1 - Is there a solution ? |
One idea: When you download the zip file, but before extracting it, try going to the properties for the zip file and clicking the "Unblock" button. I've had problems with .exe, .bat, etc. coming from zip files where Windows blocks them to some extent unless the top-level zip is unblocked before extraction. Not sure if that's the problem here, but worth a try. I, on the other hand, always get "The system cannot find the path specified." when opening a new tab (through the New console dialog) with the "Run as administrator" box checked. The administrator console doesn't have the customized prompt (and possibly some other customizations that I haven't noticed) but otherwise works fine. |
Thank you for your reply, i tried your suggestion AND i tried to extract it with 7zip but with no success. Starting as Administrator was my first suspicion as i saw the Message, also no success. |
Hi all again, i found the Problem and i want to share that big bullsh.... Since i can remember i use Ansicon for an colored cmd.exe (PHPUnit...) in work and never had Problems or anything with it - not with Vista, not with XP and not with 7. Even now i have cmder AND Ansicon installed on my Work machine which is an Windows 7 machine - never had that strange errors. Well ... on my private coding machine with Windows 8 - ansicon dont play nice with other Programs - i had the exact same Problem with the Sublime Text - Sublimerge Plugin and i began to investigate. When you run into this "The system cannot find the path specified" Problem, have Windows 8 and ANSICON is installed - Delete the Ansicon Entries in the Registry there: HKEY_CURRENT_USER\Software\Microsoft\Command Processor\AutoRun That solved all my Problems. |
Hello, I'm using cmder on multiple machines for multiple users, so sometimes when new configuration is applied (e.g. new Windows User) it gets out of sync with Cmder's configuration. Integration options:
Solution:
Regards, |
I had the same issue, somehow the %CMDER_ROOT% was not set properly when starting with administrative rights. Without admin rights everything is ok. I ended with the solution to add a windows enivronment variable CMDER_ROOT pointing to my cmder dir. Not that beautiful, but it works. |
@danimajo - Thanks -- adding the CMDER_ROOT environment variable worked for me too. |
I followed @FreaKzero's comment on my regedit. What I actually found in the autorun entry was this:
Now the annoying error message is gone. |
No need to change anything in the regedit or anything, just go to the properties of the zip file & choose file explorer to unzip the file & unzip it with that. It didn't work with the WinRar but, File Explorer did it for me. I hope it helps. :) |
Similiar to @meeglos, my issue was related to clink, yet uses the same registry fix. Thanks @FreaKzero! For context, the reason the registry key was an issue is due to some install/uninstall/reinstall attempts I made while trying to debug an issue with clink environmental aliases not working after Windows 10 Creator update earlier this year. I eventually ended up leaving clink uninstalled because, while tab completion worked, the aliases themselves did not execute (command not recognized, etc). If I had ran a utility like ccleaner after the debugging efforts, I suspect it would have removed the offending key for me. :) Regards, |
|
Thanks dude, what a life saver ;) |
Had the same issue. Whenever I would run cmder, it would display "The system cannot find the path specified". Tried everything mentioned on this page. Nothing worked. Finally found a clue "here". But since in my case it worked differently, am describing it here. Firstly, I had to setup Secondly: In cmder goto: Settings->Integration->ComSpec I had to click on "Register ConEmu Autorun" and save settings and then the error went away. What I realized was that it was unable to launch vendor/init.bat on start of cmder console. If above does not solve your issue, try opening the vanilla console (cmd.exe .. the DOS console) and try to launch the following command and see what you get: and then take it from there. (C:\cmder is the location of cmder on my computer) |
a big round of applause for you bro ! |
Hi everyone, Line 171 in bc79847
|
same case! worked for me. |
Hi Everyone, I'm on windows 10 having the same issue, Everytime I type "cd Desktop" I get the "System cannot find the path specified" each time, Any suggestions, |
@zetaontherocks Is |
No, it's not. I'm having success with cd %userprofile%/Desktop . What shall I do ? I am a bit confused and embarrased, ha. |
@zetaontherocks you can only cd into folders with |
I have the same problem with Windows 11. I installed last version cmder. But I cannot work with him. Error "The system cannot find the path specified". Someone can help me? |
I have cmder in a folder in dropbox. Although it works fine in windows 7, when I try to execute it in my computer at home (windows 8,1), the message "the system cannot find the path specified" appears once. Moreover, the same message appears after executing a command.
The text was updated successfully, but these errors were encountered: