Problem

On Windows, the Update button in the control UI (and the update.run API call) fails with an EBUSY error because npm cannot rename/replace the openclaw module folder while the gateway process is actively running and holding file locks.

Error:

npm error code EBUSY
npm error syscall rename
npm error path C:\Users\...\AppData\Roaming\npm\node_modules\openclaw
npm error errno -4082
npm error EBUSY: resource busy or locked

Expected Behaviour

The Update button should successfully update openclaw on Windows without manual intervention.

Suggested Fix

Before running npm i -g openclaw@latest, the update sequence should:

1. Stop the gateway service
2. Run the npm update
3. Restart the gateway

Current Workaround

Manually stop the gateway, run npm i -g openclaw@latest from a terminal, then restart -- which defeats the purpose of the Update button.

Environment

• OS: Windows 10/11
• Install method: npm global install
• Version: 2026.3.13