English
Appearance
English
Appearance
All of the issues below occur right after Windows boots (while the WSL VM is not yet warm, i.e. still in the cold-boot stage); once the VM is warm, things return to normal.
Most visible impact: right after Windows boots, opening the app shows no installed distros in the "distro list".
Why: wsldashboard enumerates the distro list via wsl -l -v (the list_distros function in src/wsl/ops/info.rs). During a slow VM cold boot, wsl -l -v also ends up queued waiting for the VM to be ready (see the table in "Overview" below), which causes:
Once the VM cold boot finishes, refreshing or restarting the app usually restores it.
/scheduler startup tasks slow down (but will eventually complete) /scheduler handles the background tasks at boot: distro auto-start, USB auto-attach, and port forwarding activation. During a slow VM cold boot, each of these steps has to wait for the VM to be ready:
So unless it is still not done after a long time (far beyond the VM cold-boot ceiling), no intervention is needed — it is essentially just waiting for the WSL environment to warm up.
Core idea: create a real cold boot, then time the "first distro launch".
Measure-Command { wsl -d Ubuntu -u root echo ok }Replace
Ubuntuwith your actual distro name (seewsl -l -q).
wsl --shutdown No system restart needed, but equivalent to a cold boot:
wsl --shutdown
Measure-Command { wsl -d Ubuntu -u root echo ok }| Duration | Conclusion |
|---|---|
| < 30 s (usually 5–10 s) | Normal, not affected |
| Clearly > 60 s, even minutes | Affected — hits the slow cold-boot issue |
Additional check: while running the test above, if wsl --version in another terminal still returns instantly but wsl -d ... takes a long time, that further confirms the slowness is in the VM cold boot, not the whole WSL service hanging.
In some combinations of Windows versions and WSL versions, the WSL 2 lightweight utility VM's cold boot is abnormally slow — normally launching a Linux distro takes only 5–10 s, but in affected environments it can take minutes.
Note: the "slowness" is in the VM's own cold boot — not how fast a specific Linux distro boots, and not the WSL service (LxssManager) itself hanging. You can use this distinction to tell it apart from ordinary failures:
| Command | Needs VM? | Behavior in affected environment |
|---|---|---|
wsl --version / wsl --status | No | Instant, normal |
wsl -l -v / wsl -l -q --running while the VM is starting | Yes | Blocks for minutes |
wsl -d <distro> ... (first launch) | Yes | Blocks for minutes |
| Windows version | WSL version | Kernel version | Source |
|---|---|---|---|
Windows 11 25H2 10.0.26200.9168 | 2.7.12 | 6.18.33.2 | Reproduced locally |
Windows 11 25H2 10.0.26200.9168 | 2.6.3 | — | Reproduced locally (shows WSL version is not the only variable) |
Windows 11 25H2 10.0.26200.8973 | 2.7.11 | 6.18.33.2 | microsoft/WSL#41253 |
Windows 11 25H2 10.0.26200.7623 | 2.7.0 | 6.6.114.1 | microsoft/WSL#14072 |
Windows 11 25H2 10.0.26200.8457 | 2.7.3 | — | microsoft/WSL#40616 |
Common factor: Windows 11 25H2 (build 26200) is the main trigger; it has been reported or reproduced across multiple WSL versions (2.6.3, 2.7.x).
wsl --shutdown, the first launch of any distro (VM cold boot) is slow.wsl commands return almost instantly.wsl command that needs VM state (e.g. wsl -l -v or wsl -l -q --running in another terminal) also blocks, because they all queue waiting for the VM to be ready.WSL version is confirmed to not be the only variable, so also pay attention to the following machine-level settings (.wslconfig lives at %USERPROFILE%\.wslconfig):
sparseVhd=false: disables sparse VHD; the virtual disk is fixed-allocated and heavier to mount, which can slow cold boot.memory=8GB + swap=4GB and other large memory reservations: reserving a big chunk of memory + swap at cold boot can trigger paging when the host is low on RAM, noticeably lengthening startup.dnsTunneling=true + autoProxy=true: network stack initialization may add extra latency.wsl --version (if a downgrade still shows the old version, run wsl --update or restart to confirm it took effect).%USERPROFILE%\.wslconfig, then wsl --shutdown and re-test cold boot to see if it recovers.sparseVhd first).C:\Program Files\WSL\).The slow cold boot is an environment-level issue, mainly related to Windows 25H2 (build 26200), reproduced across multiple WSL versions; it currently cannot be sped up by application-level code. For wsldashboard, the only thing we can do is adopt bounded probing + concurrent polling + timeout degradation in the scheduling path, avoiding a single blocking black hole and ensuring that business logic eventually lands correctly — not "accelerating" the VM itself.
The root cause must be fixed by the Microsoft WSL development team at the underlying VM cold-boot layer; the application side can only mitigate and degrade. It is recommended to follow the official progress on the GitHub issues listed under "Related links" above.