Accessing \\wsl.localhost results in logon failures being logged while \\wsl$ does not

[kitu-sbruce]

Windows Version

Microsoft Windows [Version 10.0.22631.4037]

WSL Version

2.2.4.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

Linux version 5.15.153.1-microsoft-standard-WSL2 (root@941d701f84f1) (gcc (GCC) 11.2.0, GNU ld (GNU Binutils) 2.37) #1 SMP Fri Mar 29 23:14:13 UTC 2024

Distro Version

Ubuntu 22.04

Other Software

No response

Repro Steps

See #11198

Expected Behavior

See #11198

The workaround mentioned in the ticket above no longer works.

Actual Behavior

See #11198

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:

• Can't access a WSL share with account/password in a win32 app when \wsl.localhost\Ubuntu\ is not mounted as a drive (#9267), similarity score: 0.73
• WSL share is not accessible (#9529), similarity score: 0.73
• Windows 11 22H2 WSL error - Windows cannot access \wsl.localhost (#8983), similarity score: 0.73
• \wsl.localhost\ not accessible from sshd on windows (#11120), similarity score: 0.73
• \wsl$ not functioning (#6967), similarity score: 0.72

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

[kitu-sbruce]

/emailed-logs

[github-actions]

Diagnostic information

Found '/emailed-logs', adding tag 'emailed-logs'

[OneBlue]

@kitu-sbruce: How exactly are you accessing that path ? Do you see the same error in explorer and cmd.exe ? Also could you capture logs for both ?

/logs

[kitu-sbruce]

Good question.

I primarily run into this issue when running something like:

alias explorer=/mnt/c/Windows/explorer.exe
explorer .

This opens up the current path in explorer which WSL resolves to \\wsl.localhost\...

I later found I could just go to Start->Run and browse to \\wsl.localhost\... and get the same behavior while \\wsl$\... does not.

No UI error is displayed and everything actually works for either case but the former(\\wsl.localhost\...) results in logon failures being reported in the Windows security log which ultimately turns into a user lockout.

Will submit logs in a few.

[kitu-sbruce]

/emailed-logs

[kitu-sbruce]

WslLogs-2024-09-12_16-05-00.zip - opening `explorer .` from WSL
WslLogs-2024-09-12_16-07-36.zip - Start->Run-> \\wsl.localhost\...
WslLogs-2024-09-12_16-08-35.zip - Start->Run-> \\wsl$\...

[github-actions]

Diagnostic information

Found '/emailed-logs', adding tag 'emailed-logs'

[OneBlue]

Thank you @kitu-sbruce. Do you have any AV / Firewall installed ? I wonder if they intercept one path and not the other.

[kitu-sbruce]

Thank you @kitu-sbruce. Do you have any AV / Firewall installed ? I wonder if they intercept one path and not the other.

Just Defender.

I mentioned this earlier but think the key to replicating is using RDP to connect to the machine with WSL. I'll also mention that my machine is not on a domain and is using local accounts.