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. :(