Openvpn error 536870397

OpenVPN Support Forum

Community Support Forum

Error during installation of windows client OpenVPN 2.5.0 amd64 OpenVPNMSICA tap_create_adapter Error 536870397 solution

Error during installation of windows client OpenVPN 2.5.0 amd64 OpenVPNMSICA tap_create_adapter Error 536870397 solution

Post by 12thFactor » Thu Nov 05, 2020 9:53 pm

Hi there everyone today I decided to move from version 2.4 to 2.5 but there was a problem with the installation.

On my machine I had version 2.4 previously installed I downloaded the client installer for version 2.5, after I installed it I noticed that another network adapter was also installed alongside TAP-Windows Adapter V9. Surprised by this I decided maybe this was because I have to do a clean install. Consequently, I uninstalled version 2.5 which I had just installed, but still the «OpenVPN Wintun» device remained behind. I decided to remove it using Windows 10 device manager including the driver.

But after that, when I tried to reinstall OpenVPN client 2.5 there was this error message:

OpenVPNMSICA: tap_create_adapter:
DiInstallDevice failed Error — 536870397:

No more explanations!

The resolution:
At first I was frustrated, but after I looked around a bit I figured it out and now I am sharing it here in case anyone else is having similar issues or problems.

Here is what to do: The device being installed which fails obviously is the network adapter, for the new Wintun device. So if you somehow could get it installed your problems would go away. This can be done in two ways:

1- You can simply open up the installer msi but this time choose to customize the installation. and after that select to not install the TAP-Windows6 and Wintun drivers. They are going to get installed, only this time you are not going to receive an error any longer. But obviously you are going to be missing a network interface. In order to take care of that open an Admin level command prompt and cd to OpenVPNbin directory wherever you installed it. and then issue the command:

Will produce the error:
DiInstallDevice failed
Error 0xe0000203
Creating TUN/TAP adapter failed (error 0xe0000203)

2- This is the most simple solution and will also get you your Wintun network device back. You have to simply reinstall wireguard https://www.wireguard.com/install/if you have had it previously installed.(remove it and then reinstall it) and after that try installing openvpn again with the derivers and there should be no problems.

Hope this helps anyone who is having similar issues.

Источник

OpenVPN Support Forum

Community Support Forum

Error during installation of windows client OpenVPN 2.5.0 amd64 OpenVPNMSICA tap_create_adapter Error 536870397 solution

Error during installation of windows client OpenVPN 2.5.0 amd64 OpenVPNMSICA tap_create_adapter Error 536870397 solution

Post by 12thFactor » Thu Nov 05, 2020 9:53 pm

Hi there everyone today I decided to move from version 2.4 to 2.5 but there was a problem with the installation.

On my machine I had version 2.4 previously installed I downloaded the client installer for version 2.5, after I installed it I noticed that another network adapter was also installed alongside TAP-Windows Adapter V9. Surprised by this I decided maybe this was because I have to do a clean install. Consequently, I uninstalled version 2.5 which I had just installed, but still the «OpenVPN Wintun» device remained behind. I decided to remove it using Windows 10 device manager including the driver.

But after that, when I tried to reinstall OpenVPN client 2.5 there was this error message:

OpenVPNMSICA: tap_create_adapter:
DiInstallDevice failed Error — 536870397:

No more explanations!

The resolution:
At first I was frustrated, but after I looked around a bit I figured it out and now I am sharing it here in case anyone else is having similar issues or problems.

Here is what to do: The device being installed which fails obviously is the network adapter, for the new Wintun device. So if you somehow could get it installed your problems would go away. This can be done in two ways:

1- You can simply open up the installer msi but this time choose to customize the installation. and after that select to not install the TAP-Windows6 and Wintun drivers. They are going to get installed, only this time you are not going to receive an error any longer. But obviously you are going to be missing a network interface. In order to take care of that open an Admin level command prompt and cd to OpenVPNbin directory wherever you installed it. and then issue the command:

Will produce the error:
DiInstallDevice failed
Error 0xe0000203
Creating TUN/TAP adapter failed (error 0xe0000203)

2- This is the most simple solution and will also get you your Wintun network device back. You have to simply reinstall wireguard https://www.wireguard.com/install/if you have had it previously installed.(remove it and then reinstall it) and after that try installing openvpn again with the derivers and there should be no problems.

Hope this helps anyone who is having similar issues.

Источник

OpenVPN Support Forum

Community Support Forum

Can’t install OpenVpn

Can’t install OpenVpn

Post by heinsenberg82 » Wed Jun 30, 2021 5:09 pm

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:

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

