Windows脚本：程序串行执行及卸载程序运行阻塞问题解决

Hey there! Let's break down how to solve both of your Windows batch script problems—they're actually two sides of the same coin when it comes to controlling execution flow.

Problem 2: Making Uninstallers Run to Completion Before the Script Continues #

The issue you're seeing is super common with GUI-based uninstallers: many of them launch a separate background process and then immediately exit the initial process your batch script called. That's why your console gets control back right away—your script thinks the uninstaller is done, even though the actual uninstall process is still running.

The fix is to use the start /wait command, which tells the script to wait for the launched process (and most child processes it spawns) to fully complete before moving on. Here's how to modify your existing code:

@setlocal enabledelayedexpansion
@for /r %%i in (un*.exe) do (
    @echo Found file: %%~nxi %%i
    # Use start /wait to force the script to wait for the uninstaller to finish
    start /wait "" "%%i"
    # Optional: Check the exit code to debug success/failure
    @echo Uninstaller for %%~nxi exited with code: !errorlevel!
)

Quick note about the empty "" in the start command: #

If your uninstaller's file path includes spaces, the start command will treat the first quoted string as a window title instead of the program path. Adding the empty double quotes gives start a placeholder for the title, ensuring it correctly interprets the uninstaller path as the program to run.

Problem 1: General Method to Wait for a Program to Finish Before Launching the Next #

For any program in a batch script, the core way to enforce sequential execution is:

• For console-based programs: Simply calling the program directly (e.g., "C:\Path\To\program.exe") will make the script wait until it finishes.
• For GUI-based programs: As with your uninstallers, use start /wait "" "C:\Path\To\program.exe" to ensure the script waits for the full process lifecycle to complete.

This approach guarantees that each program runs to completion before the script proceeds to the next task in your sequence.

Hope that clears things up! If you run into weird edge cases with specific uninstallers (like those that spawn multiple processes), feel free to tweak the script with additional checks—though start /wait handles most common scenarios perfectly.

内容的提问来源于stack exchange，提问作者skm