Ok...
This sample is from another client config that I have (and have used for quite some time now) and have used it across Windows 8, 8.1, and Windows 10.
When connecting from Windows 8 & 8.1, I am able to connect and route my web traffic to the server.
When connecting from Windows 10, I get the error message at the end of the post.
OpenVPN 2.4.2 x86_64-w64-mingw32
dev tun
tls-client
remote x xxxx
redirect-gateway def1
dhcp-option DNS x.x.x.x
pull
route-method exe
route-delay 2
Skipped adding in security cipher, auth etc.
Also important to note that in reference to
this post on serverfault, I tried to add the route-method exe and a delay to see if that would allow the modification of my Route.exe file. Unfortunately, I still receive the same type of error although it is a little cleaner.
Sun May 14 18:40:18 2017 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Sun May 14 18:40:20 2017 env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Sun May 14 18:40:21 2017 ERROR: Windows route add command failed: returned error code 1
Sun May 14 18:40:21 2017 env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Sun May 14 18:40:21 2017 ERROR: Windows route add command failed: returned error code 1
Sun May 14 18:40:21 2017 env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Sun May 14 18:40:21 2017 ERROR: Windows route add command failed: returned error code 1
Sun May 14 18:40:21 2017 env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Sun May 14 18:40:21 2017 ERROR: Windows route add command failed: returned error code 1
Sun May 14 18:40:21 2017 env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Sun May 14 18:40:21 2017 ERROR: Windows route add command failed: returned error code 1
Sun May 14 18:40:21 2017 env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Sun May 14 18:40:21 2017 ERROR: Windows route add command failed: returned error code 1
Sun May 14 18:40:21 2017 Initialization Sequence Completed
No matter how I start OpenVPN on the Win 10 system, I get the same routing error.
Ok, as I was typing this I believe I came across somewhat of an answer:
I somehow managed to come across
OpenVPN Ticket #68.
In reading comment #11, zerok0ol was able to connect when running ovpn from an elevated command prompt. When I did the same, I got the following output:
Sun May 14 18:47:49 2017 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Sun May 14 18:47:51 2017 env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Sun May 14 18:47:51 2017 env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Sun May 14 18:47:51 2017 env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Sun May 14 18:47:51 2017 env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Sun May 14 18:47:51 2017 env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Sun May 14 18:47:51 2017 env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Sun May 14 18:47:51 2017 Initialization Sequence Completed
So it looks like it works, but I am trying to install for a user who would not see using an elevated command prompt/running a batch script as a solution. Also, it doesn't connect with the GUI and inform the user with a message box that the connection has been established/severed etc.
Maybe the above issue needs to be reopened.