arm64 version openvpnserv2.exe running as x64 mode

[shadowmite]

I have a Surface Laptop 7 and while trying to get rid of any non-arm64 native apps I've noticed even OpenVPN 2.6.17 here installed from the arm64 installer is actually running in x64 emulated mode. Did something change recently or has this still never worked right?

[cron2]

Not really a "GUI" issue, transferring to openvpn main repo (maybe it's a packaging issue, in which case it would belong to openvpn-build...).

@lstipakov any ideas? How do I see what architecture a given .exe has?

[lstipakov]

Nothing has been changed especially in 2.6 (in 2.7 we refactored the service but we still target the same configuration). We build for "Any CPU" and ship the single binary which should work on all supported platforms. Do you experience any issues with the emulation? Note that the service itself doesn't do much - it enumerates openvpn configs in the global config directory and communicates to (another) openvpn privileged service to start tunnel(s), and then monitors openvpn processes and restarts them in an unlikely case they crash.

[flichtenheld]

Yeah, we always installed the same binary for all architectures. So no bug in openvpn-build, working as intended. I guess this issue will be resolved once we get rid of openvpnserv2 completely as is planned...

[shadowmite]

Not really a "GUI" issue, transferring to openvpn main repo (maybe it's a packaging issue, in which case it would belong to openvpn-build...).

@lstipakov any ideas? How do I see what architecture a given .exe has?

To see the running architecture find it in task manager, right click and "Go to Details". From that view you can also sort by architecture and get the full list of anything not arm64 native which is how I found it.

It's not really causing any issues, but it's causing the emulation framework to load which defeats the purpose of using native arm64 to increase efficiency.

[cron2]

This part of the OpenVPN package is fully optional, and only needed if you want configs (from ...\config-auto\) to be automatically started by the service, not via GUI. So if "do not load framework" is a concern here, you could disable the "OpenVPN Service" for the time being.

Do not disable "OpenVPN Interactive Service" - that is a different binary, and arm64.

But we take note as another motivational aspect for @d12fk to get rid of openvpnserv2 ;-)