Preventing console window from closing on Visual Studio C/C++ Console application

If you run without debugging (Ctrl+F5) then by default it prompts your to press return to close the window. If you want to use the debugger, you should put a breakpoint on the last line.

---

Right click on your project

Properties > Configuration Properties > Linker > System

Select Console (/SUBSYSTEM:CONSOLE) in SubSystem option or you can just type Console in the text field!

Now try it...it should work

---

Starting from Visual Studio 2017 (15.9.4) there is an option:

Tools->Options->Debugging->Automatically close the console

The corresponding fragment from the Visual Studio documentation:

Automatically close the console when debugging stops: Tells Visual Studio to close the console at the end of a debugging session.

---

Here is a way for C/C++:

#include <stdlib.h>

#ifdef _WIN32
    #define WINPAUSE system("pause")
#endif

Put this at the top of your program, and IF it is on a Windows system (#ifdef _WIN32), then it will create a macro called WINPAUSE. Whenever you want your program to pause, call WINPAUSE; and it will pause the program, using the DOS command. For other systems like Unix/Linux, the console should not quit on program exit anyway.

---

Goto Debug Menu->Press StartWithoutDebugging

---

If you're using .NET, put Console.ReadLine() before the end of the program.

It will wait for <ENTER>.

---

try to call getchar() right before main() returns.

---

(/SUBSYSTEM:CONSOLE) did not worked for my vs2013 (I already had it).

"run without debugging" is not an options, since I do not want to switch between debugging and seeing output.

I ended with

int main() {
  ...
#if _DEBUG
  LOG_INFO("end, press key to close");
  getchar();
#endif // _DEBUG
  return 0;
}

Solution used in qtcreator pre 2.6. Now while qt is growing, vs is going other way. As I remember, in vs2008 we did not need such tricks.

---

Here's a solution that (1) doesn't require any code changes or breakpoints, and (2) pauses after program termination so that you can see everything that was printed. It will pause after either F5 or Ctrl+F5. The major downside is that on VS2013 Express (as tested), it doesn't load symbols, so debugging is very restricted.

Create a batch file. I called mine runthenpause.bat, with the following contents: %1 %2 %3 %4 %5 %6 %7 %8 %9 pause The first line will run whatever command you provide and up to eight arguments. The second line will... pause. Open the project properties | Configuration properties | Debugging. Change "Command Arguments" to $(TargetPath) (or whatever is in "Command"). Change "Command" to the full path to runthenpause.bat. Hit OK.

Now, when you run, runthenpause.bat will launch your application, and after your application has terminated, will pause for you to see the console output.

I will post an update if I figure out how to get the symbols loaded. I tried /Z7 per this but without success.

---

just put as your last line of code:

system("pause");

---

add “| pause” in command arguments box under debugging section at project properties.

---

You could run your executable from a command prompt. This way you could see all the output. Or, you could do something like this:

int a = 0;
scanf("%d",&a);

return YOUR_MAIN_CODE;

and this way the window would not close until you enter data for the a variable.

---

Just press CNTRL + F5 to open it in an external command line window (Visual Studio does not have control over it).

If this doesn't work then add the following to the end of your code:

Console.WriteLine("Press any key to exit...");
Console.ReadKey();

This wait for you to press a key to close the terminal window once the code has reached the end.

If you want to do this in multiple places, put the above code in a method (e.g. private void Pause()) and call Pause() whenever a program reaches a possible end.

---

A somewhat better solution:

atexit([] { system("PAUSE"); });

at the beginning of your program.

Pros:

can use std::exit()

can have multiple returns from main

you can run your program under the debugger

IDE independent (+ OS independent if you use the cin.sync(); cin.ignore(); trick instead of system("pause");)

Cons:

have to modify code

won't pause on std::terminate()

will still happen in your program outside of the IDE/debugger session; you can prevent this under Windows using:

extern "C" int __stdcall IsDebuggerPresent(void);
int main(int argc, char** argv) {
    if (IsDebuggerPresent())
        atexit([] {system("PAUSE"); });
    ...
}

---

Either use:

cin.get();

or

system("pause");

Make sure to make either of them at the end of main() function and before the return statement.

---

You can also use this option

#include <conio.h> 
/* run this program using the console pauser or add your own getch, system("pause") or input loop */
int main() {
   .
   .
   .
   getch(); 

   return 0;
}

---

In my case, i experienced this when i created an Empty C++ project on VS 2017 community edition. You will need to set the Subsystem to "Console (/SUBSYSTEM:CONSOLE)" under Configuration Properties.

Go to "View" then select "Property Manager" Right click on the project/solution and select "Property". This opens a Test property page Navigate to the linker then select "System" Click on "SubSystem" and a drop down appears Choose "Console (/SUBSYSTEM:CONSOLE)" Apply and save The next time you run your code with "CTRL +F5", you should see the output.

---

Use Console.ReadLine() at the end of the program. This will keep the window open until you press the Enter key. See https://docs.microsoft.com/en-us/dotnet/api/system.console.readline for details.

---

Sometimes a simple hack that doesnt alter your setup or code can be:

Set a breakpoint with F9, then execute Debug with F5.

---

Since running it from VS attaches the VS debugger, you can check for an attached debugger:

if (Debugger.IsAttached)
{
    Console.WriteLine("Debugger is attached. Press any key to exit.");
    Console.ReadKey();
}

I guess the only caveat is that it'll still pause if you attach any other debugger, but that may even be a wanted behavior.

---

Visual Studio 2015, with imports. Because I hate when code examples don't give the needed imports.

#include <iostream>;

int main()
{
    getchar();
    return 0;
}

---

Currently there is no way to do this with apps running in WSL2. However there are two work-arounds:

The debug window retains the contents of the WSL shell window that closed. The window remains open if your application returns a non-zero return code, so you could return non-zero in debug builds for example.

---

It should be added that things have changed since then. On Windows 11 (probably 10, I can't check any more) the new Terminal app that now houses the various console, PowerShell and other sessions has its own settings regarding closing. Look for it in Settings > Defaults > Advanced > Profile termination behavior.

If it's set to close when a program exits with zero, then it will close, even if VS is told otherwise.

---

Go to Setting>Debug>Un-check close on end.

https://i.stack.imgur.com/ZVllg.png

---