Upgraded messa's for WSL, "Failed to start the systemd user session" reappeared.

[Chikimonki]

Windows Version

Windows 11 Version 25H2 (OS Build 26200.8039)

WSL Version

Distributor ID: Ubuntu Description: Ubuntu 24.04.4 LTS Release: 24.04 Codename: noble WSL version: 2.6.3.0 Kernel version: 6.6.87.2-1 WSLg version: 1.0.71 MSRDC version: 1.2.6353 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.26100.1-240331-1435.ge-release Windows version: 10.0.26200.8039

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

6.6.87.2-1

Distro Version

No LSB modules are available.

Other Software

Docker version 29.3.0, build 5927d80, I'm not sure it relates to Docker, but I did install nvidia drivers, then removed them and cleaned up, as I found I have different GPUs.

Bug-Report-for-Failed-message.pdf

Repro Steps

When I start WSL I get a Failed message, after waiting for nearly half a minute, then it builds. Normally, as ofr yesterday, it would be up and runn instantly, but now there's a lag. I think I've fixed it locally, but wanted to report so you're aware of what I'd experienced.

Expected Behavior

Didn't screen shot it, but here's the message: Failed to start the systemd user session.
I'd tested it after a reboot and it worked fine again.

Actual Behavior

Then, after putting the machine to Sleep, when starting WSL again, I found: Failed to start the systemd user session. So, I've cleaned it, as explained in the PDF attached.

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-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'.

[Chikimonki]

'/question'.

[github-actions]

Diagnostic information

Found '/question', adding tag 'question'