wsl-pro-service : WARNING Daemon: could not connect to Windows Agent: could not get address

[mazouab]

Windows Version

Microsoft Windows [version 10.0.19045.5854]

WSL Version

2.4.13.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.167.4-1

Distro Version

Ubuntu 24.04

Other Software

Hello,

I'm having this issue with my WSL, that causes it to crash.

There was a precedent issue, that has no response : #12433.

I have these logs in syslog, from the WSL :

2025-05-28T10:46:54.350178+02:00 MY-LAPTOP wsl-pro-service[9072]: INFO Reconnecting to Windows host in 60 seconds
2025-05-28T10:46:54.350220+02:00 MY-LAPTOP wsl-pro-service[9072]: DEBUG Updated systemd status to "Not connected: waiting to retry"
2025-05-28T10:47:54.410258+02:00 MY-LAPTOP wsl-pro-service[9072]: INFO Daemon: connecting to Windows Agent
2025-05-28T10:47:54.410457+02:00 MY-LAPTOP wsl-pro-service[9072]: DEBUG Updated systemd status to "Connecting"
2025-05-28T10:47:54.411007+02:00 MY-LAPTOP wsl-pro-service[9072]: WARNING Daemon: could not connect to Windows Agent: could not get address: could not read agent port file "/mnt/c/Users/MY-USER/.ubuntupro/.address": open /mnt/c/Users/MY-USER/.ubuntupro/.address: no such file or directory
2025-05-28T10:47:54.411043+02:00 MY-LAPTOP wsl-pro-service[9072]: INFO Reconnecting to Windows host in 60 seconds
2025-05-28T10:47:54.411058+02:00 MY-LAPTOP wsl-pro-service[9072]: DEBUG Updated systemd status to "Not connected: waiting to retry"

Repro Steps

less /var/log/syslog

Expected Behavior

No crash, and no error logs.

Actual Behavior

WSL crashes, and logs.

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 wsl-gh-logs@microsoft.com 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'.

[sirredbeard]

This appears to be an issue with the wsl-pro-service malfunctioning, I would recommend filing a bug there for that team to address.

In the interim you can uninstall the Ubuntu Pro client with sudo apt remove ubuntu-pro-client.

[mazouab]

Hello,

I'll try to remove the app. I don't think I really need it to get my WSL work.

Thanks.

[sirredbeard]

Let us know how it goes. No, it is not necessary for Ubuntu to work on WSL. If issues continue, I recommend opening an issue on wsl-pro-service.

[mk-pmb]

I encountered the same problem on noble, and the recommendation above

In the interim you can uninstall the Ubuntu Pro client with sudo apt remove ubuntu-pro-client.

won't work there, because it would uninstall package ubuntu-minimal and thus sudo, except sudo refuses to uninstall if you don't have su. To recover from the situation, you can restore the old state with: wsl.exe --user root apt install ubuntu-minimal update-manager-core wsl-pro-service

Instead, for me, for now, it seems that disabling the service in systemd was sufficient: sudo systemctl disable wsl-pro.service && sudo systemctl stop wsl-pro.service