WSL check failed: Failed to read property 'DistributionName' from distribution {730a5265-2b8f-4784-8cc5-cff2effaf8e1} Error code: Wsl/EnumerateDistros/Service/ReadDistroConfig/E_UNEXPECTED. Try running 'wsl --status' in PowerShell to diagnose. Retry Check Learn Mo

[hamsammich35-droid]

WSL check failed: Failed to read property 'DistributionName' from distribution {730a5265-2b8f-4784-8cc5-cff2effaf8e1}
Error code: Wsl/EnumerateDistros/Service/ReadDistroConfig/E_UNEXPECTED. Try running 'wsl --status' in PowerShell to diagnose.

Retry Check
Learn More

how can i fix this issue

[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-wsl-logs.ps1 -LogProfile networking instead, following the instructions in Collect WSL logs for networking issues

Once completed please upload the output files to this GitHub issue.

See Collect WSL logs (recommended method).

If you choose to email these logs instead of attaching them to the bug, please send them to wsl-gh-logs@microsoft.com with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.

[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-wsl-logs.ps1 -LogProfile networking instead, following the instructions in Collect WSL logs for networking issues

Once completed please upload the output files to this GitHub issue.

See Collect WSL logs (recommended method).

If you choose to email these logs instead of attaching them to the bug, please send them to wsl-gh-logs@microsoft.com with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.

[OriWiisp]

What exactly were you trying to do when you got this error

[chemwolf6922]

Hi @hamsammich35-droid , could you please run these commands in terminal (powershell) to check if the registry entries are complete?

reg query "HKCU\Software\Microsoft\Windows\CurrentVersion\Lxss"
reg query "HKCU\Software\Microsoft\Windows\CurrentVersion\Lxss\{730a5265-2b8f-4784-8cc5-cff2effaf8e1}" /s

A complete registry should look something like this:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Lxss\{<uuid>}
    State    REG_DWORD    0x1
    DistributionName    REG_SZ    Ubuntu
    Version    REG_DWORD    0x2
    BasePath    REG_SZ    C:\Users\<user name>\AppData\Local\Packages\CanonicalGroupLimited.Ubuntu_79rhkp1fndgsc\LocalState
    Flags    REG_DWORD    0xf
    DefaultUid    REG_DWORD    0x3e8
    PackageFamilyName    REG_SZ    CanonicalGroupLimited.Ubuntu_79rhkp1fndgsc
    Flavor    REG_SZ    ubuntu
    OsVersion    REG_SZ    22.04

If it's just the DistributionName missing, you can try recover it by manually setting a value. DO back up before doing this. If the registry is corrupted beyond repair, you should consider backup the entry and delete it.