Hi, If you are referring to running at boot using the so-called automatic service, the service runs as local system and spawns openvpn.exe with elevated privileges. If using the GUI, the "right" way is to run the GUI without elevation, let the interactive service start openvpn.exe as user (not elevated) with the service handling tasks requiring elevation. That is the default and should just work out of the box since version 2.4.
If you want to run openvpn.exe from the command line, use an elevated prompt. Setting run-as-administrator on the executable would be a mistake. It's a pity that there is so much out-dated info about OpenVPN on Windows out there. Selva On Tue, Jun 28, 2022 at 12:31 AM Jordan Hayes <jmha...@j-o-r-d-a-n.com> wrote: > The other thing that's always driven me crazy is that the client needs > to have the "run as administrator" bit set, and it doesn't happen by > default. > > /jordan > > > > _______________________________________________ > Openvpn-users mailing list > Openvpn-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openvpn-users >
_______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
