PowerShell Wait: Start-Sleep, Wait-Process, Start-Process -Wait

powershell wait refers to suspending or pausing script execution using Start-Sleep for time-based delays or Wait-Process to wait for a process to exit.

Start-Sleep -Seconds 5

Use Start-Sleep for unconditional delays and Wait-Process to block until a process exits. For launching external programs and waiting for completion, Start-Process -Wait is the canonical method.

Syntax

Start-Sleep [-Seconds] <int>
Start-Sleep [-Milliseconds] <int>
Start-Sleep [-Duration] <timespan>

Wait-Process [-Name] <string[]> [-Timeout <int>]
Wait-Process -Id <int[]> [-Timeout <int>]

Start-Process -FilePath <string> -Wait [-PassThru]

Options and Flags

Usage Examples

Example 1: Pause script execution for 1.5 seconds

Start-Sleep -Seconds 1.5
Write-Output "Resuming after 1.5 seconds"

Fractional seconds supported since PowerShell 6.2.0. Use -Milliseconds 1500 for earlier versions.

Example 2: Wait for a process by name with timeout

Wait-Process -Name "notepad" -Timeout 30
if ($?) {
    Write-Output "Notepad closed within 30 seconds"
} else {
    Write-Output "Timeout reached or process not found"
}

$? indicates success. The cmdlet throws a non-terminating error if timeout expires or the process doesn’t exist.

Example 3: Start a process and wait for it to complete

$proc = Start-Process -FilePath "msiexec.exe" -ArgumentList "/i setup.msi /quiet" -Wait -PassThru
Write-Output "Installation exit code: $($proc.ExitCode)"

The -Wait parameter suspends the script until the process exits; -PassThru returns the process object to inspect the exit code.

Troubleshooting & Common Errors

Cross-Platform Equivalents

Exit Codes

PowerShell cmdlets do not return Unix-style exit codes. Success is indicated by no error output and $? being $true. The following table covers common error conditions.

Performance Considerations

Selecting the right cmdlet and granularity minimizes idle CPU cycles. Use Start-Sleep -Milliseconds for sub-second pauses instead of -Seconds to avoid unnecessary delay. For process-level waiting, combine Start-Process -PassThru with Wait-Process -Id to eliminate polling overhead. Once you have the process object, Wait-Process -Id avoids repeated name resolution.

• Granularity: Use -Milliseconds (e.g., 25 ms) rather than -Seconds to match actual idle requirements.
• Process identification: Capture the process via Start-Process -PassThru then use Wait-Process -Id to avoid repeated name lookups.
• Batch waiting: Supply multiple process IDs to Wait-Process -Id in a single call (e.g., Wait-Process -Id $pid1,$pid2) to wait on several processes concurrently.
• Blocking vs. non-blocking: Start-Process -Wait blocks the current thread; for parallel workloads consider Start-Job or ForEach-Object -Parallel (outside this command set).

# Fine-grained wait using milliseconds
Start-Sleep -Milliseconds 25

# Wait for a specific process by ID for precise control
$proc = Start-Process -FilePath "notepad.exe" -PassThru
Wait-Process -Id $proc.Id
Write-Output "Process $($proc.Id) finished."

Start-Sleep -Seconds 5
Wait-Process -Name "notepad" -Timeout 30

Wait-Process -Name "longtask" -Timeout 120

$job = Start-Job -ScriptBlock { ... }
$result = Receive-Job -Job $job -Wait -AutoRemoveJob

Wait-Process -Name "sleep" -Timeout 10

$jobs = 1..10 | ForEach-Object -Parallel { 
    Start-Job { param($id) Start-Sleep (Get-Random -Max 10); $id } -ArgumentList $_
}
while ($jobs) { 
    $done = Wait-Job -Job $jobs -Any 
    $done | Receive-Job -AutoRemoveJob
    $jobs = $jobs | Where-Object { $_.Id -ne $done.Id }
}