openclaw - 💡(How to fix) Fix [Bug]: Win env Dreaming open config fail [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#69933Fetched 2026-04-22 07:46:29
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Participants
Timeline (top)
labeled ×2

Win env Dreaming open config fail

Error Message

09:39:37 [gateway] config.openFile failed path=C:\Users\hands.openclaw\openclaw.json: Command failed: powershell.exe -NoProfile -NonInteractive -Command Start-Process -LiteralPath 'C:\Users\hands.openclaw\openclaw.json' Start-Process : �Ҳ�����������ơ�LiteralPath��ƥ��IJ����� ����λ�� ��:1 �ַ�: 15

  • Start-Process -LiteralPath 'C:\Users\hands.openclaw\openclaw.json'
  •           ~~~~~~~~~~~~
    • CategoryInfo : InvalidArgument: (:) [Start-Process]��ParameterBindingException
    • FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.Commands.StartProcessCommand

Root Cause

Win env Dreaming open config fail

Code Example

09:39:37 [gateway] config.openFile failed path=C:\Users\hands\.openclaw\openclaw.json: Command failed: powershell.exe -NoProfile -NonInteractive -Command Start-Process -LiteralPath 'C:\Users\hands\.openclaw\openclaw.json'
Start-Process : �Ҳ�����������ơ�LiteralPath��ƥ��IJ�����
����λ�� ��:1 �ַ�: 15
+ Start-Process -LiteralPath 'C:\Users\hands\.openclaw\openclaw.json'
+               ~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [Start-Process]��ParameterBindingException
    + FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.Commands.StartProcessCommand

---
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

Win env Dreaming open config fail

Steps to reproduce

1、open dashboard with Dreaming->Diary-> Open Config 2、gateway log show the openclaw.json file open fail

Expected behavior

1、Expected the openclaw.json file will open and show

Actual behavior

log

09:39:37 [gateway] config.openFile failed path=C:\Users\hands\.openclaw\openclaw.json: Command failed: powershell.exe -NoProfile -NonInteractive -Command Start-Process -LiteralPath 'C:\Users\hands\.openclaw\openclaw.json'
Start-Process : �Ҳ�����������ơ�LiteralPath��ƥ��IJ�����
����λ�� ��:1 �ַ�: 15
+ Start-Process -LiteralPath 'C:\Users\hands\.openclaw\openclaw.json'
+               ~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [Start-Process]��ParameterBindingException
    + FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.Commands.StartProcessCommand

OpenClaw version

2026.04.15

Operating system

Windows 11

Install method

No response

Model

glm-4.7-flash

Provider / routing chain

OpenClaw -> Dreaming -> Diary -> Open Config

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The issue is likely due to an incorrect command being executed to open the openclaw.json file, and a workaround could be to modify the command to use a compatible method for opening files on Windows.

Guidance

  • The error message suggests that the Start-Process command is being used with an invalid argument, specifically the -LiteralPath parameter. This could be due to the file path containing special characters or not being properly escaped.
  • Verify that the file path C:\Users\hands\.openclaw\openclaw.json is correct and the file exists.
  • Consider using a different method to open the file, such as using the Invoke-Item cmdlet, which is a more straightforward way to open a file with its associated application on Windows.
  • Check the documentation for the Start-Process cmdlet to ensure that the correct syntax is being used.

Example

Invoke-Item -Path 'C:\Users\hands\.openclaw\openclaw.json'

This command will open the openclaw.json file with its associated application.

Notes

The issue may be specific to the Windows environment and the way the Start-Process command is being used. Further investigation may be needed to determine the root cause and find a permanent solution.

Recommendation

Apply workaround: Modify the command to use Invoke-Item instead of Start-Process to open the openclaw.json file. This should provide a more reliable way to open the file on Windows.

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

1、Expected the openclaw.json file will open and show

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: Win env Dreaming open config fail [1 participants]