OpenVPN Support Forum

Iv'e been at this for quite some time now, and I have finally gotten the client/server to the point where I can connect and have local access. It appears the same issue is plaguing the client and server. I have already tried running as administrator, and completely shutting down any/all services related to OpenVPN and then running as administrator only, however I still receive the following errors:

Note: The server error also shows up in the client log, just before the do_ifconfig.

Any ideas on how to proceed is greatly appreciated.

If you use openvpn-2.4 you do not need to run as admin ..

My apologies if I was not clear enough in my initial post, however I have tried running without administrative privileges and with, neither of which solves the routing issue.

My question really boils down to: How can I add these routes at run-time of the client connection?

I could manually add these routes into the client pc, however I feel that this may cause more issues than it solves as this would be a permanent change.

My apologies if I was not clear enough in my initial answer.

Here is a more clear one

Please see:
HOWTO: Request Help !

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.
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.
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:
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.

I spoke too soon. I disconnected from my elevated command prompt and attempted to use the GUI. My new error is that route.exe was unable to add the routes listed because they already exist.

Maybe by running the elevated command prompt, I forced the routes into route.exe, and they are now persistent?
To be honest, I don't know much about route.exe.

If the routes are persistent then could it cause any issues when using the VPN, or when not using the VPN?