Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Error code: Wsl/Service/CreateInstance/CreateVm/WSAENOTCONN #11840

Closed
1 of 2 tasks
josefschroettle opened this issue Jul 26, 2024 · 11 comments
Closed
1 of 2 tasks

Error code: Wsl/Service/CreateInstance/CreateVm/WSAENOTCONN #11840

josefschroettle opened this issue Jul 26, 2024 · 11 comments
Assignees
@chessturo

Comments

@josefschroettle
Copy link

Windows Version

Microsoft Windows [Version 10.0.22631.3958]

WSL Version

2.3.13.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

Unknown, distro does not start

Distro Version

Ubuntu-22.04

Other Software

N/A

Repro Steps

Install wsl.2.3.13.0.x64.msi
Try to start distro

Expected Behavior

Distro starts

Actual Behavior

Eine Anforderung zum Senden oder Empfangen von Daten wurde verhindert, da der Socket nicht verbunden ist und (beim Senden über einen Datagrammsocket mit einem sendto-Aufruf) keine Adresse angegeben wurde.
Error code: Wsl/Service/CreateInstance/CreateVm/WSAENOTCONN
Press any key to continue...

Diagnostic Logs

No response
@github-actions GitHub Actions
Copy link

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'.

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!

Open similar issues:

Closed similar issues:

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

@josefschroettle
Copy link
Author

The behaviour is seen with 2.3.11, 2.3.12 and 2.3.13
When reverting back to 2.2.4 everything works normal again
Config file .wslconfig has been removed for this test

@josefschroettle
Copy link
Author

Here the logs from a failed start of distro Ubuntu-22.04

WslLogs-2024-07-26_08-59-30.zip

@github-actions GitHub Actions
Copy link

Diagnostic information 
Detected appx version: 2.3.13.0
Detected user visible error: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/0x80072746
Found evidence of kernel panic: [    0.203298] Kernel panic - not syncing: Fatal exception in interrupt

@josefschroettle
Copy link
Author

This has to be related to my machine configuration. I tried 2.3.13 in a virtual machine (hyper-v) with wsl and it works there.
I am currently using 'Realtek Gaming 2.5GbE Family Controller' as primary network device, could it be related to Realtek drivers?

@chessturo chessturo self-assigned this Jul 26, 2024
@bowling233
Copy link

Having the same issue in Windows version: 10.0.26120.1330

> wsl --version
WSL version: 2.3.13.0
Kernel version: 6.6.36.3-1
WSLg version: 1.0.63
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.26120.1330
> 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

Here is the logs collected by collect-wsl-logs.ps1:

WslLogs-2024-07-28_01-41-55.zip

I'm also using 'Realtek Gaming 2.5GbE Family Controller' as primary network device.

@xiezhipeng-git
Copy link

Microsoft Windows [版本 10.0.22631.3958]
(c) Microsoft Corporation。保留所有权利。

C:\Users\Admin>wsl --version
WSL 版本： 2.2.4.0
内核版本： 5.15.153.1-2
WSLg 版本： 1.0.61
MSRDC 版本： 1.2.5326
Direct3D 版本： 1.611.1-81528511
DXCore 版本： 10.0.26091.1-240325-1447.ge-release
Windows 版本： 10.0.22631.3958

C:\Users\Admin>wsl
无法将磁盘“C:\Users\Admin\AppData\Local\Packages\CanonicalGroupLimited.Ubuntu22.04LTS_79rhkp1fndgsc\LocalState\ext4.vhdx”附加到 WSL2： 文件或目录损坏且无法读取。
Error code: Wsl/Service/CreateInstance/MountVhd/HCS/0x80070570
when I write code with vscode.
Suddenly, VSCode crashes and WSL cannot be opened. Reported this error. How to solve it?
@chessturo

@xiezhipeng-git
Copy link

NodeExecServer run: C:\windows\System32\wsl.exe -d Ubuntu-22.04 -e sh -c if [ -d ~/.vscode-server/bin/f1e16e1e6214d7c44d078b1f0607b2388f29d729 ]; then printf 'install-found '; fi; if [ -f /etc/alpine-release ]; then printf 'alpine-'; fi; if [ -s ~/.vscode-server/bin/compatibilty-check ]; then printf 'legacy-'; fi; uname -m;
[2024-07-28 08:46:42.199] Unable to detect if server is already installed: Error: Failed to probe if server is already installed: code: Failed to probe if server is already installed: code: 4294967295, , �e�l\�x�v C:\Users\Admin\AppData\Local\Packages\CanonicalGroupLimited.Ubuntu22.04LTS_79rhkp1fndgsc\LocalState\ext4.vhdx D��R0R WSL2� �e�Nb�vU__cOWN�e�l���S0
[2024-07-28 08:46:42.199] Error code: Wsl/Service/CreateInstance/MountVhd/HCS/0x80070570
[2024-07-28 08:46:42.199]
[2024-07-28 08:46:42.199] NodeExecServer run: C:\windows\System32\wsl.exe -d Ubuntu-22.04 sh -c '"$VSCODE_WSL_EXT_LOCATION/scripts/wslServer.sh" f1e16e1e6214d7c44d078b1f0607b2388f29d729 stable code-server .vscode-server --host=127.0.0.1 --port=0 --connection-token=4216714420-1561004773-1456349802-1130381406 --use-host-proxy --without-browser-env-var --disable-websocket-compression --accept-server-license-terms --telemetry-level=all'
[2024-07-28 08:46:42.235] �e�l\�x�v C:\Users\Admin\AppData\Local\Packages\CanonicalGroupLimited.Ubuntu22.04LTS_79rhkp1fndgsc\LocalState\ext4.vhdx D��R0R WSL2� �e�Nb�vU__cOWN�e�l���S0
[2024-07-28 08:46:42.235] Error code: Wsl/Service/CreateInstance/MountVhd/HCS/0x80070570
[2024-07-28 08:46:42.235]
[2024-07-28 08:46:42.235] 有关启动问题的帮助，请转到 https://code.visualstudio.com/docs/remote/troubleshooting#_wsl-tips
[2024-07-28 08:46:52.165] Download in background is enabled
This is open vscode info

@xiezhipeng-git
Copy link

log
WslLogs-2024-07-28_16-56-38.zip

@xiezhipeng-git
Copy link

error code not same.I will create new

@xiezhipeng-git xiezhipeng-git mentioned this issue Jul 28, 2024
Closed
2 tasks
@chessturo
Copy link
Collaborator

Closing as a dup of #11791. We have a temporary fix listed there --- if the fix does not work for you, please let me know.

@chessturo chessturo closed this as not planned Won't fix, can't repro, duplicate, stale Jul 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@chessturo chessturo

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@xiezhipeng-git @josefschroettle @bowling233 @chessturo