Cmder: Aliases do not work under Win10 1703 (Build 15063.11)

[JoaoRodrigues]

Hi all,

First of all, thanks for this amazing piece of software. It's making my life so easy when coming from MacOS..

I ran into trouble when updating to this newer build of Win 10. I am having problems with aliases or with launching the linux subsystem BASH shell. My problems have been mentioned in #1306 and #1257. If I tick the 'use legacy mode' in cmd, I lose the ability to launch a BASH shell. If I do not, my aliases do not work.

Does any one have any idea why this is happening, or a pointer to look for the root of the problem? Other aliases (e.g. ls, clear) work, so I am guessing it can be something with the loading of the alias file?

[Foxandxss]

I use the user-profile.sh for my git-for-windows aliases and they don't work either.

[Foxandxss]

On a fresh download of cmder it does work, but I lose stuff like having the branch name on the prompt. So I have to pick between one of those now.

If I update git-for-windows in the vendor. I get my branch name, I lose alias.

[AviVahl]

Verified here, and very annoyed by it.

[daxgames]

Windows insider build?

[AviVahl]

Final stable Windows 10 Creators Update... already released to insiders, yes, but exact same build will also be released to everyone else soon.

[daxgames]

Aliases worked prior to a previous Windows insider update. Not sure about this release as I am not running it. Cmder aliases for the cmd shell are based on the very old doskey macro functionality. We are somewhat at the mercy of Microsoft on this one if they break doskey then I don't know what we will do. It is probably best to wait untill an official Windows release and try then to see if they fix it.

The question I have is do doskey macros work in standard window cmd prompt window outside cmder with similar settings? If not it's not a cmder issue.

[Foxandxss]

I use Windows insider version indeed.

I am using bash:bash with git-for-windows. I had to replace it with a new version because it wasn't working that well (e.g. no branch information in the prompt).

To get my alias back, I do a source ~/path/to/cmder/config/user-profile.sh but it is not ideal.

[jrappen]

@daxgames Can reproduce this issue with the Creator's Update Assistant, which has been released today (April 5th) and installs Win10 1703 (Build 15063.13).

• Creator's Update Assistant: https://go.microsoft.com/fwlink/?linkid=845981
• https://www.microsoft.com/en-us/software-download/windows10
• https://blogs.windows.com/windowsexperience/2017/03/30/managing-windows-10-creators-update-rollout-seamless-experience/

[ingro]

Same here with the update assistant.

[jrappen]

ls and clear work fine for me as well, however e. and cmderr do not.

[phytemit]

Confirmed. I'm running Windows 10 (Creators Update) version from Update Assistant. For the aliases to start working again I needed to

but this is of course not ideal.

[xupisco]

