cmder: It does nothing when I first run it
Purpose of the issue
- Bug report (encountered problems/errors)
- Feature request (request for new functionality)
- Question
Version Information
Cmder:
Cmder version: 1.3.17 (2020-12-23) ConEmu version: 191012 preview
Windows:
Edition: Windows 10 Pro Version: 20H2 Operating system version: 19042.746
Description of the issue
After downloading the Mini version of Cmder, I unzip the package and run Cmder.exe, but it gets stuck on the next screen:
I left it open for a while to see if it took too long, but it seems that it never ends. Then if I open another tab, nothing appears.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 1
- Comments: 26 (14 by maintainers)
Another option is to rename the
%cmder_root%\vendor\clinkfolder in 1.3.17 and copy Clink folder from 1.3.16 to%cmder_root%\vendor\clink. This may actually be the issue since the Clink version changed in 1.3.17.Ah, ok, thanks. Probably Cmder hasn’t been updated to use a newer version of Clink yet. Probably it downgraded to v1.1.10 to work around a bug while waiting for the fix that became available in v1.1.20.
Clink is on the edge of releasing an Official Release, and I imagine Cmder will update at that time.
(By the way @daxgames the latest Clink is now able to make the
clink inject --sflag take effect even if Clink is already injected. That enables Cmder to be compatible with Clink even when Clink is installed for AutoRun!)Would it be possible to rename this issue or add additional tags. I had the same problem when I downloaded the latest version this week. However it took me hours to come across this solution because google didn’t related the content to “clink” being the problem.
Thanks for your help I can finally continue my setup
That’s it, it worked by copying the
%cmder_root%\vendor\clinkfolder from the older version to the latest: