Vmmem or vmmemWSL grabs 8 GB in Task Manager and won't release it, even after closing WSL.
WSL2 runs in a lightweight VM and holds memory as cache. By default it releases slowly, but you can cap it and tune behavior via .wslconfig.
Try this first
- 1Create %USERPROFILE%\.wslconfig (literally in your home, not in the distro). Open in Notepad.
- 2Add a [wsl2] section with memory and processors, for example 'memory=4GB' and 'processors=4'. Tune to your RAM and workload.
- 3Optionally 'swap=2GB' and 'localhostForwarding=true'. 'autoMemoryReclaim=gradual' (Windows 11, recent WSL) returns memory automatically.
- 4Fully shut down WSL with 'wsl --shutdown' in PowerShell, then 'wsl' to restart. Without shutdown the old config stays loaded.
- 5Verify with 'free -m' inside WSL and Task Manager on the Windows side. Vmmem should stay within the cap now.
- 6Keep devs informed: a low cap makes large project builds fail with OOM instead of swapping.
When to bring us in
If vmmem keeps growing past the cap or the distro crashes, check the WSL version with 'wsl --version' and update the component. Persistent leaks belong on the upstream issue tracker.
See also
- My laptop is suddenly slowThree main suspects: a runaway background process, near-full disk, or a Windows update in progress.
- One specific application is slow for everyoneIf an app is slow for one person: local. For everyone at once: server side or vendor side.
- Opening files from the file server takes minutesOften the server itself is fine and the issue is network routing or stalling DNS resolution.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.