Hi there, using legacy console works on cmd... but not with bash. :(

[mattdkerr]

As monwf just linked, this is an issue with how Clink works in the new builds of Windows. What used to work now has a bug. Not sure which side needs fixes (possibly both). If you use ConEmu separately from cmder, without Clink, Doskey should work fine.

[JoaoRodrigues]

@phytemit Yes, that is a workaround, but as I mentioned in the original post, then you cannot launch the BASH shell (WSL).

The workaround mentioned in the thread linked by @MonwF (link) could work but seems a bit cumbersome?

[bitcrazed]

Hi. Microsoft PM for Bash/Console/Cmd here.

Thanks for looping us into the thread - will take a look and get back to y'all ASAP.

[bitcrazed]

Update: We are tracking this issue internally (bug 11524988 for future reference).

Also related to Clink issue 438: https://github.com/mridgers/clink/issues/438

Bear with us while we work through the process.

[bannus]

If you want to go with the .cmd files for each alias workaround, you can use this powershell snippet.

[jrappen]

@bitcrazed Do you have more info whether or not MSFT will fix this on their end, and maybe a timeframe?

[corstar]

Glad to see this is a recent issue that people are working on. Looking forward to a working result.
Using win 10, creaters update here.

[J4r3tt]

Hope this issue can be fixed asap,thanks for hard working

[ghost]

Yep, my version is 1703, i have the same promblem too :( Thats too bad and this problem makes me want to back to win7 :p

[bitcrazed]

@corstar No ETA yet - we're currently slammed getting feature work completed for the next OS release. Will take a look when we move onto bugs in a couple of weeks.

[jrappen]

@bitcrazed So that means MSFT won't be fixing this in a patch via Windows Update and we should use work-arounds until a major release in October or even April next year?

[AviVahl]

@bitcrazed we'll be able to give you instant feedback if a fix lands in an Insider build or a KB fix.
Thanks for the update! Much appreciated.

[alexgs]

Using @phytemit's work-around is effective for me with the exception of "nested" alias. For example, my old aliases included ls=ls --show-control-chars -F --color $* and ll=ls -al. After enabling the legacy console, doing ll did not pick up the --color option defined on the "ls" alias. It's easy enough to fix by updating "ll" to ll=ls --show-control-chars -F --color -alh $*.

Just thought I'd mention it in case someone gets stuck! 😺

[nonsocode]

Mine started working again this morning. When i opened cmder I got this message

Clink v0.4.8 [git:d565ad] Copyright (c) 2012-2016 Martin Ridgers
http://mridgers.github.io/clink

Now all aliases seem to be working just fine and i can also use bash in cmder

[Foxandxss]

Not for me. Perhaps I broke it while trying stuff.

Let's see what other people say.

[Gelio]

It doesn't work for me either. I didn't get that message. Upon opening Cmder I got the usual ssh-agent starting.

I don't see why it would start working now. Was there an Insiders Build Windows update? As far as I can tell there hasn't been an update for Cmder recently as well.

@nonsocode Did you do anything the previous day that would fix aliases?

[seancheung]

This should be a temporary solution.
After enabling legacy console support, Ubuntu on Windows no longer works.

Unsupported console settings. In order to use this feature the legacy console must be disabled.
Press any key to continue...

[cmeza]

I'm not using WSL & have thoroughly enjoyed working with cmder, so enable legacy console support for me it is using @phytemit fix.

[Aristona]

I had problems with opening Console Properties, it was crashing after the update. If you need to change to legacy version, you can open regedit and go to HKEY_CURRENT_USER\Console.

Change the value of "ForceV2" to 00000000

[Justsoos]

Same problems, I had to shift to Bash on linux on Win 10, more regular bash command environment, and real alias controlled by ~/.bashrc (Ubuntu bash). Seems the arrogance and abduction of M$ pushed us to that.

root@DESKTOP-PMQ6DR3:~# uname -a
Linux DESKTOP-PMQ6DR3 4.4.0-43-Microsoft #1-Microsoft Wed Dec 31 14:42:53 PST 2014 x86_64 x86_64 x86_64 GNU/Linux

and DO remember, if your ubuntu bash version is lower than 16.0, such as 14.04.5 LTS, it was totally out-of-date, you must update to 16.04 up, do not try to upgrade with sudo do-release-upgrade, even though it is officially recommended by M$ , there are bugs of it.

Just uninstall with lxrun /uninstall, then run lxrun /install to get the 16.04 up version.
you can also access M$ file system in bash with this edition as cmder, and so on.

root@DESKTOP-PMQ6DR3:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 16.04.3 LTS
Release:        16.04
Codename:       xenial

[CraneJen]

@phytemit It worked!!

[Beej126]

linking to the Clink fix for this

[Justsoos]

https://github.com/cmderdev/cmder/issues/1325#issuecomment-292480901
change cmd of win 10 to legacy console mode will lead to broken of bash linux on win 10:
Unsupported console settings. In order to use this feature the legacy console must be disabled.

[hzhu212]

A new version of Cmder has been available : Cmder Release

I was surprised to find that the user-alias.cmd could function normally again!

So, No Need to Set CMD Legacy Mode Any More

[jpotma]

The new version (1.3.4) does fix the issue. just extract over your previous install folder and that fixed the issue for me.

[necoli1822]

Don`t know it is the case of yours, but in my case, the whole wsl colour theme gone after writing ".bash_profile" in the root folder.
After I removed ".bash_profile", the color of [user@machine] and also color theme of commend 'ls' recovered.

[bitcrazed]

~/.bash_profile loads ~/.profile which loads ~/.bashrc which is where your bash colors etc. are configured.

So if you overwrite ~/.bash_profile, you'll prevent the above from happening and your color settings won't be loaded & applied.