-
-
Notifications
You must be signed in to change notification settings - Fork 1
WSLC Not Found
WSLC was not found.
Checked:
wslc.exe
wslc
/mnt/c/Windows/System32/wslc.exe
Install or update the WSL container tooling, then run:
wip doctor
Every wip command except wip version fails with this when the wslc binary can't
be resolved.
With wslc.command: auto (the default), wip tries, in order:
-
wslc.exe— searched acrossPATH -
wslc— searched acrossPATH -
/mnt/c/Windows/System32/wslc.exe— checked directly
The first one that is executable wins. A name containing a path separator is checked with
File.executable? directly; a bare name is looked up in every PATH entry.
With any other value, that exact value must be executable — there is no fallback:
wslc:
command: /mnt/c/Program Files/WSL/wslc.exeWSLC was not found.
Checked:
/mnt/c/Program Files/WSL/wslc.exe
Is it there at all?
which wslc.exe wslc
ls -l /mnt/c/Windows/System32/wslc.exe
wslc.exe versionIs Windows interop enabled? Without it, WSL can't execute .exe files at all — which looks
identical to "not installed":
wip doctor[FAIL] Windows executable interoperability is disabled
Fix in /etc/wsl.conf, then wsl --shutdown from Windows:
[interop]
enabled = true
appendWindowsPath = trueIs System32 on your PATH? appendWindowsPath = false in /etc/wsl.conf removes Windows paths
from PATH, so wslc.exe won't be found by name. That's exactly what the third candidate covers —
but only for the default install location.
Install Microsoft's WSL container tooling on the Windows side, then confirm from Windows itself before returning to WSL:
wslc versionIf it lives somewhere non-standard:
wslc:
command: /mnt/c/Tools/wslc/wslc.exeVerify:
ls -l /mnt/c/Tools/wslc/wslc.exe # must be executable
wip doctorwip runs there too. wslc.exe needs to be on PATH, or named absolutely with a Windows path:
wslc:
command: C:\Program Files\WSL\wslc.exe[OK] Found wslc.exe
[FAIL] WSLC version failed
Different problem: the binary exists and is executable but doesn't respond to version. Usually a
partial or broken install, or a stale shim on PATH shadowing the real binary. Check what you're
actually resolving:
which -a wslc.exe wslc$ wip doctor
[OK] Found wslc.exe
[OK] WSLC is available-
Config File Discovery — the
wslc:block - wip doctor
- wip version
Introduction
Modes
Configuration
- Configuration Reference
- Config File Discovery
- Dependencies
- Networking
- Interactions
- Restart Policies
- Env Files
- Secret Masking
- Dockerignore
- Shadow Build Context
- Source Sync
- Sync Modes
compose.yml support
- Compose File Support
- Compose Build
- Compose Depends On
- Compose Profiles
- Compose Variable Interpolation
Commands
- CLI Command Reference
- wip init
- wip version
- wip doctor
- wip config
- wip build
- wip up
- wip stop
- wip down
- wip exec
- wip run
- wip shell
- wip logs
- wip sync
- wip dispatch
- Global Options
- Debug Output
- TTY Allocation
Guides
- Guides
- Migrating from dip
- Reusing an Existing compose.yml
- Fixing a Slow Boot
- Continuous Sync
- Auto Restarting Containers
- Multi Arch Images
- Using wip in CI
Troubleshooting
- Troubleshooting & FAQ
- FAQ
- Configuration Errors
- WSLC Not Found
- Registry Authentication
- Architecture Mismatch
- Volume Limit Reached
- rsync Not Found
- Reporting Issues
Comparison
Project