A connection attempt failed because the connected party did not properly respond

[darkRaspberry]

Environment

Windows build number: Microsoft Windows [Version 10.0.20150.1000]
Your Distribution version: Ubuntu 20.04
Whether the issue is on WSL 2 and/or WSL 1: WSL2

Steps to reproduce

Just launch the Ubuntu in any way.
Like launch by Windows terminal or Launch by direct app(Ubuntu)

Uploading log failed due to file not supported so renaming file to .log
lxcore_user.log
lxcore_kernel.log
lxcore_service.log

Expected behavior

Launch in normal way

Actual behavior

I am attaching the screenshot
Launch by Ubuntu app.

Launch by Windows terminal

[darkRaspberry]

#4860

Duplicate
This issue is closed but still getting error.

[darkRaspberry]

Still it exist after several restart and wsl --shutdown command What to do

[therealkenc]

#4860 Duplicate

#5092 is open. Thank you for collecting logs it is always appreciated.

[benhillis]

@darkRaspberry - Your logs are empty. Did you start the logs, repro the issue, then stop?

[darkRaspberry]

Ok should i run it again?

[BiscuiTech]

I am having the same issue as above with windows version: Microsoft Windows [Version 10.0.20150.1000].

Here are my logs:
error_logs.zip

EDIT: Updated to latest Fast ring update Microsoft Windows [Version 10.0.20152.1000] and having the same error.

[PavelSosin-320]

This issue is back after the WSL Kernel update to 5.4. Some distros can start but some fail. What is common: systemd based distro can't start - they need systemd running as PID 1. They have dozens of units inside rootfs image. There is no option to start them synchronously - it will take forever. My Ubuntu 20.04 with genie worked stable a long time until the upgrade attempt. Without systemd, i.e. D-Bus, network configuration units they can't bootstrap.
In addition- I had to enlarge WSL parameters:
[wsl2]
memory = 12Gb
processors = 4
[automount]
Docker, Kubernetes, Podman can't start with small memory. After starting the distro starts eating memory to satisfy application requirements.

[darkRaspberry]

I just wiped whole windows and leaving it forever. Anyone can take the issue further as a owner of this issue GitHub don't allow me to transfer it. I no longer use this platform so the repo owner can close this issue.

[therealkenc]

Alight there is #5092 open (whether related or otherwise) or folks are encouraged to open a new issue with WSL logs.