win7 x64 git bash won't start unless run as admin

[Roy Pardee]

Hey All,

I've had a working git install on my win7 x64 (home) machine for some
months now (tho I seldom used it) but today when I clicked on my
pinned shortcut to git bash the app folded before even showing me a
prompt. The dialog windows shows is:

[Window Title]
Windows Command Processor

[Main Instruction]
Windows Command Processor has stopped working

[Content]
A problem caused the program to stop working correctly. Windows will
close the program and notify you if a solution is available.

[Close program]

Googling "git windows command processor has stopped working" turned up
not much of use. So I uninstalled via the windows add/remove
programs, and downloaded/installed the 1.7.3.1 preview exe. I ran the
installer as an admin (either b/c it prompted me for admin to
continue, or b/c it barfed the first time I ran through it--don't
remember.)

But alas, the new version behaves just as the old one did.

In my googlings I did come across this, similar-sort-of issue:

http://code.google.com/p/msysgit/issues/detail?id=391

But taking the "--login" off the shortcut target makes no difference.
The one thing that does seem to make a difference is running as an
admin. If I'm either logged in to the machine as admin, or if I do a
"run as administrator" while logged in as a normal user, all seems to
be well.

Can anybody advise me on how to get back to a state where I can run
git as a regular user?

Many thanks!

-Roy

[Roy Pardee]

One other change that does seem to fix the problem is to change the
git-bash shortcut target from:

C:\Windows\SysWOW64\cmd.exe /c ""C:\Program Files (x86)\Git\bin
\sh.exe" --login -i"

To just:

"C:\Program Files (x86)\Git\bin\sh.exe" --login -i

So--just removing the 64-to-32 bit compatibility command shell
thingy. I've been using git this way for a couple of hours now (just
doing commits & pushes to heroku--nothing fancy) and it seems okay.
Can anybody say whether I should expect problems down the road?

(Maybe MS did something in a quick-fix patch to that version of
cmd.exe that screwed up git bash for non-admins?)

Cheers,

-Roy