You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
wsldevicehost DllHost surrogate persists after wsl --shutdown and grows threads/handles every VM cycle #42324
The device-host surrogate should stop accumulating resources when the VM stops, and the thread/handle count should return to the idle baseline after wsl --shutdown.
Actual Behavior
One DllHost.exe /Processid:{17696EAC-9568-4CF5-BB8C-82515AAD6C09} surrogate stays alive after the VM stops and keeps wsldevicehost.dll loaded. Its threads and handles grow every cycle and never drop back:
Point
Threads
Handles
baseline (no surrogate)
–
–
after start 1
23
194
after shutdown 1
21
179
after start 2
24
220
after shutdown 2
22
204
after start 3
28
242
after shutdown 3
26
227
(A separate 5-thread DllHost.exe that loads only vmdevicehost.dll appears for each VM start and exits on shutdown — that one behaves correctly.)
On a machine with 10 days of uptime and ordinary interactive wsl.exe use, the same persistent surrogate had:
1,678 threads, 7,269 handles, ~2 MB working set
all 1,670 idle threads in UserRequest wait, 8 in Unknown
Ubuntu reported Stopped for the whole time it was observed
Stopping that process freed ~7,000 handles, but it reappeared with the next WSL start and began growing again. This looks related to #42051 (the same AppID and wsldevicehost), but that issue covers one leaked process per VM started from session 0; here it is unbounded thread/handle growth inside a single long-lived surrogate.
If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise, please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.
How to collect WSL logs
Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
The script will output the path of the log file once done.
If this is a networking issue, please use .\collect-wsl-logs.ps1 -LogProfile networking instead, following the instructions in Collect WSL logs for networking issues
Once completed please upload the output files to this GitHub issue.
If you choose to email these logs instead of attaching them to the bug, please send them to wsl-gh-logs@microsoft.com with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.
Activity
github-actions commentedon Nov 21, 2026
Logs are required for review from WSL team
If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise, please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.
How to collect WSL logs
Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
The script will output the path of the log file once done.
If this is a networking issue, please use
.\collect-wsl-logs.ps1 -LogProfile networkinginstead, following the instructions in Collect WSL logs for networking issuesOnce completed please upload the output files to this GitHub issue.
See Collect WSL logs (recommended method).
If you choose to email these logs instead of attaching them to the bug, please send them to wsl-gh-logs@microsoft.com with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.
jsperry0807-rgb commentedon Nov 21, 2026
WslLogs-2026-11-21_16-04-23-redacted.tar.gz
github-actions commentedon Nov 21, 2026
Diagnostic information