Environment

• Windows 10.0.26200
• OpenClaw 2026.6.11

Problem

When running openclaw gateway start or after openclaw gateway install --force, the Gateway service is installed as a Windows Scheduled Task with <LogonType>InteractiveToken</LogonType>, which causes a cmd.exe terminal window to pop up visibly.

The service runs via gateway.cmd which launches node.exe directly. Because the task's LogonType is InteractiveToken, a command prompt window appears on the desktop each time the gateway starts or restarts.

Expected behavior

openclaw gateway start should start the gateway silently without any visible terminal window, like a proper background service on Windows.

Analysis

The schtasks XML after install shows:

<LogonType>InteractiveToken</LogonType>
<Command>...\.openclaw\gateway.cmd</Command>

Changing the LogonType to S4U (service-for-user, session 0, no GUI) or using the already-created VBS launcher as the task action would fix this.

Note: The installer already creates a VBS launcher in %APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup\OpenClaw Gateway.vbs that uses WScript.Shell.Run ..., 0, False (hidden window) — so the fix could be as simple as using that VBS as the task action instead of gateway.cmd directly.

Workaround

Start silently with the VBS launcher:

wscript.exe "%APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup\OpenClaw Gateway.vbs"