WSL 2.3.14 doesn't work on Windows 2025 (but 2.2.4 does)

[joshmouch]

Windows Version

Windows 2025 DataCenter (10.0.26257.5000)

WSL Version

2.3.14

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

6.6.36.3-1

Distro Version

Any

Other Software

No response

Repro Steps

On Windows Server 2025 DataCenter preview, upgrade to the latest preview version of WSL.

Expected Behavior

Normal WSL behavior.

Actual Behavior

Aside from "mirror" mode not being supported, WSL has been working well with Windows DataCenter 2025 preview.
However, I just tried upgrading the latest WSL preview (2.3.14) and nothing seems to work.
If I try to start a distro, I get:

PS C:\Users\administrator.MOUCH> wsl
A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied.
Error code: Wsl/Service/CreateInstance/CreateVm/WSAENOTCONN

If I try to run with --debug-shell then I get something close to (not exactly):
Error code: NOT FOUND Wsl/DEBUGSHELL/...

If I uninstall WSL and then reinstall it with the latest "stable" version (2.2.4), then everything's back to normal.

Then I tried updating to the latest preview again, with the same result.

Diagnostic Logs

No response

[github-actions]

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 wsl-gh-logs@microsoft.com 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'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Closed similar issues:

• WSL2 distro can't start: the remote procedure call failed (build 20211) (#5907), similarity score: 0.74
• WSL2 can't start any distro on Server 2022 (#8558), similarity score: 0.74
• [SEVERE] Cannot use / run wsl headlessly on fresh Windows 2022 install (#9057), similarity score: 0.73
• WSL2 on Win10 will not start after recent windows update (#7922), similarity score: 0.72
• WSL2/Distro doesn't start after Windows update on 10/13/2020 (#6091), similarity score: 0.72

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[JustLookAtNow]

#11791 (comment) just try it!

[elsaco]

Using non-store upgrade it worked on 10.0.26257.5000. The .wslconfig has only cpu and memory limits, no other custom settings were used:

PS C:\Users\Elsaco> wsl --version
WSL version: 2.2.4.0
Kernel version: 5.15.153.1-2
WSLg version: 1.0.61
MSRDC version: 1.2.5326
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26091.1-240325-1447.ge-release
Windows version: 10.0.26257.5000
PS C:\Users\Elsaco> wsl --update --pre-release
Checking for updates.
Updating Windows Subsystem for Linux to version: 2.3.14.
PS C:\Users\Elsaco> wsl --version
WSL version: 2.3.14.0
Kernel version: 6.6.36.3-1
WSLg version: 1.0.64
MSRDC version: 1.2.5326
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.26257.5000
PS C:\Users\Elsaco> wsl
elsaco@PORTLAND:/mnt/c/Users/Elsaco$ cd
elsaco@PORTLAND:~$ wslinfo --wsl-version
2.3.14
elsaco@PORTLAND:~$ wslinfo --networking-mode
nat

PS C:\Users\Elsaco> cat .\.wslconfig
[wsl2]
processors=4
memory=4294967296
swap=0

@joshmouch you could try w/out custom setting and see if it works. It helps sometimes! Also, try running hnsdiag reset all in an elevated shell.

[microsoft-github-policy-service]

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue.

Thank you!