WSL: WSL Freezing 0x8007274c
Windows Version
10.0.22621.1413
WSL Version
1.1.3.0
Are you using WSL 1 or WSL 2?
- WSL 2
- WSL 1
Kernel Version
5.15.90.1-microsoft-standard-WSL2
Distro Version
Ubuntu 22.04.1 LTS
Other Software
- Docker Desktop (Windows) version 4.17.0
- PhpStorm 2022.3.3
- WebStorm 2022.3.3
Versão do WSL: 1.1.3.0
Versão do kernel: 5.15.90.1
Versão do WSLg: 1.0.49
Versão do MSRDC: 1.2.3770
Versão do Direct3D: 1.608.2-61064218
Versão do DXCore: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows versão: 10.0.22621.1413
Repro Steps
Every that I set up my development applications (such as Docker, PhpStorm, WebStorm, etc), it starts to happen repeatedly throughout the day.
- start Ubuntu in WSL along with the others apps
- use it for a while
- after some time, if I try to open a new WSL terminal, I got
Error code: Wsl/Service/0x8007274c - PhpStorm and WebStorm start to report failed connection attempts to WSL as well (e.g. during sync git status)
Additional Information:
I started to experience it since from Windows 10 22H2 update. After a while, I did a fresh Windows 11 install, and the behavior is still happening.

Expected Behavior
Terminals and apps work without hangs.
Actual Behavior
- WSL terminals stucked
- high CPU on VmmemWSL Windows background process
- apps that needs to connect with WSL cannot work properly
To be able to continue to work:
- wsl --shutdown (sometimes, multiple times)
- Docker desktop has to be restarted
Diagnostic Logs
No response
About this issue
- Original URL
- State: open
- Created 4 years ago
- Reactions: 23
- Comments: 15 (1 by maintainers)
This is happening to me constantly lately. since I started working on a project where I need to run front-end and back-end servers at the same time, and one docker container running a postgreSQL and I’m coding with VsCode, my machine got 16Gb RAM, and I’m not using .wslconfig, but I read the WSL docs and it tells me that the default RAM is 50% windows RAM, so I think maybe the problem is not a RAM problem, maybe something with vscode and/or some plugin.
Continuing to be a problem, after turning my computer on and opening the Ubuntu app, I get
So far, the only workaround I have found is to open a cmd prompt and run
wsl --shutdownand restart WSLSo, after the fresh Windows 11 install, I tried the “free memory” mode, with no explicit configuration on the
.wslconfigbefore and I was seeing the same behavior. Same as well when I put 8GB.With no explicit configuration, the
VmmemWSLprocess almost hits 8GB of usage (the PC has 16GB total), but with the same behavior that I described.While I was trying to found a solution through internet, I saw some hints to put
guiApplications=falseinto.wslconfig. But, it did not help too much. Only the high CPU usage ofVmmemWSLwas mitigated.Thanks @andersonams. Looking at the logs, it looks like the issue is that WSL is out of memory.
Does increasing
wsl2.memoryto let’s say 8GB help ?