Back to Signal Feed
CodeTracked since May 18, 2026

Quote path arguments in Start-Process to fix silent Windows hook failures

PeonPing fixed Windows hook launch failures caused by unquoted path arguments in PowerShell `Start-Process -ArgumentList` calls, where `%USERPROFILE%` values with spaces were being split into truncated paths and child scripts exited with errors while parents still reported success.

PowerShellStart-Process-ArgumentList-File

What Happened

  • PeonPing fixed Windows hook launch failures caused by unquoted path arguments in PowerShell `Start-Process -ArgumentList` calls, where `%USERPROFILE%` values with spaces were being split into truncated paths and child scripts exited with errors while parents still reported success.
  • PeonPing fixed Windows hook launch failures caused by unquoted path arguments in PowerShell `Start-Process -ArgumentList` calls, where `%USERPROFILE%` values with spaces were being split into truncated paths and child scripts exited with errors while parents still reported success.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Implemented a targeted code fix across install and adapter scripts (`install.ps1`, `amp.ps1`, `antigravity.ps1`, `kimi.ps1`) by wrapping path variables in escaped double quotes for `Start-Process -File` argument arrays, changing `"-File", $var` to `"-File", "`"$var`""` to prevent path tokenization at spaces.

Why Track This

Why It Matters

Windows users whose account/profile path contains spaces will now get hook audio and desktop notifications again instead of silent failures, so reminders and event alerts become visible/audible during normal operation. The fix preserves the full script path when spawning detached PowerShell children; to monitor next, check for remaining unquoted path arguments in other detached `Start-Process` call sites because the parent process still often does not inspect child exit status or stderr in normal paths.

Impact

Windows users whose account/profile path contains spaces will now get hook audio and desktop notifications again instead of silent failures, so reminders and event alerts become visible/audible during normal operation. The fix preserves the full script path when spawning detached PowerShell children; to monitor next, check for remaining unquoted path arguments in other detached `Start-Process` call sites because the parent process still often does not inspect child exit status or stderr in normal paths.

What To Watch Next

  • Watch whether PowerShell becomes a repeated pattern.
  • Track follow-up changes around AI Coding Agents.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: other_unquoted_windows_start_process_calls, detached_process_exit_status_not_observed.
Open Topic TimelineOpen Technical EventOpen Original Sourceother_unquoted_windows_start_process_calls / detached_process_exit_status_not_observed / ci_not_covering_space_in_user_profile_paths

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

PeonPing/peon-ping PR #520: fix(windows): quote path arguments in Start-Process -ArgumentList

The PR standardizes path quoting in Start-Process invocations (e.g., `-File, "$var"`) so Windows sessions with space-containing user names can execute notification and sound scripts correctly.