Page 1 of 1

Can't install OpenVpn

Posted: Wed Jun 30, 2021 5:09 pm
by heinsenberg82
I'm not able to install OpenVPN on a specific machine with Windows 10, due to an error with the TAP driver.

I managed to custom install OpenVPN without Wintap drivers. When I try to run the following commands, these are the errors I get:

Code: Select all

> tapctl.exe list
get_device_reg_property: SetupDiGetDeviceRegistryProperty(1) failed
Error 0xd: Os dados sÒo invßlidos.

Code: Select all

> tapctl.exe create
tap_create_adapter: DiInstallDevice failed
Error 0xe0000203
Creating TUN/TAP adapter failed (error 0xe0000203).
Ps: no tap interface is shown on my network interfaces, neither on Device Manager.

I've already tried every tip on every forums on internet, but couldn't manage to find a solution. Any help would be appreciated, thanks!

Re: Can't install OpenVpn

Posted: Wed Jun 30, 2021 6:57 pm
by TinCanTech
Please use the official installer:
https://openvpn.net/community-downloads/

Re: Can't install OpenVpn

Posted: Tue Nov 02, 2021 2:56 pm
by yfag
I have the same problem but I cannot use the official installer :-(

I am using a compiled version for windows because I will have to implement openssl engines.

My server log:
2021-11-02 15:51:30 WARNING: --topology net30 support for server configs with IPv4 pools will be removed in a future release. Please migrate to --topology subnet as soon as possible.
2021-11-02 15:51:30 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-256-CBC' to --data-ciphers or change --cipher 'AES-256-CBC' to --data-ciphers-fallback 'AES-256-CBC' to silence this warning.
2021-11-02 15:51:30 OpenVPN 2.5.3 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Oct 27 2021
2021-11-02 15:51:30 Windows version 10.0 (Windows 10 or greater) 64bit
2021-11-02 15:51:30 library versions: OpenSSL 1.1.1k 25 Mar 2021, LZO 2.10
2021-11-02 15:51:30 NOTE: your local LAN uses the extremely common subnet address 192.168.0.x or 192.168.1.x. Be aware that this might create routing conflicts if you connect to the VPN server from public locations such as internet cafes that use the same subnet.
2021-11-02 15:51:31 Diffie-Hellman initialized with 2048 bit key
2021-11-02 15:51:31 interactive service msg_channel=0
2021-11-02 15:51:31 ROUTE_GATEWAY 192.168.1.1/255.255.255.0 I=16 HWADDR=7c:76:35:bb:cd:5d
2021-11-02 15:51:31 open_tun
2021-11-02 15:51:31 There are no TAP-Windows nor Wintun adapters on this system. You should be able to create an adapter by using tapctl.exe utility.
2021-11-02 15:51:31 Exiting due to fatal error

So if I want to create a tap interface on my own:
tap_create_adapter: DiInstallDevice failed
Error 0xe0000203
Creating TUN/TAP adapter failed (error 0xe0000203).

Any help will be appreciated!

Re: Can't install OpenVpn

Posted: Tue Nov 02, 2021 3:59 pm
by TinCanTech
yfag wrote:
Tue Nov 02, 2021 2:56 pm
I am using a compiled version for windows because I will have to implement openssl engines.
--engine [engine-name] Enable OpenSSL hardware-based crypto engine functionality.

Re: Can't install OpenVpn

Posted: Wed Nov 03, 2021 9:39 am
by yfag
TinCanTech wrote:
Tue Nov 02, 2021 3:59 pm
yfag wrote:
Tue Nov 02, 2021 2:56 pm
I am using a compiled version for windows because I will have to implement openssl engines.
--engine [engine-name] Enable OpenSSL hardware-based crypto engine functionality.
Thanks but I understand that I will have to use --engine option but for now without any engine I want to set up a simple vpn client/server and I have to create a tap interface and thE command is failing.

Re: Can't install OpenVpn

Posted: Sun Nov 07, 2021 7:33 am
by temporary-gorilla
Hi. I had faced a similar issue in the past, and it was due to not being able to install TUN adapters as the build I was using was not signed. I had instead extracted drivers from Eddie VPN installer, then run the wintun.msi file, after which the tapctl command ran fine. However this was about an year ago or so. I faced the similar issue again when working for a newer client and now it does not seem to work in either case, however cannot pin down the reason for it acting like so.