Open nopeless opened 11 months ago
Thanks for reporting this. Your use case makes sense.
We have actually had issues in the past where other "security software" prevents our daemon from automatically starting on boot. This type of fix would solve that issue as well.
I have spoken to our GUI developer and it would probably make sense to try out just executing the command sc.exe start mullvadvpn
on GUI process startup iff it fails to connect to the management named pipe.
I have created an internal issue to track this feature request, we will investigate. https://linear.app/mullvad/issue/DES-490/try-to-start-system-service-on-gui-start-if-its-not-running
Thank you. I can't access that link, but I would like to hear updates about it. Keep me posted if possible 👍
Sorry, I did not state that clear enough. The internal issue tracker is not publicly available. I posted the link mostly for my colleagues to have a connection from this issue into linear.
@faern I am still interested in this issue, and its been over a month. What is the status on this?
@nopeless Hi, no updates yet, it's in our backlog and will hopefully be implemented fairly soon.
Software and Platform
Operating system: Win 11
App version: 2023.5
Motivation
I have most Windows services running on demand (manual), so that when I boot up the machine, only required processes are running. This includes the Mullvad vpn service. However, when launching the gui app, it doesn't attempt to start the service. It would be nice to automatically start it.
Details
When starting the application, the according Windows service (Mullvad VPN service) should be started if it is not running.
I am willing to contribute to the codebase