Bug type
Behavior bug (incorrect output/state without crash)
Summary
Version
OpenClaw 2026.3.2 (85377a2)
Platform
- Node host: Windows 10/11, German locale (de-DE)
- Gateway: Ubuntu Linux (noble)
Description
openclaw node status on the Windows node host reports the service as "stopped", even though the Scheduled Task is actively running and the node is connected to the gateway.
The output contradicts itself:
Service: Scheduled Task (registered)
Runtime: stopped (state Wird ausgeführt)
"Wird ausgeführt" is the German localization of "Running" in schtasks output. The status parser does not recognize this string and defaults to "stopped".
Steps to reproduce
Steps to Reproduce
- Install OpenClaw node on a Windows machine with German locale
openclaw node install → creates Scheduled Task "OpenClaw Node"
Start-ScheduledTask -TaskName "OpenClaw Node" → task starts successfully
- Confirm node is connected via gateway (
nodes status shows connected: true)
- Run
openclaw node status on the Windows machine
- Status incorrectly shows "stopped"
Expected behavior
Expected Behavior
openclaw node status should report the service as "running" when the Scheduled Task state is "Wird ausgeführt".
Root Cause (likely)
The schtasks state parser probably only matches English strings like "Running" / "Ready" / "Disabled". German Windows returns localized strings:
- "Wird ausgeführt" = Running
- "Bereit" = Ready
- "Deaktiviert" = Disabled
Suggested Fix
Either:
- Parse schtasks output locale-independently (e.g. use
schtasks /Query /FO CSV and match on exit code or status codes instead of strings)
- Use PowerShell
Get-ScheduledTask which returns structured objects with a State property that uses English enum values (Running, Ready, Disabled) regardless of locale
- Add common locale strings for major languages
Option 2 seems most robust:
(Get-ScheduledTask -TaskName "OpenClaw Node").State
# Returns "Running" even on German Windows
Actual behavior
🦞 OpenClaw 2026.3.2 (85377a2) — Half butler, half debugger, full crustacean.
Service: Scheduled Task (registered)
Command: ...
Runtime: stopped (state Wird ausgef�hrt)
Service is loaded but not running.
Logs: schtasks /Query /TN "OpenClaw Node" /V /FO LIST
OpenClaw version
2026.3.2 (85377a2)
Operating system
Windows 11
Install method
npm global
Logs, screenshots, and evidence
Impact and severity
No response
Additional information
No response
Bug type
Behavior bug (incorrect output/state without crash)
Summary
Version
OpenClaw 2026.3.2 (85377a2)
Platform
Description
openclaw node statuson the Windows node host reports the service as "stopped", even though the Scheduled Task is actively running and the node is connected to the gateway.The output contradicts itself:
"Wird ausgeführt" is the German localization of "Running" in
schtasksoutput. The status parser does not recognize this string and defaults to "stopped".Steps to reproduce
Steps to Reproduce
openclaw node install→ creates Scheduled Task "OpenClaw Node"Start-ScheduledTask -TaskName "OpenClaw Node"→ task starts successfullynodes statusshowsconnected: true)openclaw node statuson the Windows machineExpected behavior
Expected Behavior
openclaw node statusshould report the service as "running" when the Scheduled Task state is "Wird ausgeführt".Root Cause (likely)
The schtasks state parser probably only matches English strings like "Running" / "Ready" / "Disabled". German Windows returns localized strings:
Suggested Fix
Either:
schtasks /Query /FO CSVand match on exit code or status codes instead of strings)Get-ScheduledTaskwhich returns structured objects with aStateproperty that uses English enum values (Running,Ready,Disabled) regardless of localeOption 2 seems most robust:
Actual behavior
🦞 OpenClaw 2026.3.2 (85377a2) — Half butler, half debugger, full crustacean.
Service: Scheduled Task (registered)
Command: ...
Runtime: stopped (state Wird ausgef�hrt)
Service is loaded but not running.
Logs: schtasks /Query /TN "OpenClaw Node" /V /FO LIST
OpenClaw version
2026.3.2 (85377a2)
Operating system
Windows 11
Install method
npm global
Logs, screenshots, and evidence
Impact and severity
No response
Additional information
No response