Python Script Opens and Closes Instantly? Here’s How to Fix It

You double-click your Python file, a black window flashes on the screen for a split second, and then it is gone. You cannot read what it said, and you have no idea whether the script worked or crashed. This is one of the most common frustrations for Windows beginners, and it is not a fault in your code. The window closes because the program ended, whether it finished normally or hit an error. This guide shows you how to keep the window open, see the real output, and run scripts the reliable way from the terminal.

Quick Answer

The window closes instantly because your script reached the end or crashed, and Windows closes the console when the program exits. The best fix is to run the script from an already-open terminal: open Command Prompt or PowerShell in the file’s folder and run py your_script.py. For a quick double-click fix, add input("Press Enter to exit...") at the very end of the script so it waits for you.

Why the Window Disappears

When you double-click a .py file, Windows starts the Python interpreter in a brand-new console window created just for that program. The moment the interpreter exits, Windows destroys the window. If your script takes half a second, the window lives for half a second. Crucially, the same thing happens when the script crashes: the error text is printed, the interpreter exits immediately, and the traceback vanishes before you can read a single word.

This is why double-clicking is a poor way to develop or debug. The fix is not to slow the script down, but to separate the window’s lifetime from the program’s lifetime, which is exactly what running from an open terminal does.

Method 1: Run From an Open Terminal (Recommended)

1. Open the folder containing your script in File Explorer.
2. Click the address bar, type cmd, and press Enter. Command Prompt opens already pointing at that folder. In PowerShell or Windows Terminal, right-click in the folder and choose Open in Terminal if available.
3. Run the script with py your_script.py (use your real file name). On systems where py is missing, use python your_script.py.
4. Read the output at your own pace. If there is an error, the full traceback stays on screen, and the window remains open after the program ends.

Our full walkthrough on running a Python file from the Windows terminal step by step covers paths, arguments, and switching folders in more detail if this is your first time using the terminal.

Method 2: Add a Pause at the End of the Script

If you want to keep the double-click habit for finished scripts, end the file with this line:

input("Press Enter to close...")

The program waits for the Enter key before exiting, so the window stays open. Two honest warnings come with this trick. First, if the script crashes before reaching that line, the window still vanishes. Second, a script left waiting for input will hang forever if something else tries to run it automatically. Treat this as a convenience for finished personal scripts, not as a debugging method.

Method 3: Catch the Error So You Can Read It

To see crashes while double-clicking, wrap your main code so errors print and pause:

try:
    main()
except Exception:
    import traceback
    traceback.print_exc()
input("Press Enter to close...")

Now, when anything inside main() fails, the full traceback prints and the window waits. This is genuinely useful for scripts you hand to non-technical family members. The official Python Windows FAQ discusses this exact double-click behaviour and suggests the same pause technique.

Method 4: Run the Script Inside Your Editor

Editors keep output visible by design. In VS Code, open the file and press the Run button or Ctrl+F5; output and errors appear in the integrated terminal panel, which never closes on its own. IDLE, which comes with Python, behaves the same way: use Run → Run Module or press F5, and results stay in the shell window. While you are learning, running everything from the editor or a terminal will save you hours of guessing.

What If the Script Produces No Output at All?

Sometimes the flash is normal: the script ran, printed nothing because it contains no print() calls, and exited. Add a simple print("Done") at the end to confirm it reached the finish. Silent scripts that write files or process data often look broken when they are actually fine.

Common Mistakes to Avoid

• Adding pauses inside loops or functions. A pause buried in the middle of the logic makes the program seem frozen and does nothing for the final crash.
• Assuming a flash means an error. Fast, successful scripts also flash. Always check from a terminal before “fixing” code that may be fine.
• Saving your script with a .txt extension. Files named script.py.txt open in Notepad instead of running. Turn on file name extensions in Explorer to see the real name.
• Double-clicking a script that asks for input. Input-based programs need a visible, waiting window: run them from a terminal so you can actually type answers.

What About Scripts That Need Arguments?

Some scripts expect extra words after the file name — a file to process, a folder to scan, an option to set. Double-clicking can never supply those, which is another reason the flash-and-vanish pattern misleads: the script may have printed “Usage: provide a file name” and closed before the message registered. If a script you downloaded seems to do nothing at all on double-click, run it once from a terminal before assuming it is broken. The terminal run will show the usage message, and you can then call it properly, for example py converter.py photo.jpg.

This is also why most shared Python tools are documented with terminal commands rather than double-click instructions. The terminal is where arguments, input prompts, error messages, and output all live visibly in one place. Building the terminal habit early — even if you mostly work in an editor — removes an entire class of invisible failures from your learning path. The flashing window stops being a mystery and becomes what it always was: a sign that the program ended, for reasons the terminal will happily show you.

Conclusion

The flashing window is simply Windows closing the console the moment Python exits. Run your scripts from an open terminal or your editor and you will always see the output and the full error message. Save the input() pause trick for finished scripts you launch by double-clicking, and you will never lose another traceback to a vanishing window.

Frequently Asked Questions

Does a flashing window mean my code has an error?

Not necessarily. A short script that finishes successfully closes its window just as fast as a crashing one. The only way to know is to run it from a terminal where the output stays visible. Most of the time you will find either a clean finish or a small, fixable error.

How do I keep the window open after an error specifically?

Either run from a terminal, where the window belongs to you rather than the program, or wrap the script in a try/except block that prints the traceback and then waits on input(). The terminal method is better because it also catches errors that happen before any of your code runs.

Why does the script work in VS Code but flash when double-clicked?

VS Code runs the script inside its own terminal panel, which stays open after the program ends. Double-clicking creates a temporary console owned by the Python process, and Windows closes it at exit. Same script, different window behaviour.

Can I make a double-clickable script stay open permanently?

You can create a small batch file that runs the script and then pauses. Save a file called run.bat containing @echo off, py your_script.py, and pause on separate lines, then double-click the batch file instead. The built-in pause keeps the window open regardless of errors.

My script needs keyboard input. What should I do?

Run it from a terminal or editor every time. A program waiting on input() in a double-clicked window will accept your typing only while that window has focus, and it still closes when the program ends. A terminal gives you a stable place to interact with it.