From ad97d2cab062475f932c89cd9f433498c178b74d Mon Sep 17 00:00:00 2001 From: Ma Date: Wed, 24 Jun 2026 22:26:54 -0700 Subject: [PATCH] update known issue --- superclaw/README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/superclaw/README.md b/superclaw/README.md index b72f30dd..a356a856 100644 --- a/superclaw/README.md +++ b/superclaw/README.md @@ -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. +- **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.