Post by TinCanTech » Wed Jun 30, 2021 6:57 pm

Re: Can’t install OpenVpn

Post by yfag » Tue Nov 02, 2021 2:56 pm

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

Источник

tap_create_adapter: DinstallDevice failed error about openvpn-build HOT 3 OPEN

I’m also getting this error. I had OpenVPN 2.5.3 previously installed on this system a year ago. Now I need OpenVPN again and I can’t install 2.5.7 because of this error.

mattock commented on January 16, 2023

Can you try manually removing all traces of any previous tap-windows6 adapters as outlined here in the Debugging section:

Inverness commented on January 16, 2023

Can you try manually removing all traces of any previous tap-windows6 adapters as outlined here in the Debugging section:

I wanted to add that the error only appears when selecting to install the Wintun driver. When I select only the Tap driver, installation is successful.

• Cannot build v2.5.1 due to a missing lz4.h file HOT 6
• DISABLESAVEPWD not working HOT 1
• generic build for Windows does not build openvpnserv2.exe HOT 1
• Launch on user logon setting lost on upgrade HOT 6
• Building 2.6_git for Windows with NSIS fails for openvpn.8.html HOT 5
• fail to build on any macos/linux HOT 5
• Windows NSIS installer and Easy-RSA 3 HOT 2
• mingw builds HOT 6
• Build Openvpn on a 64 bit windows host for a 32 bit windows target HOT 4
• Configure OpenSSL while Building HOT 9
• [Feature] Make the Docker image official HOT 7
• netcfginstanceid registry value failed HOT 1
• Build failed 2.5.8 HOT 4
• PLAP not in released MSI HOT 2
• Typo in latest build for macOS HOT 1
• centos 7 gcc: error: lz4-exe.o: 没有那个文件或目录 HOT 6
• Hard coded path in openvpn-plap-install.reg HOT 2
• Installer — Enable multilanguage installer HOT 3
• libopenvpn_plap.dll is not signed

Recommend Projects

React

A declarative, efficient, and flexible JavaScript library for building user interfaces.

Vue.js

🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

Typescript

TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

TensorFlow

An Open Source Machine Learning Framework for Everyone

Django

The Web framework for perfectionists with deadlines.

Laravel

A PHP framework for web artisans

Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

javascript

JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

Some thing interesting about web. New door for the world.

server

A server is a program made to process requests and deliver data to clients.

Machine learning

Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

Visualization

Some thing interesting about visualization, use data art

Some thing interesting about game, make everyone happy.

Recommend Org

Facebook

We are working to build community through open source technology. NB: members must have two-factor auth.

Microsoft

Open source projects and samples from Microsoft.

Источник

Почему не устанавливается драйвер для penvpn(tap-windows)?

Пытаюсь на windows 7 поставить openvpn client, при установке возникает ошибка «error occurred installing the TAP device driver»
Лог установщика:
We are running on a 64-bit system.
Output folder: C:Program FilesTAP-Windowsbin
Extract: devcon.exe. 100%
Output folder: C:Program FilesTAP-Windowsdriver
Extract: OemWin2k.inf. 100%
Extract: tap0901.cat. 100%
Extract: tap0901.sys. 100%
Output folder: C:Program FilesTAP-Windows
Extract: license.txt. 100%
Extract: icon.ico. 100%
devcon.exe hwids returned: 0
TAP install (tap0901) (May require confirmation)
Device node created. Install is complete when drivers are installed.
Updating drivers for tap0901 from C:Program FilesTAP-WindowsdriverOemWin2k.inf.
devcon.exe failed.
devcon.exe returned: 2
devcon.exe cumulative status: 2
Created uninstaller: C:Program FilesTAP-WindowsUninstall.exe
Completed

Как я понял devcon.exe это какая-то очередная мелкософтская софтина для установки драйверов при этом не штатная(не из коробки).
По итогу установки остается только драйвер и бинарник devcon.exe
Пробовал запускать бинарник из командной строки от админа
devcon.exe install «OemWin2k.inf» «C:Program FilesTAP-Windowsdriver»
devcon.exe failed.
Пробовл через штатный установщик драйверов hdwwiz — произошла ошибка.
Пробовал отключать проверку цифровой подписи. Не помогло.
Хвост логов C:Windowsinfsetupapi.dev.log здесь https://pastebin.com/AGPxKMMQ
Пробовал запускать исправление неполадок, скачивать уйму майкрософтским программ для устранения ошибок — ругаются на некоторые драйверы или пытаюся исправить, но по-какой-то причине не могут(пытаются обновить драйвер и не находят в системе, либо вероятно находят, но коротко сообщают — «отказ»).
До этого на машине стоял VMware и VirtualBox и очень замусорили систему своими виртуальными устройствами. Была ситуация, когда стим переставал обновляться из-за большого количества сетевых устройств(около 20). Решилась отключением этих устройств. В настоящий момент оба виртуализатора удалены, видимых лишних сетевых устройств в «изменение параметров адапетра» нет(осталось 4 шт). В диспечере устройств осталось несколько драйверов и неопознанных устройств, но что с ними можно сделать, если они штатно не обновляются.

