WSL sometimes freezes and the disk usage stuck at 100%.

[ChenPi11]

Windows Version

Microsoft Windows [版本 10.0.26100.4652] (Microsoft Windows [Version 10.0.26100.4652])

WSL Version

2.5.9.0

Are you using WSL 1 or WSL 2?

• [x] WSL 2
• [ ] WSL 1

Kernel Version

6.6.87.2-1

Distro Version

Debian GNU/Linux (sid)

Other Software

Microsoft Visual Studio Code 1.101.2 with WSL extension 0.99.0

Repro Steps

This bug is hard to reproduce. It happens if I suspend my system (especially suspend for more than 12h) and working on VSCode for a period of time. Resume the system and continue to work on VSCode will cause this problem probability. Only restart WSL will not relieve the problem. Reboot Windows can relieve it.

Expected Behavior

Don't freezes witth the disk usage stuck at 100%.

Actual Behavior

It happens in two forms:

1. WSL freezes and the disk usage stuck at 100%. It lasts for a period of time then resume.

2. WSL freezes and the disk usage stuck at 100% forever until wsl --shutdown.

If this occured, every window and even mouse will nearly freezed. It's hard to capture the screenshot above.

In short, it’s hard to reproduce and difficult to capture, but once it happens, it has a significant impact.

Diagnostic Logs

No response

[github-actions[bot]]

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:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

[ChenPi11]

WslLogs-2025-07-14_15-29-13.zip

[ChenPi11]

This logs contains a short freeze.

[github-actions[bot]]

Diagnostic information

.wslconfig found
Detected appx version: 2.5.9.0

[m-salman-afzal]

having the same issue

[ChenPi11]

now my wsl getting stucked more frequently. I need to reboot it about 10 times a day.😡

[ChenPi11]

having the same issue

Are you using VSCode for developing? It seems that the process in WSL does not have enough memory. Then Vmmem will use swap to relieve it. This will cause high occupation in disk usage.

VmmemWSL seems having a very high level in IO scheduling. It occupied 100% disk IO resource. Then the kernel will crash because disk IO timeout.

[ChenPi11]

VSCode extensions have a large memory usage. They may easily causing insufficient memory.

[IonutDaniel99]

I have the same problem. My expectation its that "Copilot suggestions + Eslint/pylint" increase my SDD to 100%.

Tested it when I put the copilot into "snooze" and had no problems for 20 minutes. After he left the snooze and started "in line recommendation" .. the SDD goes rocket agian

[Kariamos]

I am experiencing the same issue as soon as I open vscode with suggestions and linter

[gabrielrbarbosa]

Also using phpstorm + docker and running any command like rector or phpstan make it crash and reach 100% disk usage