install on win7 enterprise, can't modify bash start up shortcut

Corinna Vinschen
Fri Aug 19 19:36:00 GMT 2011

On Aug 19 21:19, Csaba Raduly wrote:
> On Fri, Aug 19, 2011 at 8:31 PM, LMH  wrote:
> (Please don't top-post)
> > I've had no issue with re-sizing the bash window in the past and having
> > those changes saved to the shortcut, even on win7 ent, so I am concerned
> > about the health of the install.
> The health of the Cygwin install should be unrelated. I gues  this is
> some Windows-y permission issue.
> The shortcut points to cygwin.bat; Windows runs cmd.exe to interpret
> the batch file, which eventually starts bash.
> >The desktop icon points to Cygwin.bat, but
> > that doesn't have anything in it about the bash shell. Can someone point me
> > to the ini file where the specs of the bash window would be recorded?
> That window belongs to cmd.exe;

No, not really.  Cmd is a shell, like bash.  Up to Windows Vista and
Server 2008, the console itself was implemented as just a bunch of
library functions and a shared core in the csrss process.  Start bash
from Explorer, and in Task Manager you will see that no cmd is running.

Starting with Windows 7 and Server 2008 R2, the console window is
implemented as a standalone application called conhost.exe.  So, if you
start bash from explorer in W7, you will not only see bash, but also an
additional conhost process.  So, in a way conhost is the same as mintty,
a terminal emulator, even if not a good one.

Either way, that's a common misunderstanding of the way the Windows
console works.  It was never cmd.  Cmd is and always was only a shell,
just another console application like bash.

I hope it goes without saying why you see a cmd process in task manager
when you started bash via the Cygwin.bat batch file...


Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

Problem reports:
Unsubscribe info:

More information about the Cygwin mailing list