Предложите как это можно решить(само собой без переустановки винды), где можно посмотреть причину(где логи, Лебовски?).

• Вопрос задан более трёх лет назад
• 5168 просмотров

Отключил проверку подписей сертификатов при загрузке(до этого отключал политикой), поудалял какие смог устройства, оставшиеся от виртуалок(vmware, virtualbxox+один из интерфейсов ISATAP), поломал, потом повосстанавливал реестр(HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlNetwork), неудачно попытался воспользоваться certutils, подробно поизучал логи. В итоге
tap-windows-9.9.2_3 так и не заработал — устройство появилось в диспечере устройств неопознанным, писало, что устройство не подключено.
openvpn-install-2.3.13-I601-x86_64 установил драйвер, ошибок не показывал, но т.к. драйвер не подписан, то работало только при отключении проверки сертификтов при загрузке, но работает! Проверил, успешно подключается, интерфейс есть.

Т.е. похоже все дело из-за подписи. Надо подумать как заставить драйвер работать в обычном режиме(в нем подпись проверяется, драйвер соответственно не работает и TAP адаптер среди сетевых интерфейсов в центре управления сетями пропал). Вроде можно самим подписать.

Перестал работать и в режиме без проверки подписей драйверов(не знаю почему).
Дрова самоподписанным сертификатов подписать не смог(возможно что то не так делал), но сертификаты итак лежат в доверенных издателях(видимо после галочки «всегда доверять этому издатели» при установке драйвера).
Переустановка не помогла.
Удаление пакетов через
pnputil.exe -e
pnputil.exe -d Oem#.inf (где# номер тап драйвера и драйверов виртуальных машин)
не помогла.
Виндовое устранение неисправностей не помогло.
Помог поиск по реестру по ROOTNET000 (упоминается в ошибке).
Находится в одной из папок реестра, где лежит и значение «Подключение по локальной сети 3″(которого давно нет).
Помогло удаление всех (трех) папок реестра с этим значением. Пример одного из них:
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINESYSTEMControlSet001ControlNetwork<4d36e972-e325-11ce-bfc1-08002be10318><54e4a266-cf20-4c30-9a05-a7fb94045197>Connection]
«DefaultNameResourceId»=dword:0000070a
«DefaultNameIndex»=dword:00000003
«Name»=»Подключение по локальной сети 3»
«PnpInstanceID»=»ROOT\NET\0000»
«MediaSubType»=dword:00000000

После этого все заработало.
Вопрос можно считать закрытым. Похоже при адекватном использовании и современная винда(юзерферйндли, ага) должна быть переустановлена каждые полгода(а потому должна умереть). Привожу сюда (только) ошибки из лога, чтобы они проиндексировалась в поисковике.
! sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
! inf: Package was already in store: skipping Driver Store add
! sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
! sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
! inf: Empty Section! [tap0901.files]
! sig: VerifyTrustFailed for C:Windowssystem32DRIVERStap0901.sys.
! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
. cci: NdisCoinst:NcipCreatePersistedInterface DeviceIoControl failed with error 0x1f
. cci: NdisCoinst: NcipCreatePersistentInterface failed with error 0x1f
. dvi: CoInstaller 1: failed(0x0000001f)!
. dvi: Error 31: A device attached to the system is not functioning.
. ndv: Error(0000001f) installing device!
! ndv: Queueing up error report since device installation failed.
! ndv: Installing NULL driver!
! cci: !NCI: IfType Present, NetLuidIndex NOT Present. pszPnpID= ROOTNET000
. dvi: Error obtaining device ID!
. dvi: Cleaning up failed installation (00000006)
! dvi: Failed to set Config Flags property: 0x00000020
! dvi: Error 0xe000020b: The device instance does not exist in the hardware tree.
. dvi: Default installer: failed!
. dvi: Error 6: The handle is invalid.
! dvi: Driver list already built
. dvi: Class installer: failed(0xe000020b)!
. dvi: Error 0xe000020b: The device instance does not exist in the hardware tree.

Источник