On Sat, 27 May 2017 01:42:40 +0000 (UTC),
Roy Tremblay actually wrote:

Permission problem with openvpn moving from WinXP to Win10 causing route
changes to fail.

Thanks to the suggestion from Good Guy, I solved the problem of *.ovpn
OpenVPN text files not having the permissions to run the necessary route
commands to get onto VPN.

After I installed the Win7/8/Vista/10 64-bit OpenVPN package on Windows 10,
I changed the file associations for doubleclicking on *.ovpn text files to
open up in the "OpenVPN Daemon" instead of the "OpenVPN GUI".
https://s14.postimg.org/y3vs59vnl/Clipboard03.gif

I did that same file association change many years ago, on Windows XP:
https://s29.postimg.org/estakppgn/openvpn.gif

This allows me to just doubleclick on any of hundreds of *.ovpn openvpn text
files, and they open up in the OpenVPN Daemon, which just looks like a
command windows with a text running log file (which is what I pasted
separately).

When I close the command window with the running log file, that knocks me
off of VPN. So, there is no OpenVPN GUI involved. And there is no link
involved.

I doubleclick on an *.ovpn text file to get on VPN.
I close that running log file to get off of VPN.

On Windows 10, I made the same file association change:
https://s14.postimg.org/y3vs59vnl/Clipboard03.gif

But after clicking on an *.ovpn OpenVPN text file, the running log showed
that it needed more permissions for some very strange reason (unknown to me
at this point).

Predictably, setting the "OpenVPN GUI" link to run as administrator did
nothing:
https://s1.postimg.org/oppwqvrzz/Clipboard01.gif

But that's probably because I am not using the OpenVPN GUI (and even more to
the point, I'm not using any links to start the program). I'm using file
associations to start the OpenVPN Daemon instead of using the OpenVPN GUI.

So, based on Good Guy's suggestion, I went to the OpenVPN bin directory and
arbitrarily set *all* the exe files to run as administrator:
https://s9.postimg.org/w1wwgzlrj/Clipboard02.gif

That solved the problem of permissions!

Now when I doubleclick in Windows 10 on any *.ovpn OpenVPN text file, the
OpenVPN Daemon pops up the running log file, which shows that there are no
longer permission errors when the route commands are run.

I have no idea why this extra step is required, nor why it's not documented
in any of the OpenVPN setup tutorials for Windows 10.

All I know is that setting all the executables to run as administrator
solved whatever problem Windows 10 has introduced that Windows XP didn't
have.