openclaw - 💡(How to fix) Fix Windows: browser screenshot and inbound media fail with EPERM on directory fsync

Summary

On Windows, \openclaw browser screenshot\ always fails with: \
GatewayClientRequestError: Error: EPERM: operation not permitted, fsync \\

Inbound media from Telegram (images sent by user) also fails silently with the same error, making it impossible to receive image attachments.

Root Cause

The issue is that \sync()\ on a directory file descriptor is not supported on Windows — it returns \EPERM\ by design. This is a known Windows/libuv limitation (nodejs/node#3879).

Reproduction: \\js const fs = require('fs'); const fd = fs.openSync('C:\\Windows\\Temp\\openclaw', fs.constants.O_RDONLY); fs.fsyncSync(fd); // → EPERM: operation not permitted, fsync \\

File-level fsync works fine; only directory-level fd fsync fails.

Environment

• OS: Windows 11 (10.0.26200, x64)
• Node.js: v24.13.1
• OpenClaw: 2026.5.2
• Channel: Telegram

Impact

1. \openclaw browser screenshot\ → always fails (unusable on Windows)
2. User-sent images via Telegram → \media fetch failed\ (cannot receive photo attachments)

Expected Fix

Skip or catch the EPERM when calling \sync\ on a directory fd on Windows (\process.platform === 'win32'). The temp file write itself succeeds; the directory fsync is not necessary for correctness on Windows.

Workaround (current)

Capture screenshots via CDP WebSocket directly and save with \s.writeFileSync, bypassing the OpenClaw screenshot API.