Windows 安装脚本在默认 PowerShell 执行策略下闪退且无错误提示 || Windows installation script crashes without error prompt under default PowerShell execution policy

[Must77]

What version of Kimi Code CLI is running?

未安装成功 - 问题发生在首次安装阶段。当时版本 v1.22.0

Which open platform/subscription were you using?

N/A

Which model were you using?

N/A

What platform is your computer?

Window 10 和 Window 11，无法查询更具体型号

What issue are you seeing?

在干净的 Windows 环境下运行官网推荐的安装命令时，PowerShell 窗口会直接闪退（瞬间关闭），没有任何错误提示或日志输出，用户无法获知失败原因。

根本原因分析：
Windows 默认 PowerShell 执行策略为 Restricted，阻止了 Invoke-Expression 执行远程脚本。而安装脚本中设置了 $ErrorActionPreference = "Stop" 且缺乏错误捕获，导致权限错误直接触发进程终止，窗口关闭。

也就是说，需要在执行安装脚本前执行 Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope Process

What steps can reproduce the bug?

0代码环境的 Windows 电脑

打开 PowerShell 粘贴并执行官网命令：irm https://code.kimi.com/install.ps1 | iex

观察现象：PowerShell 窗口瞬间关闭，无任何提示，回到桌面

What is the expected behavior?

用户应该不单独执行 Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope Process ，而直接采用官网提供的单条安装命令即可成功安装。单独 Debug 对于非程序员来说很困难。

Additional information

已经在 Win10 和 Win11 上复现，均为0代码环境。

---

What version of Kimi Code CLI is running?

Installation not successful - the problem occurred during the first installation phase. The current version was v1.22.0

Which open platform/subscription were you using?

N/A

Which model were you using?

N/A

What platform is your computer?

Window 10 and Window 11, unable to query more specific models

What issue are you seeing?

When running the installation command recommended by the official website in a clean Windows environment, the PowerShell window will crash directly (close instantly) without any error prompt or log output, and the user cannot know the reason for the failure.

Root cause analysis:
The default Windows PowerShell execution policy is Restricted, which prevents Invoke-Expression from executing remote scripts. However, $ErrorActionPreference = "Stop" is set in the installation script and there is a lack of error capture, causing permission errors to directly trigger process termination and window closing.

In other words, Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope Process needs to be executed before executing the installation script.

What steps can reproduce the bug?

0 code environment Windows computer

Open PowerShell, paste and execute the official website command: irm https://code.kimi.com/install.ps1 | iex

Observation phenomenon: The PowerShell window closes instantly without any prompt and returns to the desktop.

What is the expected behavior?

Users should not execute Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope Process separately, but directly use the single installation command provided by the official website to successfully install. Debugging alone is difficult for non-programmers.

Additional information

It has been reproduced on Win10 and Win11, both in 0 code environment.

[Br1an67]

I've implemented the fix. The root cause is exactly as described: $ErrorActionPreference = 'Stop' combined with the Restricted execution policy causes the script to terminate instantly without any feedback.

Fix:

1. Auto-set RemoteSigned execution policy for the current process only (non-persistent, safe)
2. Wrap all installation steps in try-catch blocks
3. Display user-friendly error messages with clear remediation steps
4. Add Read-Host pause before exit so the PowerShell window stays open on failure

PR incoming.

[Br1an67]

Root Cause Analysis

The install.ps1 script sets $ErrorActionPreference = "Stop" but wraps no try-catch around Invoke-RestMethod | Invoke-Expression. Under the default Restricted execution policy, Invoke-Expression throws a security exception, and since ErrorActionPreference is Stop, the process terminates immediately — closing the window with no feedback.

Fix: PR #1516 wraps Install-Uv in try-catch and shows a clear error message with the remediation command (Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope Process). Also adds a "Press any key to exit" prompt to keep the window open.

[Must77]

I've implemented the fix. The root cause is exactly as described: $ErrorActionPreference = 'Stop' combined with the Restricted execution policy causes the script to terminate instantly without any feedback.

Fix:

1. Auto-set RemoteSigned execution policy for the current process only (non-persistent, safe)
2. Wrap all installation steps in try-catch blocks
3. Display user-friendly error messages with clear remediation steps
4. Add Read-Host pause before exit so the PowerShell window stays open on failure

PR incoming.

这个pr里的代码看起来就像是纯粹ai而未经人类审核的，充斥着过量的try-catch和冗长的命名。现在的install.ps1至少能做到一眼就看出来问题出在哪里

[Must77]

看起来这个 issue 的解决不在于 install.ps1 本身，应该考虑修改官网上的单行安装命令，即
irm https://code.kimi.com/install.ps1 | iex
变为
powershell -ExecutionPolicy ByPass -c "irm https://code.kimi.com/install.ps1 | iex"

这个 bug 的原因是 kimi-cli 没有正确的依照 uv 的安装文档。不知道这是为了简洁性还是意外导致的。如果是故意为之的，我认为应该考虑和 uv-install.ps1:615 附近一样添加一段明显的提示。下面是615行附近的内容

  # show notification to change execution policy:
  $allowedExecutionPolicy = @('Unrestricted', 'RemoteSigned', 'Bypass')
  If ((Get-ExecutionPolicy).ToString() -notin $allowedExecutionPolicy) {
    throw @"
Error: PowerShell requires an execution policy in [$($allowedExecutionPolicy -join ", ")] to run $app_name. For example, to set the execution policy to 'RemoteSigned' please run:

    Set-ExecutionPolicy RemoteSigned -scope CurrentUser

"@
  }

说实话我并不知道该 at 谁来解决这个问题。@RealKai42 ，如果这不属于你的解决范围内，很抱歉打扰，并请帮助我关闭这个 issue。