Share via

systemd service down in WSL2 Ubuntu distro after ubuntu default user added

Mondhe, Pranav 0 Reputation points
2025-09-30T09:43:30.0266667+00:00

based on my journalctl.logs  --> The main issue is the failure of wsl-pro-service to connect to the Windows Agent, which blocks systemd startup. Restarting WSL, updating WSL and Windows, and ensuring no security software is interfering should resolve the problem. If it persists, check for WSL bugs or reinstall WSL.

 

Key points from your logs:

  • wsl-pro-service is trying to connect to the Windows Agent but cannot get the address or read the agent port file.
  • Systemd status is stuck at "Connecting" and then "Not connected: waiting to retry".
  • Multiple warnings: /etc/resolv.conf updating disabled in /etc/wsl.conf.

What this means:

  • WSL systemd integration relies on communication between the Linux environment and the Windows host via the WSL agent.
  • If the WSL agent (on Windows) is not running, misconfigured, or blocked (by firewall, antivirus, or permissions), systemd cannot fully start.
  • The /etc/resolv.conf warning is informational and not a blocker, but it shows that WSL is respecting your config to not auto-update DNS.

 

Windows for business | Windows 365 Enterprise
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Quinnie Quoc 11,055 Reputation points Independent Advisor
    2025-09-30T10:34:49.0033333+00:00

    Hi,

    From what you've described, the core issue seems to be that the wsl-pro-service is unable to connect to the Windows Agent, which is preventing systemd from starting properly. This typically happens when the agent can’t access the port file or retrieve the address, often due to firewall rules, antivirus interference, or a misconfigured WSL environment.

    Restarting WSL, updating both Windows and WSL, and temporarily disabling any security software are good first steps. If the issue continues, it may be worth checking for known WSL bugs or considering a clean reinstall of WSL to reset the integration. The /etc/resolv.conf warning you’re seeing is expected behavior based on your configuration and shouldn’t impact systemd startup.

    Let me know if you'd like help walking through any of these steps or reviewing your setup further.

    If my answer is useful for you, please vote for it.

    Best regards,

    Quinnie Quoc.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.