RustDeskServer.exe forces nssm service names to be `hbbr` and `hbbs`. Setup instructions in Docs conflict with server hard-coded names.

Your setup instructions are broken.

The nssm install step results in a service that cannot be inspected by the RustDeskServer.exe wrapper UI. The wrapper is hard-coded to look for services named hbbs and hbbr, but your website instructs users to create services with nssm named "RustDesk hbbr service" and "RustDesk hbbs service"

https://rustdesk.com/docs/en/self-host/rustdesk-server-oss/windows/

The RustDeskServer.exe wrapper will keep changing its title between "RustDesk Server" and "RustDesk Server Stopped" over and over, when those services are manually set up with those names. In order to get it to stop doing that, the user has to name the services hbbr and hbbs verbatim.

I figured this out when I decided to just click Start in the "RustDesk Server" UI. This resulted in the wrapper registering its own copies of the services with the unfortunate names of hbbr and hbbs. <---------- I do not like these names, because they do not show up in the Windows Services page when I type "Rust" to find them.

You (the developer) need to rename your services in the app to be more descriptive than simply hbbr and hbbs. No customer of yours is going to remember the services were called hbbr and hbbs when they go looking in the Windows Service manager to find out if their service is running.

Start with the Windows setup page at rustdesk.com/docs/en/self-host/rustdesk-server-oss/windows/ and the RustDeskServer.exe wrapper behavior described in the issue. Trace how the wrapper names and discovers the hbbs and hbbr services, then align the setup instructions and service names so the services are discoverable in Windows Services and correctly recognized by the wrapper.