Share via

My WSL 2 is not starting, nor responding to any commands.

Anonymous
2024-02-13T18:30:58+00:00

Hello, I have been using WSL for a while, and today I tried to update WSL.

I ran wsl --update in cmd and it completed the update. However, now my WSL will not start.

When I try to start WSL, the WSL Console opens, but nothing happens. The Window stays black.

I tried to uninstall and Reinstall WSL multiple times, but no luck. The result is the same.

I have also tried running the following commands:

'wsl -l' to list installed distriburions. This Command hangs infinitely and does nothing, until interrupted by Ctrl-C.

'wsl --shutdown' has the same effect.

'wslconfig /l' also hangs. The same for 'wslconfig /t Debian'

'wsl --install Debian' tries to install the Distro, but gives the following error message:
"An error occurred while deleting the package's previously existing application data.

Error code: Wsl/InstallDistro/0x80073d05"

My WSL version (shown by 'wsl -v'):

WSL version: 2.0.14.0

Kernel version: 5.15.133.1-1

WSLg version: 1.0.59

MSRDC version: 1.2.4677

Direct3D version: 1.611.1-81528511

DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp

Windows version: 10.0.19045.3930

I would appreciate any help.

Windows for home | Windows 10 | Install and upgrade

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

10 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-08-19T07:38:28+00:00

    Here is a [temporary] fix I found. With WSL terminal hung, run in the windows prompt shell:

    1. tasklist | findstr wsl
    2. taskkill /PID wslservice.exe_PID /F

    That's what I've used and tested, but you can alternatively combine both steps into one as taskkill /IM wslservice.exe /F

    The hung wsl terminal quit, and when I restarted wsl it launched successfully.

    30+ people found this answer helpful.
    0 comments
  2. Anonymous
    2024-10-03T18:07:05+00:00

    This worked for me

    4 people found this answer helpful.
    0 comments
  3. Anonymous
    2025-04-18T18:15:43+00:00

    It worked after I ran this script in PowerShell as an administrator:

    tasklist | findstr wsl
    taskkill /IM wslservice.exe /F

    $wslConfigPath = "$env:USERPROFILE.wslconfig"

    $content = @"

    [wsl2]

    networkingMode=None

    "@

    Set-Content -Path $wslConfigPath -Value $content -Encoding UTF8

    Write-Host "`n✅created .wslconfig : $wslConfigPath"

    Write-Host "📦 content:"

    Write-Host $content

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2024-11-08T10:51:14+00:00

    running the following in powershell (admin mode) did the job for me:

    taskkill /IM wsl.exe /F

    2 people found this answer helpful.
    0 comments
  5. Anonymous
    2024-02-14T10:44:50+00:00

    Hello, welcome to the Microsoft Community.

    I understand your problem and the error code is: Wsl/InstallDistro/0x80073d05" You can try:

    • Residual files and directories: Search for residual files and directories related to WSL in the system. This may include installation directories, configuration files, registry entries, etc. For example, you can search for folders related to WSL under the directory C:\Users<YourUsername>\AppData\Local\Packages.
    • Application data: Search for application data related to WSL in the system. You can use the Windows PowerShell command Get-AppxPackage *WindowsSubsystemForLinux* to find application data related to WSL, and then use the Remove-AppxPackage command to delete them. 
    
Get-AppxPackage \*WindowsSubsystemForLinux\* | Remove-AppxPackage
    • File system integrity: Search for file system corruption or errors. You can use the Windows PowerShell command sfc /scannow to check and repair file system errors. 
    
sfc /scannow

    Disclaimer: Generally, modifying registry subkeys or work group is intended for advanced users, administrators, and IT Professionals. It can help fix some problems, however, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For further protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click How to back up and restore the registry in Windows - Microsoft Support to view the article. 

    • WSL registry entries: Search for WSL-related registry entries. Be careful when handling registry entries and make sure not to delete unrelated items. You can use the Registry Editor (regedit.exe) to search for and delete these entries.
    • Reinstall WSL: After completing the above steps, you can try to uninstall and reinstall WSL. Uninstall WSL using the command wsl --unregister <DistributionName> and then rerun the installation command.

    If the problem still exists, you can set the WSL version to 1 and switch the WSL version. For specific instructions on switching your WSL version, you can open the link below and find "Set WSL version to 1 or 2."

    Basic commands for WSL | Microsoft Learn

    Hope the above information helps you.

    Leo Z|Microsoft Community Support Specialist

    Welcome to Microsoft Answers!

    2 people found this answer helpful.
    0 comments