Skip to content

WSL VM Cold Boot Extremely Slow ​

1. Impact (on wsldashboard) ​

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.

1.1 App shows no distro list on open ​

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:

  • The UI stays blank for a long time and shows no installed distros;
  • Downstream actions that depend on that list (start/stop, port proxy sync, USB attach, status refresh) cannot proceed normally;
  • Users may wrongly think "distros are lost" or "the app is broken", when in fact the status simply cannot be queried — no data is lost.

Once the VM cold boot finishes, refreshing or restarting the app usually restores it.

1.2 /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:

  • The overall flow stretches from "seconds" to "minutes" (consistent with the ~4.5 min measured on this machine);
  • It looks "stuck", but it is not failing — as long as the VM eventually becomes ready, these tasks will definitely complete (distros get started, USB gets attached, port forwarding gets applied).

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.

2. How to check if you are affected ​

Core idea: create a real cold boot, then time the "first distro launch".

  1. Restart Windows 11.
  2. Once boot completes, immediately open PowerShell (admin or non-admin).
  3. Run:
powershell
Measure-Command { wsl -d Ubuntu -u root echo ok }

Replace Ubuntu with your actual distro name (see wsl -l -q).

Method B: cold-boot test via wsl --shutdown ​

No system restart needed, but equivalent to a cold boot:

powershell
wsl --shutdown
Measure-Command { wsl -d Ubuntu -u root echo ok }

Result interpretation ​

DurationConclusion
< 30 s (usually 5–10 s)Normal, not affected
Clearly > 60 s, even minutesAffected — 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.

3. Overview ​

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:

CommandNeeds VM?Behavior in affected environment
wsl --version / wsl --statusNoInstant, normal
wsl -l -v / wsl -l -q --running while the VM is startingYesBlocks for minutes
wsl -d <distro> ... (first launch)YesBlocks for minutes

4. Affected environments (reported / reproduced) ​

Windows versionWSL versionKernel versionSource
Windows 11 25H2 10.0.26200.91682.7.126.18.33.2Reproduced locally
Windows 11 25H2 10.0.26200.91682.6.3—Reproduced locally (shows WSL version is not the only variable)
Windows 11 25H2 10.0.26200.89732.7.116.18.33.2microsoft/WSL#41253
Windows 11 25H2 10.0.26200.76232.7.06.6.114.1microsoft/WSL#14072
Windows 11 25H2 10.0.26200.84572.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).

5. Symptoms ​

  1. Happens only on cold boot: right after restarting Windows, or after wsl --shutdown, the first launch of any distro (VM cold boot) is slow.
  2. Warm boot is normal: once the VM is already running, wsl commands return almost instantly.
  3. It "hangs" rather than "errors": the command just never returns, with no visible error output.
  4. Knock-on effect: during the VM cold boot, any 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.
  5. Typical duration degrades from the normal 5–10 s to minutes, intermittent or consistently reproducible.

7. Factors that may magnify the issue (troubleshooting) ​

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.
  • Antivirus real-time scanning of VHDX / VM processes (interference seen in some environments).

Troubleshooting / workarounds ​

  1. Confirm the version first: wsl --version (if a downgrade still shows the old version, run wsl --update or restart to confirm it took effect).
  2. Temporarily back up and empty %USERPROFILE%\.wslconfig, then wsl --shutdown and re-test cold boot to see if it recovers.
  3. If it recovers, add the config back one line at a time to bisect and identify the specific line (suspect sparseVhd first).
  4. If it is still slow, consider Hyper-V / Virtual Machine Platform cold boot, or antivirus exclusions for WSL's vhdx and install directory (C:\Program Files\WSL\).

8. Conclusion ​

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.