Issue:
I'm currently developing a simple project that uses version 1.0.0-beta.6 of the library. It's installed correctly and can act properly on the available scenarios (listeners). The actual problem for me is that the "status" of the process is not synced with the services.msc program, regardless of reboots/list refresh, and also, it's not seen on the net start command as well.
The project does not have any GUI, it's just a simple ExpressJS server that spawns a couple of Powershell scripts that escalate privileges for some management stuff, nothing serious there.
Maybe this is dumb stuff, but it can be helpful for avoiding duplicate execution, which is not expected at all.
How To Reproduce:
Not applicable.
Expected Behavior:
I assume that if the svc.start() executes fine, the status of the process on the services.msc should display the stop/restart status control over the start process, and of course, the started process should be visible on the net start command execution
Issue: I'm currently developing a simple project that uses version
1.0.0-beta.6of the library. It's installed correctly and can act properly on the available scenarios (listeners). The actual problem for me is that the "status" of the process is not synced with theservices.mscprogram, regardless of reboots/list refresh, and also, it's not seen on thenet startcommand as well.The project does not have any GUI, it's just a simple ExpressJS server that spawns a couple of Powershell scripts that escalate privileges for some management stuff, nothing serious there.
Maybe this is dumb stuff, but it can be helpful for avoiding duplicate execution, which is not expected at all.
How To Reproduce: Not applicable.
Expected Behavior: I assume that if the
svc.start()executes fine, the status of the process on theservices.mscshould display thestop/restartstatus control over thestartprocess, and of course, the started process should be visible on thenet startcommand executionScreenshots:
OS Windows 10 - 64 bits based OS