[Windows] Kimi Computer Use install fails: PowerShell 7 installed via winget (MSIX) not found at hardcoded C:\Program Files\PowerShell\7\pwsh.exe (spawn ENOENT)

What version of Kimi Code is running?

0.34.0

Which open platform/subscription were you using?

Kimi Code OAuth

Which model were you using?

k3-256k

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Installing the Kimi Computer Use plugin on Windows fails even though both Windows PowerShell 5.1 and PowerShell 7 are installed and fully working on the machine. Full error:

Error: Kimi Computer Use for Windows installation failed: Kimi Computer Use requires Windows
PowerShell 5.1 or PowerShell 7 with the commands required by its official installer. Windows
PowerShell (C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe): missing commands:
Get-FileHash, Get-AuthenticodeSignature; PowerShell 7 (C:\Program Files\PowerShell\7\pwsh.exe):
Failed to spawn "C:\Program Files\PowerShell\7\pwsh.exe": spawn C:\Program
Files\PowerShell\7\pwsh.exe ENOENT

What steps can reproduce the bug?

1. On Windows 11, install PowerShell 7 via winget install Microsoft.PowerShell (MSIX variant).
2. Ensure C:\Program Files\PowerShell\7\pwsh.exe does not exist (no MSI install).
3. In Kimi Code CLI 0.34.0, install the Kimi Computer Use plugin from /plugins.
4. Installation fails with the error above.

What is the expected behavior?

The installer detects PowerShell 7 regardless of how it was installed (MSI or winget/MSIX), e.g. by resolving pwsh from PATH, and the installation succeeds.

Additional information

Likely root cause: the installer only probes the MSI install path C:\Program Files\PowerShell\7\pwsh.exe. When PowerShell 7 is installed via winget as an MSIX package (winget install Microsoft.PowerShell), pwsh.exe lives under:

C:\Program Files\WindowsApps\Microsoft.PowerShell_7.6.4.0_x64__8wekyb3d8bbwe\pwsh.exe

with an execution alias at %LOCALAPPDATA%\Microsoft\WindowsApps\pwsh.exe (both on PATH). The hardcoded MSI path does not exist on such systems, hence spawn ... ENOENT.

Additionally, the probe of Windows PowerShell 5.1 reports Get-FileHash and Get-AuthenticodeSignature as missing, but both commands ship with PowerShell 5.1 out of the box — so that detection path looks faulty as well.

Environment details:

• OS: Windows 11 Pro, 10.0.26200 (Build 26200)
• Windows PowerShell: 5.1.26100.8875 at C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe
• PowerShell 7: 7.6.4, installed via winget (MSIX) at C:\Program Files\WindowsApps\Microsoft.PowerShell_7.6.4.0_x64__8wekyb3d8bbwe\pwsh.exe
• winget: v1.29.280

Start at the Kimi Computer Use installer’s PowerShell detection and installation path resolution; no source files or tests are named in the issue. Reproduce on Windows 11 with PowerShell 7 installed through winget as an MSIX, then verify that installation succeeds when pwsh is available through PATH and that the Windows PowerShell command checks pass.