PowerShell Wait-Job未生效：如何实现进程完成后再执行后续指令

Hey Paul, let's get this sorted out—your script's jumping ahead to variable operations before the scan finishes because you haven't properly tied the wait logic to the actual scan process instance. Here's how to fix it, depending on how you're launching that scan task:

1. 如果用Start-Process启动扫描工具 #

This is the most common scenario. You need to use the -PassThru parameter to capture the process object, then call WaitForExit() on it to block until the scan is done (no need to guess how long it'll take—it waits as long as needed):

# 先保留你原有的变量定义
$logPath = "C:\Users\Administrator\Desktop\log.txt"
$scanPath = "C:\Users\Administrator\Desktop\scan.txt"
$repairLog = "C:\Users\Administrator\Desktop\repair.txt"
$failLog = "C:\Users\Administrator\Desktop\fail.txt"
$computer = "SERVER2012"
$CBSFileLocation = "C:\Windows\Logs\CBS\CBS.log" # 补全你未写完的路径

# 启动扫描进程并捕获它（替换成你实际的扫描工具路径和参数）
$scanProcess = Start-Process -FilePath "C:\Path\To\Your\ScanTool.exe" -ArgumentList "/scan $scanPath" -PassThru -NoNewWindow

# 等待扫描进程完全结束
$scanProcess.WaitForExit()

# 现在执行后续变量操作——这些会等扫描完成后才运行
Write-Host "扫描已完成，开始处理结果..."
$scanResults = Get-Content $scanPath

# 示例：根据扫描结果写入对应日志
if ($scanResults -notmatch "Error|Failed") {
    "[$(Get-Date)] 扫描完成：未发现异常" | Out-File $logPath -Append
} else {
    "[$(Get-Date)] 扫描完成：检测到问题" | Out-File $repairLog -Append
}

2. 如果通过WMI/CIM启动扫描进程 #

If you're using WMI to start or reference the scan process on your remote SERVER2012 machine, use the Wait() method on the WMI process object:

# 定位到目标机器上的扫描进程
$scanProcess = Get-WmiObject -ComputerName $computer -Class Win32_Process -Filter "Name='ScanTool.exe'"

# 等待进程终止
$scanProcess.Wait()

# 后续操作放在Wait()之后执行即可

关键注意事项 #

• 一定要捕获进程对象: 没有-PassThru（针对Start-Process）或直接的WMI/CIM对象引用，脚本就无法追踪进程，自然没法等待它完成。
• 可选但实用：检查退出码: 等待完成后，你可以通过$scanProcess.ExitCode判断扫描是否成功（通常0代表成功），再调整后续逻辑。
• 避免提前执行: 所有变量处理、日志写入等后续步骤，必须放在等待方法调用之后——别把它们写在前面，否则会直接跳过等待环节。

内容的提问来源于stack exchange，提问作者Paul Shane Hay