Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Bug: openclaw onboard --install-daemon 在 Windows 原生环境报 ERR_UNSUPPORTED_ESM_URL_SCHEME (v2026.4.5) [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#62408•Fetched 2026-04-08 03:04:44
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
qazyysqazyys
Participants
qazyysqazyys
Timeline (top)
labeled ×2subscribed ×1

Error Message

命令执行报错，终端输出如下：Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'f:' Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'f:'

Code Example

npm install -g openclaw@2026.4.5

### Expected behavior

**Additional info**
- 该错误与配置自定义 provider (`custom-integrate-api-nvidia-com/minimaxai/minimax-m2.5`) 有直接关联：配置完成后立即出错。
- 怀疑 OpenClaw 在处理自定义 provider 的配置保存或后续初始化时，使用了一个包含盘符路径的 ESM `import()` 或 `require()`，导致 Node.js 将 `F:` 解析为协议。

### Actual behavior

### Actual behavior

执行 `openclaw onboard --install-daemon` 后，按照交互提示依次操作：

1. 验证成功：`◇  Verification successful.`
2. 输入 Endpoint ID：`custom-integrate-api-nvidia-com`
3. 输入 Model alias（可选）：`minimaxai`

随后终端输出：Configured custom provider: custom-integrate-api-nvidia-com/minimaxai/minimax-m2.5
Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'f:'

### OpenClaw version

2026.4.5

### Operating system

windows11

### Install method

_No response_

### Model

minimaxai/minimax-m2.5

### Provider / routing chain

openclaw -> custom-integrate-api-nvidia-com (NVIDIA API) -> minimaxai/minimax-m2.5

### Additional provider/model setup details




### Logs, screenshots, and evidence
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

问题摘要

在 Windows 原生环境（非 WSL2）中，运行 openclaw onboard --install-daemon 命令时，报出 ERR_UNSUPPORTED_ESM_URL_SCHEME 错误，命令执行中断。

环境信息

  • 操作系统: Windows Windows 11 专业版 23H2
  • Node.js 版本: node --version → v24.14.1
  • npm 版本: npm --version → 11.11.0
  • OpenClaw 版本: openclaw --version → 2026.4.5 (3e72c03)
  • Shell环境: PowerShell (PS C:\Users\11019>)

重现步骤

  1. 在 Windows 原生环境中安装 OpenClaw：npm install -g openclaw@latest
  2. 运行 onboard 命令：openclaw onboard --install-daemon
  3. 观察终端输出。

实际结果

命令执行报错，终端输出如下：Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'f:'

Steps to reproduce

  1. 环境准备：在 Windows 原生环境（非 WSL2）中，安装 Node.js v24.14.1 和 npm 11.11.0。
  2. 全局安装 OpenClaw v2026.4.5： 
    npm install -g [email protected]

Expected behavior

Additional info

  • 该错误与配置自定义 provider (custom-integrate-api-nvidia-com/minimaxai/minimax-m2.5) 有直接关联：配置完成后立即出错。
  • 怀疑 OpenClaw 在处理自定义 provider 的配置保存或后续初始化时，使用了一个包含盘符路径的 ESM import() 或 require()，导致 Node.js 将 F: 解析为协议。

Actual behavior

Actual behavior

执行 openclaw onboard --install-daemon 后，按照交互提示依次操作：

  1. 验证成功：◇ Verification successful.
  2. 输入 Endpoint ID：custom-integrate-api-nvidia-com
  3. 输入 Model alias（可选）：minimaxai

随后终端输出：Configured custom provider: custom-integrate-api-nvidia-com/minimaxai/minimax-m2.5 Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'f:'

OpenClaw version

2026.4.5

Operating system

windows11

Install method

No response

Model

minimaxai/minimax-m2.5

Provider / routing chain

openclaw -> custom-integrate-api-nvidia-com (NVIDIA API) -> minimaxai/minimax-m2.5

Additional provider/model setup details

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The issue can be resolved by ensuring that OpenClaw handles custom provider configurations correctly, specifically by avoiding the use of absolute paths that Node.js interprets as invalid URL schemes.

Guidance

  1. Verify Custom Provider Configuration: Check how the custom provider (custom-integrate-api-nvidia-com/minimaxai/minimax-m2.5) is configured and ensure it does not use absolute paths that could be misinterpreted by Node.js.
  2. Use Relative Paths or Valid URL Schemes: Modify the configuration to use relative paths or ensure that any absolute paths are properly formatted as file:// URLs to avoid triggering the ERR_UNSUPPORTED_ESM_URL_SCHEME error.
  3. Review OpenClaw Documentation: Consult the OpenClaw documentation for any specific guidelines on configuring custom providers and handling paths in Windows environments.

Example

No specific code example can be provided without more details on the custom provider configuration. However, ensuring that paths are correctly formatted (e.g., using file:// for absolute paths on Windows) is crucial.

Notes

The solution may depend on the specifics of how OpenClaw handles custom provider configurations and the exact nature of the custom-integrate-api-nvidia-com/minimaxai/minimax-m2.5 provider. Further investigation into OpenClaw's documentation and source code may be necessary.

Recommendation

Apply a workaround by correctly formatting paths in the custom provider configuration to avoid the ERR_UNSUPPORTED_ESM_URL_SCHEME error, as this is likely a configuration issue rather than a problem with OpenClaw itself.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Additional info

  • 该错误与配置自定义 provider (custom-integrate-api-nvidia-com/minimaxai/minimax-m2.5) 有直接关联：配置完成后立即出错。
  • 怀疑 OpenClaw 在处理自定义 provider 的配置保存或后续初始化时，使用了一个包含盘符路径的 ESM import() 或 require()，导致 Node.js 将 F: 解析为协议。
#api#agent execution#callback error#memory management#API rate limit

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING