OpenVPN puts the route on the wrong interface - how to overcome it?

Question

openvpn

There is a VPN server with an internal network 192.168.100.x, an external address, etc., there are several clients on Windows XP-10. All of a sudden, one of the clients on Win10 started reporting a broken VPN connection. During the analysis, I found out that when a connection is established, the TAP device does not first rise, after some time it starts, but the routes from the VPN server to 192.168.0.0/16 through 192.168.100.1 are assigned to the external, non-TAP interface with the address 192.168 .хх.хх, as a result, the VPN server pings from both sides, both inside and outside, but the client cannot get into the local network behind the VPN. Manually adding the route after the connection is established solves the problem, but this is a crutch that I would not like to offer to the client (he does not understand the routes). What can be done and how? OpenVPN client version 1.0.3 compiled by VPN Builder into a monolithic executable,

Answer 1

Try to reinstall the TAP interface on the client, it helped me many times on win10.