I tried to run sublime text using cmder; however did not work.
What wrong on my aliases sir?
Happens for me too. All aliases stopped working on 161206 latest stable
doskey /macros shows all aliases exist for me, they're just not usable.

Did you guys recently get the new Windows 10 Creators Update (Version 1703)? Maybe that's the issue.
I installed it yesterday and today I notice aliases doesn't work anymore (might be unrelated though).
Yes, and this failure happened after that. I tested using doskey in a standard cmd.exe window and it appears to work there. I assumed the two were related.
@Tomcat9 Yep, installed this morning
This repros for me after update to Windows 1703 as well. Worked fine yesterday with the same cmder install under Windows 1607. I'm able to use doskey to define the same macros in a regular cmd shell and they work; manually defining them using doskey in cmder as did @archer0001 they do not work.
I also tried calling doskey in user-profile.cmd with no luck either.
Setting cmd.exe to use legacy console as suggested in https://github.com/cmderdev/cmder/issues/1325 works around this.
@mollman Thank you! Am now following #1325 as well.
@Tomcat9 yes, i installed 2 days ago
@mollman Thank you, now i'm following #1325
Most helpful comment
Did you guys recently get the new Windows 10 Creators Update (Version 1703)? Maybe that's the issue.
I installed it yesterday and today I notice aliases doesn't work anymore (might be unrelated though).