Collect networking logs does not work because WSL distros does not exist (admin is a different user account)

[borjamunozf]

Windows Version

whatever

WSL Version

whatever

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

1. Company laptops have two accounts in machine:

• Normal user account.
• Admin user account

2. Distros listed and working under normal user account.
3. As distros are not detected nor installed under admin user account, the collect networking fails

.\collect-networking-logs.ps1

Directory: C:\Users\WHATEVER
                                                                                                                        Mode                 LastWriteTime         Length Name                                                                  ----                 -------------         ------ ----                                                                  d-----         8/26/2024   6:43 PM                WslNetworkingLogs-2024-08-26_18-43-01                                 wsl_networking.wprp not found in the current directory. Downloading it from GitHub.                                     networking.sh not found in the current directory. Downloading it from GitHub.

Initializing data collection -- please wait.
Initialization complete. Reproduce the scenario, then run 'capture stop'.

Log collection is running. Please reproduce the problem and press any key to save the logs.
Saving logs...
Windows Subsystem for Linux has no installed distributions.

Use 'wsl.exe --list --online' to list available distributions
and 'wsl.exe --install <Distro>' to install.

Distributions can also be installed by visiting the Microsoft Store:
https://aka.ms/wslstore
Error code: Wsl/Service/CreateInstance/GetDefaultDistro/WSL_E_DEFAULT_DISTRO_NOT_FOUND
Data collection successful; output = WslNetworkingLogs-2024-08-26_18-43-01/wfpdiag.cab

Expected Behavior

Collect-networking-logs works.

Actual Behavior

Collect-networking-logs fails because distros are not detected under admin account, given that wsl installs distribution per user.

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 [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!

Closed similar issues:

• The Windows admin user cannot see the WSL installed on a normal user. (#10863), similarity score: 0.74
• Admin user does not see a Ubuntu installation (#8890), similarity score: 0.70

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

[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!