Cannot start rustdesk as service (not ServiceProfiles Folder broken, always failed to create IPC service)

[lugt]

Bug Description

When I install rustdesk as service, the mouse will blink , process exit and start, show the wait ring and hide, then show and hide again.
I have to uninstall the software .(remote side)
uninstalling and reinstalling does not restore the situation.

the client program when started still attempts to connect to the pipe to contact the Service, which is not removed somehow during uninstallation process.

PS. only occur when tried to install as a Service, and somehow that installation failed.

How to Reproduce

Install as Service.

Expected Behavior

Capable of proper uninstallation at least, does everything to restore the environment after installation.
Capable of installation as a Service.

Operating system(s) on local side and remote side

both Windows 10 version 22H2, 19045.3570 -> Windows 10

RustDesk Version(s) on local side and remote side

1.2.3 -> 1.2.3

Screenshots

Closed in a split of a second

Additional Context

[2023-12-08 11:27:42.718369 +08:00] INFO [src\core_main.rs:162] main start args:[]
[2023-12-08 11:27:42.838742 +08:00] DEBUG [libs\hbb_common\src\config.rs:475] Configuration path: C:\Users\lugt\AppData\Roaming\RustDesk\config\RustDesk_local.toml
[2023-12-08 11:27:42.856373 +08:00] DEBUG [libs\hbb_common\src\config.rs:475] Configuration path: C:\Users\lugt\AppData\Roaming\RustDesk\config\RustDesk.toml
[2023-12-08 11:27:42.866656 +08:00] DEBUG [libs\hbb_common\src\config.rs:475] Configuration path: C:\Users\lugt\AppData\Roaming\RustDesk\config\RustDesk_default.toml
[2023-12-08 11:27:42.870761 +08:00] DEBUG [libs\hbb_common\src\config.rs:475] Configuration path: C:\Users\lugt\AppData\Roaming\RustDesk\config\RustDesk2.toml
[2023-12-08 11:27:43.725921 +08:00] INFO [src\server.rs:409] server not started (will try to start): deadline has elapsed
[2023-12-08 11:27:43.727231 +08:00] ERROR [src\ipc.rs:293] Failed to start ipc server at path \\.\pipe\RustDesk\query: access denied. (os error 5)
[2023-12-08 11:27:43.727570 +08:00] ERROR [src\server.rs:374] Failed to start ipc: access denied. (os error 5)

[rustdesk]

It seems your system has special security settings. Can not create IPC on your system.

Answer from ChatGPT.

Failed to create IPC on Windows, why?

There are several reasons why you might be failing to create an IPC on Windows:

1. IPC Service is not running:

• The IPC service is responsible for enabling IPC communication in Windows. If it's not running, you won't be able to create an IPC.

Solution:

1. Open the "Services" window.
2. Locate "Remote Procedure Call (RPC)".
3. Right-click on "Remote Procedure Call (RPC)" and select "Start".

2. Insufficient IPC Permissions:

• Creating an IPC requires specific permissions. If you don't have the necessary access, you won't be able to proceed.

Solution:

1. Open the "Local Security Policy" window.
2. Expand "Local Policies""Security Options".
3. Locate "Allow local users to remotely connect using NTLM authentication (RPC)".
4. Ensure this policy is set to "Enabled".

3. Lack of System Resources:

• Creating an IPC consumes resources like memory and disk space. If your system is lacking, it might not be able to handle the request.

Solution:

1. Open the "Task Manager".
2. Switch to the "Performance" tab.
3. Check the "Memory" and "Disk" usage.

4. Third-party IPC Software Issues:

• If you're using a third-party IPC software, there might be internal issues causing the problem. Contact the software developer for assistance.

5. General System Issues:

• Sometimes, temporary problems or glitches can hinder IPC creation.

Solutions:

• Restart your computer.
• Create a new user account and try again.
• Utilize Windows' built-in IPC tools.

Additional Tips:

• If you're still facing issues after trying the above solutions, consider consulting Windows technical support.
• Double-check the specific error message you're receiving, as it might provide further clues about the cause of the problem.
• If you're working with a specific software or program requiring IPC, consult its documentation or support channels for specific troubleshooting steps.

Remember, troubleshooting IPC issues can involve multiple factors. By systematically checking for the most common causes and applying the appropriate solutions, you should be able to resolve the problem and successfully create an IPC on your Windows system.

[lugt]

Thanks for the attention given, and to your hard work in making rustdesk more reliable than ever. 👍

[fufesou]

@deep-soft

I can hardly reproduce the crash.

Can you build the debug exe on your PC?
If you can please try the master commit?

