Blue

FYI, to format the code to our clang-format rules, you can run `powershell .\FormatSource.ps1 -ModifiedOnly $false`. You can also enable clang-format in VS for that to be done automatically.

> Note: msipackage does not build locally due to missing clang/MSBuild tooling, but wsladiag.exe builds and runs normally. Please confirm the MSI wiring (BINARIES + File entry) looks correct. The...

/logs

Thanks @andersonams. Looking at the logs, it looks like the issue is that WSL is out of memory. Does increasing `wsl2.memory` to let's say 8GB help ?

Thank you for reporting this @ImranKamaluddin. Could you share a [TDD trace of the wsl.exe process](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#12-collect-wslservice-time-travel-debugging-traces) capturing this ? (make sure to include subprocesses as well so we can see...

@ImranKamaluddin: Sorry if I was unclear, do what we'd need here is a TDD trace of `wsl.exe` (the executable causing the loop), not wslservice.exe

If the file is too big for Github, a OneDrive / GDrive share link would be the easiest way to share the .zip

Thank you for reporting this @cooperoptigrid. Could you share which PATH you have set in that shell ? I wonder if there's a parsing bug in wsl.exe. For PowerShell: ```...

Thank @cooperoptigrid. I can't reproduce the issue directly in WSL, so just checking, if you run wsl.exe outside of vscode, do you see the same issue or do things work...

@CatalinFetoiu: Looks like this is caused by a failure to allocate a port range: ``` Microsoft.Windows.Lxss.Manager Error 0 10-10-2025 14:16:22.620 " " "code: failurecount: 102 file: C:\__w\1\s\src\windows\service\exe\WslCoreGuestNetworkService.cpp function: hr: 0x8007054F...