After clicking "enable service" Rustdesk refuses to operate

[biggestsonicfan]

Bug Description

I was connected to a remote system and decided to "enable service" while connected. Rustdesk then force-minimized and began an infinite loop where every second my cursor would show "busy". Attempting to restore Rustdesk from the tray resulted in the application minimizing again. I uninstalled Rustdesk, however running the executable from releases results in Rustdesk force closing,I can not reinstall.

How to Reproduce

(Assumed)

• Install Rustdesk from the 1.2.3-1 release on a Windows 10 system, but do not enable the service.
• Connect to a remote computer.
• Click the "Enable service" hyperlink at the bottom of the application while connected.
• • I did notice that on the remote computer it suggested to set up my own server instead of the "Enable service" option

Expected Behavior

Rustdesk should close, install the service, then allow Rustdesk to be launched again.

Operating system(s) on local side and remote side

Windows 10

RustDesk Version(s) on local side and remote side

1.2.3-1 -> 1.2.3-1

Screenshots

As I can no longer get Rustdesk running on my host, I am only including a relevant entry I am finding using ProcMon

Additional Context

There doesn't appear to be a Rustdesk service running or any config files Rustdesk is reading to inform itself to force close.

[biggestsonicfan]

After a reboot, I was able to replicate the issue while recording.

2024-03-10.17-18-50.mp4

[rustdesk]

tracked by #7342

[biggestsonicfan]

How was this unreproducible? I managed to reproduce it, which is how I got footage of it.

[biggestsonicfan]

Running a fresh install using Windows 10 Media creator to create an ISO and installing in VirtualBox 7.0 I was able to reproduce the issue 100%. Please remove the "unreproducible" label.

2024-03-10.20-00-55-00.02.35.169-00.06.53.783-seg2.mp4

[devdevfork]

This bug is indeed weird and happened to me sometimes, the solution would be if that happens terminate the rustdesk service via task manager, and re-launch rustdesk.

[biggestsonicfan]

This bug is indeed weird and happened to me sometimes, the solution would be if that happens terminate the rustdesk service via task manager, and re-launch rustdesk.

Or maybe not have an option available during a remote session that will cripple the software. It can be prompted when there is no remote session.