openclaw - 💡(How to fix) Fix [Bug] openclaw status/cron list hangs with SIGKILL on Windows (Node v22+) [1 participants]

TL;DR

Downgrade to OpenClaw 4.14 to avoid the regression introduced in version 4.15 that causes openclaw status and openclaw cron list to hang indefinitely on Windows 11 with Node.js v22+.

Guidance

• Verify that the issue is specific to OpenClaw 4.15 by testing with OpenClaw 4.14, as indicated by the fact that openclaw status works fine on this version.
• Check the system logs for any error messages related to the SIGKILL signal that is killing the openclaw status and openclaw cron list commands.
• Investigate the changes introduced in OpenClaw 4.15, particularly the cron list detection fix (commit 43bf5b29), to understand how they might be causing the regression.
• Consider testing with different Node.js versions to confirm that the issue is not specific to a particular version, although the problem persists across Node versions v22/v24/v25.

Example

No code snippet is provided as the issue seems to be related to a specific version of OpenClaw and its interaction with the operating system and Node.js, rather than a code-level problem.

Notes

The issue appears to be specific to OpenClaw 4.15 on Windows 11, and downgrading to OpenClaw 4.14 may be the most straightforward workaround until the regression is fixed in a future version of OpenClaw.

Recommendation

Apply workaround: Downgrade to OpenClaw 4.14, as this version has been confirmed to work correctly and the issue seems to be specific to the changes introduced in OpenClaw 4.15.