Execution

Author(s)

• Manuel

Tags

Execution Self-Elevation Stub PowerShell Windows

Functions

Clear-TempDirectories ConvertTo-SplatHashtable Exit-AndWaitOnUI Format-SplatHashtable Get-QuotedPath Invoke-NativeCommand Invoke-StubScript Invoke-WhenFileChanged Remove-ItemSafe Restart-SelfElevated Set-PSScriptID

PSEditions

Desktop Core

Dependencies

This module has no dependencies.

Release Notes

Execution v5.1.0+sha.3b1671c

## [v5.1.0] - 2026-05-06

### Added

- `Invoke-NativeCommand`: new `-Backend Auto|ScriptBlock|Process`
 parameter to override the implicit backend selection. `Auto` (default)
 keeps the v5.0 behaviour; `Process` and `ScriptBlock` force the
 matching backend. Combining `-Backend ScriptBlock` with `-TimeoutSec`,
 `-Encoding`, or `-NoWait` raises a terminating error rather than
 silently ignoring the un-honoured switch.
- `Invoke-NativeCommand`: graceful-termination phase before hard-kill
 on `-TimeoutSec`. New `-GracePeriodSec` parameter (default `5`,
 range `0..3600`). The Process backend now sends SIGTERM (Unix) or
 `Process.CloseMainWindow()` (Windows) when the timeout elapses, waits
 up to `GracePeriodSec` for the process to exit cleanly, then falls
 back to `Process.Kill()`. `-GracePeriodSec 0` restores v5.0
 immediate-kill behaviour. Note: Windows console programs do not
 respond to `CloseMainWindow`; for them the grace period is effectively
 a no-op before the hard-kill fallback.
- `Invoke-NativeCommand`: new `-Stream` switch for live output. Each
 captured stdout/stderr line is written to the host as it arrives
 (stdout default color, stderr DarkYellow), in addition to the
 existing `-PassThru` capture. Triggers the Process backend implicitly;
 combining `-Stream` with `-Backend ScriptBlock` raises a terminating
 error. Streaming pauses during the graceful-termination grace period
 on `-TimeoutSec`; queued events are emitted in the post-exit drain.

### Fixed

- `Invoke-NativeCommand` Process backend: trailing stdout lines could
 be reordered on Windows PowerShell 5.1 (B5 regression flake;
 observed as `Stdout[-1] = 'line-999'` while `Stdout.Count = 1000`).
 Root cause: the drain loop sorted PSEventManager events by
 `TimeGenerated`, and two `OutputDataReceived` events fired
 sub-millisecond apart can share a `TimeGenerated` value. PS 5.1's
 `Sort-Object` is not stable (stable sort was added in PS 7), so
 ties reorder consecutive lines. Sort by `EventIdentifier` instead --
 it's monotonic per PSEventManager and reflects FIFO queue-insertion
 order, giving a deterministic drain on every host. Also adds the
 MSDN-recommended no-arg `Process.WaitForExit()` after the polling
 loop on the non-timed-out branch as defense-in-depth (the timed-out
 branch already called it via the kill sequence).