Skip to content

update known issue #82

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kimtaeyo merged 1 commit into from
Jun 25, 2026
Merged

update known issue #82

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion superclaw/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -129,7 +129,8 @@ Minimal public-channel setup: `app_mentions:read`, `channels:read`, `chat:write`
---

## Known Issues
- **Hardware virtualization is required.** If installation fails, enable Intel VT-x or Intel Virtualization Technology in BIOS/UEFI, restart Windows, and run the installer again. On managed PCs, contact your IT administrator if the setting is locked.
- **CPU virtualization is required to install WSL.** SuperClaw uses WSL, which requires CPU virtualization to be enabled in BIOS/UEFI. If installation fails, enable Intel Virtualization Technology, also called Intel VT-x, restart Windows, and run the installer again. On managed PCs, contact your IT administrator if the setting is locked or unavailable.
Comment thread
MiaomiaoMaIntel marked this conversation as resolved.
- **Restart Windows after installing WSL.** If WSL is installed during setup and Windows is not restarted, the SuperClaw installer may stop around 10%. Restart Windows, then run the installer again so the WSL components are fully available.
- **WSL repair may be needed if installation stops around 10%.** If `wsl.exe` reports `Wsl/CallMsi/Install/REGDB_E_CLASSNOTREG` or says WSL is corrupted, open PowerShell as Administrator, run `wsl --install --no-distribution`, restart Windows, and run the installer again. If needed, run `wsl --update` as Administrator, restart, and try again.
- **`owt.failed` can mean the backend is unreachable or loopback traffic is proxied.** If `http://127.0.0.1:8787/health` returns `403 Forbidden`, add `127.0.0.1,localhost,::1` to your user `NO_PROXY` setting, keeping any existing corporate entries, then stop SuperClaw and relaunch it from a new terminal. If it is still stuck, stop SuperClaw, run `wsl.exe --unregister superclaw-docker`, and relaunch.
- **Corporate networks may require proxy setup before installation.** If your corporate network requires a proxy for downloads, configure the required HTTP proxy before installing SuperClaw. On an open network, no proxy setup is needed. If you switch between a corporate network and an outside network, quit SuperClaw, run `wsl.exe --unregister superclaw-docker`, and reopen the app so the backend is recreated with the current network settings.
Expand Down