Command Prompt closes instantly after opening a .exe that uses it

[Ozzypig]

(I'm not very good with this stuff, so please bare with me.)
For a while I've had this strange problem on my computer. I'm using a 32-bit version of Windows 8 with 4GB of RAM.

It was fine a few weeks ago. But now, whenever I open a program that runs in the Command Prompt (Like this, I'm not sure how to really explain it.) it closes instantly.
I'm trying to run Git Bash to get some stuff, but I'm not able to. A few weeks ago, I was using Git Bash absolutely fine.
This problem seems to be occurring in many other programs that run in the 'console'.
Strangely, I can open the command prompt normally (cmd.exe).
I've tried doing the WINDOWS + R thingy and execute it from there, but I would like to just be able to double-click on the .exe and it runs, like normal.
Any idea why I can't open up .exes that use the CMD? (Sorry if I got it wrong, feel free to get angry at me.)
If I'm missing any information that you need, feel free to tell me and I'll reply.

 

[Pinhedd]

this is normal behaviour.

When you run an executable that uses the Windows command console it will terminate the console as soon as the program that you ran returns to the console. Command line based programs such as git use a set of options and parameters to determine the program's behaviour each time it is run. Omitting any options or parameters typically triggers the help dialog which is printed once after which the program terminates and control is returned to the command line interpreter. If you want the command line interpreter to persist after the program has been run, the correct solution is to run the program from within an open command window rather than by double clicking on it. So, run cmd.exe first and work from there.

 

[USAFRet]

You ARE opening and running it. It just closes really fast.

A batch file would do the trick cmd /k YourFile.exe
would probably work.