WSL is not responding, the specified network name is no longer available

[aliuq]

Windows Version

Microsoft Windows [版本 10.0.27774.1000]

WSL Version

2.4.8.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

No response

Distro Version

No response

Other Software

No response

Repro Steps

After updating Windows, I found that WSL was not responding. There was no output when executing the wsl command and it kept loading. When I clicked to enter the Ubuntu directory through the file manager, I found that I could not enter it and was stuck. wsl.exe --list --online none can be executed successfully

Expected Behavior

Looking forward to normal access

Actual Behavior

nothing

Diagnostic Logs

WslLogs-2025-01-19_22-26-04.zip

[github-actions]

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:

• WSL not working after open Linux filesystem in windows 10 explorer (#10968), similarity score: 0.81
• No response when launching wsl in terminal (#10010), similarity score: 0.77
• WSL Service has stopped working after the latest update and reboot on Windows 11 (#12131), similarity score: 0.77
• wsl.exe hang after windows update (#10209), similarity score: 0.77
• WSL won't run Ubuntu (#7126), similarity score: 0.77

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

Diagnostic information

.wslconfig found
Detected appx version: 2.4.8.0

[aliuq]

Tried some of these methods, but still doesn't work

[aliuq]

Can anyone help? I don't want to lose my data, and I don't know if my data still exists on the local disk?

[zcobol]

@aliuq in an elevated powershell session run wsl --shutdown then hnsdiag reset all. This command will not touch your user data, so it's safe to run. It resets your WSL networking, and more.

hnsdiag.exe help:

Copyright (c) Microsoft Corporation. All rights reserved.

   hnsdiag <command> <object> [options ...]

   list <object> [id_1 id_2 ... id_n]
     Lists the specified object(s). If ids are given will list the ids.

   delete <object> <id_1> [id_2 ... id_n]
     Delete the specified object(s).

   reset <object>
     Delete all instances of the object.

   Objects
     All  (only valid when used with list, reset)
     Endpoints
     Loadbalancers
     Namespaces
     Networks

   Flags
     -d[f][l]
          Detailed option, when used with list, dumps the primitive json of the object.
        f
          Specifying 'f' will additionally give the full json of the object.
        l
          Specifying 'l' will additionally give the object in the latest schema version.

[aliuq]

@zcobol Thanks for your reply. I tried the command you mentioned, but it doesn't seem to work, and the time of wsl --shutdown is not reasonable either.

After restarting the computer, it still doesn’t work.

My operation process

1. Execute wsl --shutdown
2. Execute hnsdiag reset all
3. Test the wsl command
4. If it doesn’t work, restart the computer.
5. Test the wsl command

After waiting 20 minutes, an error occurred

> wsl
由于未安装所需的特性，无法启动操作。
错误代码: Wsl/Service/CreateInstance/CreateVm/HCS/HCS_E_SERVICE_NOT_AVAILABLE

[xdrew]

I have same problem just after the last insiders preview update (Windows 11 Insider Preview 27774.1000 (rs_prerelease)):

wsl
The operation could not be started because a required feature is not installed.
Error code: Wsl/Service/CreateInstance/CreateVm/HCS/HCS_E_SERVICE_NOT_AVAILABLE

The command above took about 40 minutes to run.

wsl --version
WSL version: 2.3.26.0
Kernel version: 5.15.167.4-1
WSLg version: 1.0.65
MSRDC version: 1.2.5620
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.27774.1000

[shadow3aaa]

I have same problem just after the last insiders preview update too...

[shadow3aaa]

I have same problem just after the last insiders preview update (Windows 11 Insider Preview 27774.1000 (rs_prerelease)):

wsl
The operation could not be started because a required feature is not installed.
Error code: Wsl/Service/CreateInstance/CreateVm/HCS/HCS_E_SERVICE_NOT_AVAILABLE

The command above took about 40 minutes to run.

wsl --version WSL version: 2.3.26.0 Kernel version: 5.15.167.4-1 WSLg version: 1.0.65 MSRDC version: 1.2.5620 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.26100.1-240331-1435.ge-release Windows version: 10.0.27774.1000

Reverting to the previous Windows version and executing bcdedit /set hypervisorlaunchtype Auto resolved my issue, though I'm not sure which one actually did the trick.

[xdrew]

I'm not sure which one actually did the trick

This must be reverting, cause the command did not work.

Sadly, reverting is not possible for me, cause when I tried it, it installed the same version and then disabled that button. Only fresh install remains which I do not consider as an option.

Thanks for sharing

[aliuq]

This problem is caused by the Windows 11 Insider Preview 27774.1000 (rs_prerelease) update. I checked the related hyper-v services and found that the vmms service will automatically stop during the execution of wsl -l -v

The solution is to roll back to the previous version Windows 11 Insider Preview 27768.1000 (rs_prerelease) through System-Recovery-Advanced Startup, then execute Start-Service vmms, and then everything returns to normal

Not sure this reason applies to everyone

View Hyper-V related services

Get-WindowsOptionalFeature -Online | Where-Object { $_.FeatureName -like "*Hyper-V*" }

View WSL related services

Get-WindowsOptionalFeature -Online | Where-Object { $_.FeatureName -like "*WSL*" -or $_.FeatureName -like "*VirtualMachinePlatform*" -or $_.FeatureName -like "*Linux*" }

View services

Get-Service -Name vmms, hvhost, wslservice

This problem has been bothering me for a long time