{git}, {lamb} and strange new console options

[ashecorven]

Fresh download of mini or full version 1.1.3, opening cmder.exe results in {git} and {lamb} in prompt.

As per similar issues resolution- #126
Attempting to remove clink from global autorun

Doesn't have an effect that I can see.

Also new console window has some strange options

This is my first time attempting to use cmder, have never had clink installed before.

Also the installation instructions on the homepage reference cmder.bat, which is not contained in the v1.1.3 archives.

[ashecorven]

Solutions from other issues do not change the symptoms for me.

#212
prompt.lua is present in my install

#121
zip is not blocked
Ansicon has never been installed and the following key is not present: HKEY_CURRENT_USER\Software\Microsoft\Command Processor\AutoRun

Is anyone able to assist?

[ingro]

I have got the same problem too, fresh install of Cmder and got this issue. Clink is not installed on my system (it's not defined outside Cmder)... anyone have a clue?

[PterX]

I have this problem too,then it is normal today

[ashecorven]

Symptoms still present in v1.1.4

Win8.1

[ingro]

Yes it still doesn't work :(

[MartiUK]

Have you tried the 7z?

[ingro]

Yes, no luck so far :( It's strange because at work it runs flawlessy on the same OS (Win7 x64).

[ashecorven]

v1.1.4.1 reverts back to original problem.

Any updates?

[cringerjs]

Yes this is rather annoying. Any updates?

[Maeldor]

I have this exact same problem. My new console dialog options are identical to the screenshot. Win 8.1 and v1.1.4.1, too.

Any updates on a fix, please? Issue seems to be quiet 😟

[MartiUK]

Could all of you run clink in cmder and let me know if you get something similar to this:

λ clink
Clink v0.4.2 [git:1111eb] Copyright (c) 2014 Martin Ridgers`
http://mridgers.github.io/clink`

Usage: <verb> <verb_options>

  Verbs:
  inject   Injects Clink into a process.
  autorun  Manage Clink's entry in cmd.exe's autorun.
  set      Adjust Clink's settings.
           ('<verb> --help' for more details).

[ashecorven]

{lamb} clink
Clink v0.4.2 [git:1111eb] Copyright (c) 2014 Martin Ridgers
http://mridgers.github.io/clink

Usage: <verb_options>

Verbs:
inject Injects Clink into a process.
autorun Manage Clink's entry in cmd.exe's autorun.
set Adjust Clink's settings.
(' --help' for more details).

[Maeldor]

Thanks, MartiUK. Here you go:

{lamb} clink                                               
Clink v0.4.2 [git:1111eb] Copyright (c) 2014 Martin Ridgers
http://mridgers.github.io/clink                            

Usage: <verb> <verb_options>                               

  Verbs:                                                   
  inject   Injects Clink into a process.                   
  autorun  Manage Clink's entry in cmd.exe's autorun.      
  set      Adjust Clink's settings.                        
           ('<verb> --help' for more details).             

[ingro]

Here we are:

{lamb} clink --h
Clink v0.4 [git:c13aaf] Copyright (c) 2013 Martin Ridgers
http://code.google.com/p/clink

Usage: <verb_options>

Verbs:
inject Injects Clink into a process.
autorun Manage Clink's entry in cmd.exe's autorun.
set Adjust Clink's settings.
(' --help' for more details).

Copyright (c) 1994-2012 Lua.org, PUC-Rio
Copyright (c) 1987-2010 Free Software Foundation, Inc.

[twreid]

{lamb} clink
Clink v0.4.2 [git:1111eb] Copyright (c) 2014 Martin Ridgers
http://mridgers.github.io/clink

Usage: <verb_options>

Verbs:
inject Injects Clink into a process.
autorun Manage Clink's entry in cmd.exe's autorun.
set Adjust Clink's settings.
(' --help' for more details).

[sztomi]

{lamb} clink
Clink v0.4.2 [git:1111eb] Copyright (c) 2014 Martin Ridgers
http://mridgers.github.io/clink

Usage: <verb_options>

Verbs:
inject Injects Clink into a process.
autorun Manage Clink's entry in cmd.exe's autorun.
set Adjust Clink's settings.
(' --help' for more details).

[PxlBuzzard]

I am getting the same error as well (and clink is present). I installed via chocolatey which I guess could effect it somehow, I can't think of any other reason why.

[MasterOfWebM]

I am finding an interesting fix on my system. I currently have Bitdefender Internet Security, and when I disable 'Active Virus Control' the prompt returns to normal. When reactivated, it returns to the {git} and {lamb} prompts.

[ingro]

@MasterOfWebM you are a genius! Same result for me... I tried to add cmder's folder to the exluded folder list in Bitdefender config but it didn't work, the only solution seems to disable the active virus control which is not good :(

[MasterOfWebM]

@ingro So I have contacted Bitdefender support, and am currently trying to get a fix. They are having me send a bunch of stuff to them (screenshots, reports, etc.) I almost would advise others in doing this, hopefully in number we would be able to get a patch for it -- but who knows.

[ingro]

I will do the same tomorrow if I get the chance, let's hope they can fix this problem! Thanks for reporting!

[MartiUK]

I'm not surprised it's to do with AV. Hopefully you guys can white list cmder from active virus scans.

[ingro]

Well I tried to whitelist cmder with no luck... should I try with clink too? Are there other files or dll that are involved?

[nivinj]

Reporting same issue here. I've tried everything mentioned here and on #212 and #121. Is there anything else I can check / more info that I can provide?

Fresh install of cmder (full and mini) on 64-bit Windows 10 Technical Preview. Running just the built-in Windows Defender Antivirus, and already attempted disabling real-time protection.

Suggestions?

[MartiUK]

@nivinj Clink doesn't support Win10, see #279.

[nivinj]

D'oh! Thanks for that Marti.

I can confirm however that a hotfix is available at mridgers/clink#253 that fixed the issue for me.

[patrickcarlohickman]

I had the same problem. Instead of completely disabling the Active Virus Control (AVC), I was able to get it working by excluding the cmd.exe process (no other exclusions needed). Still not as secure as before, but better than completely disabling AVC.

Also, if you need some more information to pass to BitDefender, you can check out your clink.log file (C:\Users\[user]\AppData\Local\clink\clink.log), and you'll probably see something like this:

do_inject():268 -- Creating remote thread at 000000007E13F780 with parameter 0000000001FD0000
set_rl_readline_name():57 -- Setting rl_readline_name to 'cmd.exe'
hook_trap_veh():118 -- VEH hit - caller is 000000007E12D5AB.
hook_jmp():364 -- Attemping jump hook.
hook_jmp():365 -- Target is kernel32.dll, ReadConsoleW @ 0000000076EEA5E0
hook_jmp_impl():277 -- Attempting to hook at 0000000076EEA5E0 with 000007FEE9675880
hook_jmp_impl():346 -- Unable to match prolog 81B9B848
hook_jmp():371 -- Jump hook failed.
apply_hook_jmp():73 -- Unable to hook ReadConsoleW in kernel32.dll
hook_trap_veh():123 -- Hook trap 000007FEE9675C18 failed.

[ingro]

That's fair for me, thanks a lot @patrickcarlohickman !

[MasterOfWebM]

Thanks @patrickcarlohickman , I will pass that bit of information to them.

[gosukiwi]

Thanks @nivinj ! That's just the very same issue I had 😄

[psgganesh]

@torresandres that worked ;) perfect 💯 👍 Step 1 is very important before anything, Thank you once again :)

[johnkors]

@torresandres 's solution also works here. Win 8.1, BitCommander and cmder installed via Chocolatey.

[jasonwilliams]

yep @torresandres worked
Can we not just update it from here, is there a PR for this?

@Stanzilla why did you close this issue? its not fixed

[Stanzilla]

@Jayflux our latest pre release comes with the latest clink release, that's why.

[jasonwilliams]

@Stanzilla are you sure?
I downloaded 1.2.9 from the website which looks like your latest release and still had this problem.
Or is it only fixed on Github?

[Stanzilla]

@Jayflux nope, should be in 1.2.9, please make sure you delete any older files you have there before you copy the new ones in, especially the lua files have changed and having some there twice could break it.

[navkor]

yep @torresandres worked Windows 10 clean install. But you have to remove the contents of the clink vendor directory first. Then, make sure it isn't installed in programs. Then, just for good measure, I tried to run it in the Cmd just to see. And then, I extracted the zip contents into the vendor/clink folder. Then it works. It was so awesome to see! Finally!

[kruncher]

I just had the same issue after having accepted the automatic update prompt. I was able to resolve this by downloading the latest portable version of clink and the overwriting the one inside the cmder directory.

OS: Windows 7

[Gonnagle]

Like @kruncher I also just suffered the same problem when I let cmder autoupdate itself. Fixed with @torresandres solution.

OS: Windows 8.1 Enterprise (64-bit)

[Deathnerd]

I let Cmder autoupdate today and came across this issue. I've tried @torresandres solution but to no avail. I've also disabled any AV I have running and still no change. Running Windows 10 Pro 64-bit.

[Deathnerd]

Nevermind. I had two installations of cmder for some reason and applied the fix to the wrong one. All hail cmder and @torresandres!

[ghost]

Manually updating clink in the /vendor folder worked for me.

[adambotley]

+1 @mystrdat

Manually updating clink in the /vendor folder worked for me.

this solved the problem for me too

[barabator]

@torresandres Thank you for solution!

[rakete]

I just wanted to mention that it is possible to use cmder with its own clink and still have the functionality where clink injects itself into every cmd as if it was installed globally.

When clink is installed globally it creates two keys in the registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor\AutoRun
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Command Processor\AutoRun

with a string pointing to the clink.bat file that should be something like:

C:\Program Files\cmder\vendor\clink\clink.bat

so that every time a cmd is opened, that clink.bat file is executed and injects clink. Now, I assume cmder prefers to run clink itself, and the problems discussed in this issue stem from having the globally installed clink inject itself into cmder before it can inject clink on its own. So, to get clink to inject into every cmd and have cmder still work correctly, all that needs to be done is to exclude cmder when automatically injecting clink.

To do that it is possible to check if the CMDER_ROOT variable is defined and then not inject clink if it is. You can probably just edit the clink.bat, but I choose to create my own bat with something like this:

@echo off
if not defined CMDER_ROOT (
    "c:\Program Files\cmder\vendor\clink\clink_x64.exe" inject --quiet --profile "c:\Program Files\cmder\vendor\clink\profile"
)

and then put that into the AutoRun registry keys. This should give you clink injected into every cmd that is not cmder, like ConEmu or just plain cmd.exe, and still have cmder work correctly with clink.

[romaindurand]

@torresandres 's solution worked for me !

[jasonwilliams]

Can people please use the +1's on the bottom of the comments, its a bit annoying getting pinged about this thread for "me too" comments

Thanks!

[valuka]

@torresandres 's solution worked for me too.

Hopefully with next Cmder update I wont have to install Clink manually again.

[chriswithpants]

Direct link to save people hunting for that solution:
#223 (comment)

Cheers @torresandres, worked for me too.

[shrayasr]

Got an update yesterday that pushed my ConEmu up to 160619 stable and started seeing the same issue.

@torresandres' fix worked fine for me. Clink is now at version 0.4.7.

Thank you! 🎉

[vmuriart]

@rakete 's idea worked for me. I implemented it on clink.bat directly instead.

[veirus]

Super Easy Fix -- insert this into your "C:\Program Files (x86)\clink\0.4.8\clink.bat" :
if defined CMDER_ROOT goto :eof

[LordHog]

Wanted to say that @torresandres solution also worked for me