Assertion failed error for Gateway

[tacit spire]

Whenever I try to run anything OpenClaw gateway related, I get the same error that stops the OpenClaw system from starting. I cannot start gateway, I cannot run doctor all the way when it starts because it tries the gateway, and updates fail. The error I receive is:

Assertion failed: new_time >= loop->time, file src\win\core.c, line 327

It started happening when I upgraded from 5.2 to 5.7. It doesn't seem to occur at the same point whenever running the gateway or other commands, but the error is the same every time.

Running on windows, connected to Claude

[thin owl]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[fervent marten]

That assertion is coming from Node/libuv's Windows event loop, not from Claude auth or an OpenClaw config key. So I’d treat this as a native Windows runtime/crash issue first.

Can you paste these from a fresh PowerShell?

openclaw --version
node -v
where.exe openclaw
where.exe node

A couple of useful next checks/fixes:

winget upgrade OpenJS.NodeJS.LTS
npm i -g openclaw@latest

[fervent marten]

openclaw gateway run --verbose

Then close/reopen PowerShell before retrying, so PATH picks up the Node install. OpenClaw requires Node 22.14+, and current docs recommend Node 24: https://docs.openclaw.ai/install/node

If this is native Windows and still crashes on latest, the practical workaround is WSL2; docs explicitly call WSL2 the more stable full-experience path on Windows: https://docs.openclaw.ai/platforms/windows

If it still reproduces after the Node/OpenClaw reinstall, this is worth a GitHub issue with the four command outputs above plus the exact crashing command/log snippet: https://github.com/openclaw/openclaw/issues

[tacit spire]

resolution was to run this in powershell:
bcdedit /set disabledynamictick yes

[fervent marten]

Good find, thanks for reporting back.

For anyone landing here later: this points pretty strongly at a Windows timer/clock issue underneath Node/libuv. bcdedit /set disabledynamictick yes needs an elevated PowerShell and usually a reboot to fully apply.

If this fixed it, please right-click the solution message → Apps → ✅ Mark Solution. That helps Answer Overflow index the fix for the next person who hits the same assertion.