1. Build the flutter version.
2. Copy the target\debug\librustdesk.pdb to flutter\build\windows\runner\Debug.
3. Optional. Replace the files in flutter\build\windows\runner\Debug with the files in C:\Program Files\RustDesk if you have installed RustDesk. Then restart the service.
4. Run the exe, reproduce the crash.
5. Package the rustdesk.dmp in %LocalAppData%\CrashDumps and all files in flutter\build\windows\runner\Debug.
6. Upload to somewhere.

I'll find the crash stack.

You can also skip step 1 and 2, and try my prebuilt package Debug.zip in https://github.com/fufesou/rustdesk/releases/tag/tmp .

If you use my prebuilt package. You can only upload the rustdesk.dmp in %LocalAppData%\CrashDumps.

[rustdesk]

Please reproduce it with out your code change.

[fufesou]

On that work PC I can't run the nightly build or the prebuilt package above.

Why? What error does it report? Or can you check the Windows event viewer?

OK, i'll try to build the debug version on github CI.

github CI will build a release version, which does not contain debug symbols.
Make sure you have do some changes to build the debug version.

[rustdesk]

@deep-soft stop doing such thing next time (abuse our resource on your build), otherwise, I will block you.

[lugt]

My guess is that there is a problem in the installation process of Service Mode, apart from the one pointed by deep-soft. maybe someone else could post an issue later on.

[ethanriverpage]

Hey, having this same issue here. On my work laptop, so I assume it has something to do with GPO's defining security policies. @lugt , is this machine hooked up to a AD/AAD instance? Work/school laptop, etc.

[lugt]

This is my personal laptop, no AD that I am aware of, though I had a Office 365 account logged in(belonging to workplace), should that be of concern?

[scruel]

@rustdesk Same issue here, rustdesk just won't be useable because of this... I have to reboot the whole system every time for using it, and don't know what caused this.
Confirmed RpcSs service started, tried to run rustdesk with admin privileges, close the windows firewall, disable defender and related protections, nothing helped...

[scruel]

@rustdesk Tried the latest version and the issue is now gone in this version.

[rustdesk]

Thank you so much. Let me know if you have the issue again.

[thib3113]

Same issue here . I got a problem about keys on the server (bad docker volume) . When I debug my key problem, I reboot rustdesk app ... and it crash loop with the error Failed to start ipc server at path \\.\pipe\RustDesk\query . ( v1.2.4 ) .

Reusing the correct keys on the server resolve the problem on my side

[rustdesk]

Can you still reproduce this issue constantly? Even with latest nightly https://github.com/rustdesk/rustdesk/releases/tag/nightly, I upgraded tokio (which fixed an ipc issue) yesterday, could you try?

[thib3113]

Ok, so I've done more tests with 1.2.4 version (not nightly) .

First, moving key from server (so, the keys will be regenerated) .

starting/killing the app => seems to doesn't reproduce

checking the rustdesk app, it say "ready", but can't connect because keys missmatch ( normal ) .

I checked the windows services, and I found rustdesk service is off (strange that the app doesn't tell to start it ?) .
So, I try to start it manually ... and it crash loop, and starting the rustdesk app will close it some seconds after .
C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\RustDesk\log\server

---

So, I uninstall rustdesk, and try to start the install, but crash each times ... checking the task manager, it seems that a process of rustdesk is running

I kill the process, and restart the exe . It asks UAC ( not on the previous test ), and don't crash

---

So, installing the nightly :

• the app say it's ready (but can't connect because keys missmatch ( normal )) => no crash
• try to reboot the app => no crash
• sometimes ask to start the service => service seems started, and doesn't crash loop
  

It seems fixed on nightly, I will update if I found errors later

--
( I restored the keys, and no errors )

[rustdesk]

Thank you so much.

[pfranzke]

I got a similar issue. I can't run the .exe as a user, but as an admin. The user has privileges to run all .exe programs. When I try to start Rustdesk, the loading symbol comes for a second and then nothing happens. I don't see any running process in Task Manager. I want to share Rustdesk as a portable app for my colleagues.

[21pages]

Yes, "does not end the script" is expected, because I want to reproduce the failed ipc like the first time.

[pfranzke]

I just recognized, when I am running the script already and try to run it in another cmd, the task will fail.

[21pages]

Yes, only one application is allowed to occupy the specified ipc.

[21pages]

On your computer, is there any situation which can reproduce ipc failure with a high probability?

[pfranzke]

Not as far as I know.

[nate235]

Apologies for the "duplicate" I checked the issues section for this bug, not here...

[rustdesk]

No problem. Please try out #6640 (reply in thread)
It worked for @thib3113 and @scruel