Cmder: Problem with environment variables that contain parentheses

Created on 12 Jan 2017  路  1Comment  路  Source: cmderdev/cmder

When using cmder for working with visual studio 2013, the following error raises:

\Microsoft was unexpected at this time.

and the console, yet still functional, behaves as a standard dos shell.

This problem seems to be related to adding the following line (with the parentheses) to the path environmental variable:

C:\Program Files (x86)\Microsoft Visual Studio 12.0...

This problem is already reported for general shell scripts :

https://support.microsoft.com/en-us/kb/2524009

picture oeolartep

Most helpful comment

I was getting this error message only in cmder and not in a standard cmd shell, so I thought it was related to the init scripts of conemu/cmder, but I just found that the problem was having PATH鈥檚 members enclosed in double quotes:

http://www.blinnov.com/en/2010/06/04/microsoft-was-unexpected-at-this-time/

I just removed the double quotes in the problematic path member and cmder start working again.

I will close the issue.

picture oeolartep on 12 Jan 2017
👍5

>All comments

I was getting this error message only in cmder and not in a standard cmd shell, so I thought it was related to the init scripts of conemu/cmder, but I just found that the problem was having PATH鈥檚 members enclosed in double quotes:

http://www.blinnov.com/en/2010/06/04/microsoft-was-unexpected-at-this-time/

I just removed the double quotes in the problematic path member and cmder start working again.

I will close the issue.

oeolartep picture oeolartep on 12 Jan 2017
👍5
Was this page helpful?
0 / 5 - 0 ratings

Related issues

danwellman picture danwellman  路  3Comments
AaronKaa picture AaronKaa  路  3Comments
jenisys picture jenisys  路  3Comments
giuliannosbrugnera picture giuliannosbrugnera  路  3Comments
sathishsoundharajan picture sathishsoundharajan  路  3Comments