install.ps1: syntax error in Linux PATH branch causes script to fail on Windows too

[AronRubin]

Bug

Running the quick-install one-liner on Windows fails with a parser error even though the broken code is in a Linux-only branch:

\
iwr https://raw.githubusercontent.com/standardbeagle/ps-bash/main/install.ps1 | iex
\\

Error:
\
ParserError: install.ps1:99:44
Line |
99 | \ = "export PATH="""":\"
| ~~~~~~~~~~~~~~~~~~~~~~~
| Unexpected token '\"":\"' in expression or statement.
\\

Root Cause

Line 99 uses \"\ as a string escape inside a double-quoted PowerShell string, which is not valid PowerShell syntax. The correct escape is \". PowerShell parses the entire script before executing it, so this syntax error in the Linux branch aborts the script on Windows before any code runs.

\\powershell

Line 99 — current (broken)

\ = "export PATH="""":\"

Fix

\ = "export PATH="\":\"
\\

Environment

• OS: Windows 11
• PowerShell: 7.6.2
• Affected: both \iwr ... | iex\ and saving to file and running with \pwsh -File\

Workaround

Download the zip directly from the Releases page and extract \ps-bash.exe\ manually.

[AronRubin]

Second bug: ps-bash-host runspace initialization exceeds the 20s connection timeout

After fixing the install script manually and installing successfully, \ps-bash -c "echo test"\ still fails:

\
ps-bash: ps-bash-host did not accept connections within 20s.
\\

Investigation

The host binary starts and creates its named pipe correctly — I can verify the pipe exists and connect to it via \NamedPipeClientStream:

\\powershell
\System.Diagnostics.Process = Start-Process ".\ps-bash-host.exe" -ArgumentList "--ipc-endpoint=pipe:psbash-\2e822448902b4562b9a04ace32fdbd3c" -PassThru -WindowStyle Hidden
Start-Sleep -Milliseconds 2000

Pipe exists:

[System.IO.Directory]::GetFiles('\.\pipe') | Where-Object { \ -match \2e822448902b4562b9a04ace32fdbd3c }

→ \.\pipe\psbash-

But ps-bash's health check times out before the runspace finishes initializing

\\

The root cause: \SdkRunspace.Create()\ spins up a PS SDK runspace and loads \PsBash.psm1\ on a background thread. On this machine that initialization takes longer than 20 seconds — which is also the connection deadline in \IpcWorker.GetStartupTimeout(). The host is alive and listening on the pipe but the PowerShell runspace isn't ready to answer the health handshake within the window.

Environment

• OS: Windows 11
• PowerShell: 7.6.2 (PS7 installed in OneDrive-synced Documents folder)
• .NET runtime: 10.0.8 (matches host requirement)
• PSCX module installed (shadows some built-in cmdlets — may slow runspace init via \CreateDefault2())
• \PSModulePath\ includes an OneDrive-synced path

Suggested fix

Either increase the default startup timeout (e.g. 60s), or make it configurable via an env var like \PSBASH_STARTUP_TIMEOUT\ separate from \PSBASH_TIMEOUT\ (which controls per-command idle timeout). The 20s default may be fine for most machines but is too tight when runspace init is slow.