如何防止Wscript.Shell弹窗暂停PowerShell脚本执行？

Absolutely! The default Wscript.Shell.Popup method is synchronous—it blocks your script until the user interacts with the popup. But you can run it in a separate background process or job to let your main script keep executing while the popup is visible. Here are a few straightforward ways to make this happen:

Method 1: Use Start-Job for a background popup #

This is the simplest approach using built-in PowerShell cmdlets. We’ll launch the popup as a background job, so your main script proceeds immediately.

$test = (Get-Process -Name Win*).ProcessName

# Launch the popup in a background job
Start-Job -ScriptBlock {
    $test = $args[0]
    (New-Object -COM Wscript.Shell).Popup(($test -join "`r`n"), 0, "WARNING - STRING XYZ WAS DETECTED", 48)
} -ArgumentList $test | Out-Null

# Your main script continues running here
Write-Host "rest of script..."

Quick notes: #

• Out-Null suppresses job status output that would otherwise clutter your console.
• If you need to check later whether the user closed the popup, use Get-Job to track the job’s status.

Method 2: Use Start-Process to spawn a separate PowerShell instance #

This method creates a completely separate process for the popup, ensuring it doesn’t interfere with your main script’s flow. We use Base64 encoding to avoid issues with special characters in your message.

$test = (Get-Process -Name Win*).ProcessName
$testString = $test -join "`r`n"

# Encode the command to handle special characters safely
$encodedCommand = [Convert]::ToBase64String([Text.Encoding]::Unicode.GetBytes(@"
(New-Object -COM Wscript.Shell).Popup('$testString', 0, 'WARNING - STRING XYZ WAS DETECTED', 48)
"@))

# Launch the popup in a separate PowerShell process
Start-Process powershell.exe -ArgumentList "-NoProfile -EncodedCommand $encodedCommand"

# Main script keeps going
Write-Host "rest of script..."

Quick notes: #

• The separate PowerShell process runs in the background (no visible console window) since we’re using the Wscript popup.
• Encoding prevents command-line errors if your message includes quotes or special symbols.

Bonus: Use a .NET WinForms MessageBox (more control) #

If you want a native Windows-style popup with extra customization options, you can run it in a separate runspace for asynchronous behavior.

Add-Type -AssemblyName System.Windows.Forms

$test = (Get-Process -Name Win*).ProcessName
$testString = $test -join "`r`n"

# Create a separate runspace to show the MessageBox without blocking
$runspace = [runspacefactory]::CreateRunspace()
$runspace.Open()
$ps = [powershell]::Create().AddScript({
    param($message)
    [System.Windows.Forms.MessageBox]::Show($message, "WARNING - STRING XYZ WAS DETECTED", [System.Windows.Forms.MessageBoxButtons]::OK, [System.Windows.Forms.MessageBoxIcon]::Warning)
}).AddArgument($testString)
$ps.Runspace = $runspace
$asyncResult = $ps.BeginInvoke()

# Main script continues execution
Write-Host "rest of script..."

# Optional: Clean up resources later if needed
# $ps.EndInvoke($asyncResult)
# $ps.Dispose()
# $runspace.Close()
# $runspace.Dispose()

Quick notes: #

• This requires loading the System.Windows.Forms assembly.
• The runspace approach ensures the MessageBox doesn’t block your main script’s execution.

All these methods let your script keep running while the popup is displayed to the user—pick the one that best fits your workflow!

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