Platform
Windows
Wayland Version
v0.11.18
Bug Description
Wayland cannot execute any shell command.
Every command (including a simple echo ok) fails with:
Failed to execute command: sandbox child timed out
After four retries, Wayland displays the "Stopped a runaway loop" dialog.
Because the execution environment never starts, shell-based features such as Office rendering cannot run.
Steps to Reproduce
- Open Wayland v0.11.18 on Windows 11 Pro.
- Create a brand-new empty project.
- Send:
echo ok
- Observe the result.
Expected Behavior
The command executes successfully and returns:
ok
Actual Behavior
Every shell command fails with:
Failed to execute command: sandbox child timed out
Wayland retries four times and then displays the "Stopped a runaway loop" dialog.
The same behavior occurs in a brand-new empty project.
Additional Context
Environment
- Windows 11 Pro
- Wayland v0.11.18
- Installed using the official Windows installer
Diagnostics already performed
- Rebooted Windows
- Restarted Wayland
- Created a brand-new empty project
- Same behavior in every project
- Windows Defender Protection History shows no blocks
- Controlled Folder Access is OFF
- Node.js is installed and working
- npm is installed and working
Verified:
where node
-> C:\Program Files\nodejs\node.exe
where npm
-> C:\Program Files\nodejs\npm
-> C:\Program Files\nodejs\npm.cmd
The bundled Bun runtime also executes normally outside Wayland:
"C:\Program Files\Wayland\resources\bundled-bun\win32-x64\bun.exe" --version
Output:
1.3.14
The Wayland installation appears complete, including:
- bundled-bun
- bundled-wayland-core
- bundled-workflows
Since the bundled Bun runtime executes correctly outside Wayland, it appears the failure occurs before or during Wayland's sandbox/child-process execution rather than inside Bun itself.
I'm happy to provide additional logs or run diagnostic builds if needed.
Platform
Windows
Wayland Version
v0.11.18
Bug Description
Wayland cannot execute any shell command.
Every command (including a simple
echo ok) fails with:Failed to execute command: sandbox child timed out
After four retries, Wayland displays the "Stopped a runaway loop" dialog.
Because the execution environment never starts, shell-based features such as Office rendering cannot run.
Steps to Reproduce
echo ok
Expected Behavior
The command executes successfully and returns:
ok
Actual Behavior
Every shell command fails with:
Failed to execute command: sandbox child timed out
Wayland retries four times and then displays the "Stopped a runaway loop" dialog.
The same behavior occurs in a brand-new empty project.
Additional Context
Environment
Diagnostics already performed
Verified:
where node
-> C:\Program Files\nodejs\node.exe
where npm
-> C:\Program Files\nodejs\npm
-> C:\Program Files\nodejs\npm.cmd
The bundled Bun runtime also executes normally outside Wayland:
"C:\Program Files\Wayland\resources\bundled-bun\win32-x64\bun.exe" --version
Output:
1.3.14
The Wayland installation appears complete, including:
Since the bundled Bun runtime executes correctly outside Wayland, it appears the failure occurs before or during Wayland's sandbox/child-process execution rather than inside Bun itself.
I'm happy to provide additional logs or run diagnostic builds if needed.