can't run as windows service (already admin role)
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 5.1k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug**
can't run as windows service (already admin role), told us :can't connect to host
**To Reproduce**
Steps to reproduce the behavior:
use the lastest code sorce (2022-6-18) complie a win desktop then get admin role then run as service
**Remotely Version**
Server (can be found on about page): use the lastest code sorce (2022-6-18) complied
Agent (can be found in device card):use the lastest code sorce (2022-6-18) complied
**Expected Behavior**
can run as service on windows
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Desktop (please complete the following information):**
- OS: [e.g. iOS] Microsoft Windows [ 10.0.19044.1766]
- Browser [e.g. chrome, safari] chrome 99
- Version [e.g. 22]
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Windows service failure using the latest source on Windows 10, with the desktop build running under an administrator account. Inspect the service startup and host-connection path based on the reported “can't connect to host” result. Done means the compiled application runs as a Windows service and connects successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100