Скачать или смотреть How to Kill a Process in Windows Without Halting the Current Process

Learn how to effectively kill a process in Windows while keeping your running Python script active with this step-by-step guide.
---
This video is based on the question https://stackoverflow.com/q/62362463/ asked by the user 'H4CK3R 5M4CK3R' ( https://stackoverflow.com/u/13129822/ ) and on the answer https://stackoverflow.com/a/62362745/ provided by the user 'xxbinxx' ( https://stackoverflow.com/u/3868653/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: How to kill a process in window without killing current process

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
How to Kill a Process in Windows Without Halting the Current Process

Every programmer faces the need to control running processes in their scripts, especially when building applications that need to manage themselves dynamically. In this blog, we’ll explore the problem of killing a process without affecting the current process in Windows, particularly focusing on a Python script that reads from a file and interacts with a batch script.

The Problem

Imagine you have a Python script that continuously checks a text file for specific commands. When it sees the command "pause" in the file, it runs a batch file that is supposed to terminate itself and restart the Python script. However, the challenge lies in the way processes are managed: running the batch file effectively kills the Python process simultaneously, leading to a failure in restarting it.

Example Setup

You may have a structure like this:

Python script (main.py) - Monitors the file (input.txt).

Batch script (kill.bat) - Responsible for restarting the Python script.

As seen in the provided snippets, when the "pause" command is found, the kill.bat script is executed, which terminates the command prompt (cmd.exe). However, this inadvertently shuts down your Python script as well, complicating your automation.

The Solution

To resolve this issue while ensuring that only the desired process is terminated, follow this organized approach. This will involve slightly modifying both the Python and batch scripts.

Step 1: Modify the Python Script

Objective: Capture the current process ID (PID) and pass it to the batch file when you need to restart the script.

Here's a simplified version of how your Python script can be adjusted:

[[See Video to Reveal this Text or Code Snippet]]

Step 2: Update the Batch Script

Objective: Modify the batch script to accept the PID as an argument, kill the correct process, and restart the Python script.

You can change your kill.bat as follows:

[[See Video to Reveal this Text or Code Snippet]]

Helpers for Understanding

To break it down further, let’s look at the key components:

How to Get Current Process ID in Python:

[[See Video to Reveal this Text or Code Snippet]]

Passing Process ID to Batch Script:
Use the command:

[[See Video to Reveal this Text or Code Snippet]]

Batch Script Argument Handling:
In the batch file, %1 captures the first argument (your PID), while %* includes all passed arguments.

Killing a Process:
You can kill the process in the batch file using:

[[See Video to Reveal this Text or Code Snippet]]

Starting Python as a Separate Process:
You can use:

[[See Video to Reveal this Text or Code Snippet]]

Conclusion

By strategically modifying your Python and batch scripts, you ensure that only the intended process is terminated, allowing your scripts to self-manage without disruption. This approach not only increases the robustness of your code but also makes your applications more user-friendly by managing their states effectively.

Feel free to reach out if you have any questions or need clarification on any aspect of the solution. Happy coding!