Osu!lazer not starting

[yt6983138]

Type

Crash to desktop

Bug description

installer

if i run the installer, the icon shows and the progress bar progresses, then the window just died

game

if i launch the game i can see the process just open up for a moment then died in task manager, no log are produced (%appdata%/osu folder not created also), in event viewer (pic attached below) shows that it encounters a connection issue, i have tested a bit more:

1. osu stable: working
2. user debug version: working
3. user release version: just dies
4. release from website: dies again
   now i have no idea why this happens

oh btw, i wonder is installer project included there? i dont see it

Screenshots or videos

(no log found in %appdata%/osu)

Version

2024.312.0

Logs

(no log found at %appdata%/osu, folder not exist)
Report.zip

[cdwcgt]

can you check port 44823 is bind to other process?
and you can try to launch tournament, use osu.exe --tournament

[yt6983138]

44823 is not binded by tcp nor udp
yes i can launch in tournament normally, any idea?

[cdwcgt]

lazer won't start when 44823(the IPC port) was binded. that is, multiple simultaneous starts are not allowed.
and your lazer may tried to pass some IPC message which cause connected refused.

Sorry for replying now, I did not receive the message notification

[yt6983138]

huh about 2 weeks later (now) it just started working again...? 🤔

[Rekunan]

Does the event viewer and everything look fine?

[cdwcgt]

maybe just the port was released?

[pytheor]

Hi, I came across this same problem that the game will crash on startup because it fails to bind on 44823. In my case the port was unused (checked through TCPView) and even restart didn't help. According to this post https://stackoverflow.com/questions/48478869/cannot-bind-to-some-ports-due-to-permission-denied it's caused by Hyper-V/WSL. Restarting winnat service fixed it.
This probably only affects a small portion of users but it might be worth considering retrying different ports of one fails.

[yt6983138]

btw sometimes you need to preserve the ports yourself to prevent them being binded by other service again

i found the reason after months later doing asp.net project (unable to bind port but not used), apparently asp.net has more developers than osu so i found the solution pretty quickly