-
12thFactor
- OpenVpn Newbie
- Posts: 3
- Joined: Thu Nov 05, 2020 9:18 pm
Error during installation of windows client OpenVPN 2.5.0 amd64 OpenVPNMSICA tap_create_adapter Error 536870397 solution
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:
This will create a network interface which you can remove using:
In such a scenario you will not get your Wintun network adapter back even using 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.
Last edited by 12thFactor on Thu Nov 05, 2020 10:18 pm, edited 1 time in total.
-
TinCanTech
- OpenVPN Protagonist
- Posts: 11142
- Joined: Fri Jun 03, 2016 1:17 pm
Re: Error during installation of windows client OpenVPN 2.5.0 amd64 OpenVPNMSICA tap_create_adapter Error 536870397 solu
Post
by TinCanTech » Thu Nov 05, 2020 10:01 pm
Are you saying that
installing OpenVPN to a Windows PC which already has Wireguard installed causes problems ?
-
12thFactor
- OpenVpn Newbie
- Posts: 3
- Joined: Thu Nov 05, 2020 9:18 pm
Re: Error during installation of windows client OpenVPN 2.5.0 amd64 OpenVPNMSICA tap_create_adapter Error 536870397 solu
Post
by 12thFactor » Thu Nov 05, 2020 10:09 pm
TinCanTech wrote: ↑
Thu Nov 05, 2020 10:01 pm
Are you saying thatinstalling OpenVPN to a Windows PC which already has Wireguard installed causes problems ?
Yes, but quite very possibly not under normal circumstances, only if the driver for wireguard network adapter is not present on the machine or if it is manually removed from a machine that has wiregaurd installed but its driver is removed.
Consider my situation and how that error was produced on my machine.
-
12thFactor
- OpenVpn Newbie
- Posts: 3
- Joined: Thu Nov 05, 2020 9:18 pm
Re: Error during installation of windows client OpenVPN 2.5.0 amd64 OpenVPNMSICA tap_create_adapter Error 536870397 solu
Post
by 12thFactor » Thu Nov 05, 2020 11:02 pm
Yes absolutely please feel free to do it, it is not about who would it it is about the problem being solved thanks, please . feel free to report it on github.
I am not on github.
-
unicornir
- OpenVpn Newbie
- Posts: 3
- Joined: Sat Dec 26, 2020 4:49 pm
Re: Error during installation of windows client OpenVPN 2.5.0 amd64 OpenVPNMSICA tap_create_adapter Error 536870397 solu
Post
by unicornir » Sat Dec 26, 2020 5:00 pm
Hi!
I have the same problem in my Windows 10 v1607 build:14393.0. I notice this problem when I try to install new version of Windscribe. The installation goes till it reaches to 60%, and after some while it show this message:
An error occurred installing the TAP device driver: 2
Short story, after some digging, I found out the root problem is OpenVPN and I uninstall all of my VPN’s and their TAP drivers also OpenVPN itself. Then try to install OpenVPN v2.5.0 x64 and I got another error message! Then I found out this topic and try this command: «tapctl create» but I get bellow message at CMD (in Admin mode):
tap_create_adapter: DiInstallDevice failed
Error 0x5b4: This operation returned because the timeout period expired.
Creating TUN/TAP adapter failed (error 0x5b4).
Now, I cannot install any of my VPN’s!!! What I have done till now:
1) Uninstall all VPN’s with Revo Uninstaller with their leftovers.
2) Use CCleaner + Disk Clean built-in Windows.
3) Restart many times!
4) Disable Comodo Firewall + Its HIPS completely (I am sure it is not the root of the problem)
5) I do not have «wireguard » as mentioned in the first post!
6) Disable all other network adapters in my network control panel except my main one, before I reinstall OpenVPN. (I found this solution on the net) (I have VMWare v15.5.6)
What can I do to solve this problem!?
Thanks in Advanced
-
TinCanTech
- OpenVPN Protagonist
- Posts: 11142
- Joined: Fri Jun 03, 2016 1:17 pm
Re: Error during installation of windows client OpenVPN 2.5.0 amd64 OpenVPNMSICA tap_create_adapter Error 536870397 solu
Post
by TinCanTech » Sat Dec 26, 2020 5:08 pm
unicornir wrote: ↑
Sat Dec 26, 2020 5:00 pm
What can I do to solve this problem!?
unicornir wrote: ↑
Sat Dec 26, 2020 5:00 pm
Disable Comodo Firewall + Its HIPS completely
I would uninstall this ..
-
unicornir
- OpenVpn Newbie
- Posts: 3
- Joined: Sat Dec 26, 2020 4:49 pm
Re: Error during installation of windows client OpenVPN 2.5.0 amd64 OpenVPNMSICA tap_create_adapter Error 536870397 solu
Post
by unicornir » Sat Dec 26, 2020 9:47 pm
TinCanTech wrote: ↑
Sat Dec 26, 2020 5:08 pm
I would uninstall this ..
Well, as I pointed, Comodo is not a problem! To make sure, I try same Windows 10 Version on VMware virtual machine with Comodo on it and without any problems I could install OpenVPN v2.5.0 and new Windscribe v2.0 beta! So there should be another problem with my main machine Windows 10!!??
-
TinCanTech
- OpenVPN Protagonist
- Posts: 11142
- Joined: Fri Jun 03, 2016 1:17 pm
Re: Error during installation of windows client OpenVPN 2.5.0 amd64 OpenVPNMSICA tap_create_adapter Error 536870397 solu
Post
by TinCanTech » Sun Dec 27, 2020 2:11 am
«If I have 5 exploding carrots and 3 of them explode then how many exploding pears do I have ?»
-
unicornir
- OpenVpn Newbie
- Posts: 3
- Joined: Sat Dec 26, 2020 4:49 pm
Re: Error during installation of windows client OpenVPN 2.5.0 amd64 OpenVPNMSICA tap_create_adapter Error 536870397 solu
Post
by unicornir » Sun Dec 27, 2020 10:11 am
TinCanTech wrote: ↑
Sun Dec 27, 2020 2:11 am
«If I have 5 exploding carrots and 3 of them explode then how many exploding pears do I have ?»
I am seeking for help here 
! and not funny posts! 
Is there any Admin’s or OpenVPN programmers checking here!? I post the error message in my message. What can I do to solve the problem and be able to install OpenVPN and Windscribe on my system again.
-
desbest
- OpenVpn Newbie
- Posts: 18
- Joined: Fri May 18, 2018 8:11 am
Re: Error during installation of windows client OpenVPN 2.5.0 amd64 OpenVPNMSICA tap_create_adapter Error 536870397 solu
Post
by desbest » Sat Feb 20, 2021 12:32 am
unicornir wrote: ↑
Sun Dec 27, 2020 10:11 am
TinCanTech wrote: ↑
Sun Dec 27, 2020 2:11 am
«If I have 5 exploding carrots and 3 of them explode then how many exploding pears do I have ?»I am seeking for help here
! and not funny posts!
Is there any Admin’s or OpenVPN programmers checking here!? I post the error message in my message. What can I do to solve the problem and be able to install OpenVPN and Windscribe on my system again.
I believe that TinCanTech is saying metaphorically and colloquially, that just because something solves part of a problem or fails to solve it in a particular circumstance, doesn’t mean that it cannot solve your problem in your specific circumstance, or there’s no other things to consider to solve the problem completely (ie. your specific circumstance). In your case, your antivirus (Comodo), so you should try out the suggestion given, rather than to say «it works in my virtual machine».
-
sextant
- OpenVpn Newbie
- Posts: 10
- Joined: Wed Dec 01, 2021 8:29 am
Re: Error during installation of windows client OpenVPN 2.5.0 amd64 OpenVPNMSICA tap_create_adapter Error 536870397 solu
Post
by sextant » Wed Dec 01, 2021 8:33 am
Hello!
I get exactly the same (== 536870397) error code when trying to install v2.5.4 on vanilla win7/64.
(«vanilla» means — no antiviruses or any other 3rd party code, only the native win7 stuff — untweaked)
-
TinCanTech
- OpenVPN Protagonist
- Posts: 11142
- Joined: Fri Jun 03, 2016 1:17 pm
Re: Error during installation of windows client OpenVPN 2.5.0 amd64 OpenVPNMSICA tap_create_adapter Error 536870397 solu
Post
by TinCanTech » Wed Dec 01, 2021 1:16 pm
Please post your install log C:Windowsinfsetupapi.dev.log
Only the last few days of it should be enough.
-
sextant
- OpenVpn Newbie
- Posts: 10
- Joined: Wed Dec 01, 2021 8:29 am
Re: Error during installation of windows client OpenVPN 2.5.0 amd64 OpenVPNMSICA tap_create_adapter Error 536870397 solu
Post
by sextant » Thu Dec 02, 2021 9:36 am
Sorry for the layout, could not find the «spoiler» tag here…
Code: Select all
[Boot Session: 2021/12/01 10:54:32.407]
>>> [Device Install (DiInstallDevice) - ROOTNET000]
>>> Section start 2021/12/01 11:08:17.555
cmd: C:Windowssystem32MsiExec.exe -Embedding B6D8C0C6854D62B58186741776B67AD1 M GlobalMSI0000
dvi: Set selected driver complete.
dvi: Set selected driver complete.
dvi: {Build Driver List} 11:08:17.556
dvi: Searching for hardware ID(s):
dvi: wintun
cpy: Policy is set to make all digital signatures equal.
dvi: Enumerating INFs from path list 'C:Windowsinf'
inf: Searched 0 potential matches in published INF directory
inf: Searched 35 INFs in directory: 'C:Windowsinf'
dvi: {Build Driver List - exit(0x00000000)} 11:08:21.304
dvi: {DIF_SELECTBESTCOMPATDRV} 11:08:21.304
dvi: CoInstaller 1: Enter 11:08:21.305
dvi: CoInstaller 1: Exit
dvi: CoInstaller 2: Enter 11:08:21.305
dvi: CoInstaller 2: Exit
dvi: CoInstaller 3: Enter 11:08:21.306
dvi: CoInstaller 3: Exit
dvi: Class installer: Enter 11:08:21.306
dvi: Class installer: Exit
dvi: Default installer: Enter 11:08:21.307
dvi: {Select Best Driver}
! dvi: Selecting driver failed(0xe0000228)
dvi: {Select Best Driver - exit(0xe0000228)}
! dvi: Default installer: failed!
! dvi: Error 0xe0000228: There are no compatible drivers for this device.
dvi: {DIF_SELECTBESTCOMPATDRV - exit(0xe0000228)} 11:08:21.403
<<< Section end 2021/12/01 11:08:21.404
<<< [Exit status: FAILURE(0xe0000203)]
>>> [Device Install (DiInstallDevice) - ROOTNET000]
>>> Section start 2021/12/01 11:10:18.054
cmd: C:Windowssystem32MsiExec.exe -Embedding 520F59B75410D3C7832A29B1733CD0F5 M GlobalMSI0000
dvi: Set selected driver complete.
dvi: Set selected driver complete.
dvi: {Build Driver List} 11:10:18.055
dvi: Searching for hardware ID(s):
dvi: wintun
cpy: Policy is set to make all digital signatures equal.
dvi: Enumerating INFs from path list 'C:Windowsinf'
inf: Searched 0 potential matches in published INF directory
inf: Searched 35 INFs in directory: 'C:Windowsinf'
dvi: {Build Driver List - exit(0x00000000)} 11:10:18.140
dvi: {DIF_SELECTBESTCOMPATDRV} 11:10:18.140
dvi: CoInstaller 1: Enter 11:10:18.141
dvi: CoInstaller 1: Exit
dvi: CoInstaller 2: Enter 11:10:18.141
dvi: CoInstaller 2: Exit
dvi: CoInstaller 3: Enter 11:10:18.141
dvi: CoInstaller 3: Exit
dvi: Class installer: Enter 11:10:18.141
dvi: Class installer: Exit
dvi: Default installer: Enter 11:10:18.142
dvi: {Select Best Driver}
! dvi: Selecting driver failed(0xe0000228)
dvi: {Select Best Driver - exit(0xe0000228)}
! dvi: Default installer: failed!
! dvi: Error 0xe0000228: There are no compatible drivers for this device.
dvi: {DIF_SELECTBESTCOMPATDRV - exit(0xe0000228)} 11:10:18.143
<<< Section end 2021/12/01 11:10:18.143
<<< [Exit status: FAILURE(0xe0000203)]
>>> [Device Install (Hardware initiated) - USBVID_0483&PID_DF11FFFFFFFEFFFF]
>>> Section start 2021/12/01 15:19:25.340
ump: Creating Install Process: DrvInst.exe 15:19:25.374
ndv: Retrieving device info...
ndv: Setting device parameters...
ndv: Searching Driver Store and Device Path...
dvi: {Build Driver List} 15:19:25.660
dvi: Searching for hardware ID(s):
dvi: usbvid_0483&pid_df11&rev_2200
dvi: usbvid_0483&pid_df11
dvi: Searching for compatible ID(s):
dvi: usbclass_fe&subclass_01&prot_02
dvi: usbclass_fe&subclass_01
dvi: usbclass_fe
cpy: Policy is set to make all digital signatures equal.
dvi: Enumerating INFs from path list 'C:Windowsinf'
inf: Searched 0 potential matches in published INF directory
inf: Searched 35 INFs in directory: 'C:Windowsinf'
dvi: {Build Driver List - exit(0x00000000)} 15:19:26.135
ndv: Selecting best match from Driver Store (including Device Path)...
dvi: {DIF_SELECTBESTCOMPATDRV} 15:19:26.136
dvi: No class installer for 'STM32 BOOTLOADER'
dvi: No CoInstallers found
dvi: Default installer: Enter 15:19:26.136
dvi: {Select Best Driver}
! dvi: Selecting driver failed(0xe0000228)
dvi: {Select Best Driver - exit(0xe0000228)}
! dvi: Default installer: failed!
! dvi: Error 0xe0000228: There are no compatible drivers for this device.
dvi: {DIF_SELECTBESTCOMPATDRV - exit(0xe0000228)} 15:19:26.159
ndv: Searching Windows Update for drivers... 15:19:26.189
ndv: Acquired WU search serialization mutex. 15:19:26.189
ndv: About to release WU search serialization mutex. 15:19:26.226
ndv: No driver found on Windows Update. 15:19:26.226
ndv: {Core Device Install} 15:19:26.228
! ndv: Installing NULL driver!
dvi: Set selected driver complete.
dvi: {DIF_ALLOW_INSTALL} 15:19:26.229
dvi: No class installer for 'STM32 BOOTLOADER'
dvi: Default installer: Enter 15:19:26.229
dvi: Default installer: Exit
dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 15:19:26.230
dvi: {DIF_INSTALLDEVICE} 15:19:26.230
dvi: No class installer for 'STM32 BOOTLOADER'
dvi: Default installer: Enter 15:19:26.231
! dvi: Installing NULL driver!
dvi: Writing common driver property settings.
dvi: {Restarting Devices} 15:19:26.310
dvi: Restart: USBVID_0483&PID_DF11FFFFFFFEFFFF
dvi: Restart complete.
dvi: {Restarting Devices exit} 15:19:26.364
dvi: Default installer: Exit
dvi: {DIF_INSTALLDEVICE - exit(0x00000000)} 15:19:26.365
ndv: Device install status=0xe0000203
ndv: Performing device install final cleanup...
! ndv: Queueing up error report since device installation failed...
ndv: {Core Device Install - exit(0xe0000203)} 15:19:26.367
ump: Server install process exited with code 0xe0000203 15:19:26.369
<<< Section end 2021/12/01 15:19:26.372
<<< [Exit status: FAILURE(0xe0000203)]
-
sextant
- OpenVpn Newbie
- Posts: 10
- Joined: Wed Dec 01, 2021 8:29 am
Re: Error during installation of windows client OpenVPN 2.5.0 amd64 OpenVPNMSICA tap_create_adapter Error 536870397 solu
Post
by sextant » Thu Dec 02, 2021 11:20 am
My attempt to use the solution from the very first post here also failed:
Code: Select all
Microsoft Windows [Version 6.1.7601]
(c) Корпорация Майкрософт (Microsoft Corp.), 2009. Все права защищены.
C:PROGRA~1OpenVPNbin>dir
Том в устройстве C не имеет метки.
Серийный номер тома: 567A-3901
Содержимое папки C:PROGRA~1OpenVPNbin
2021-12-02 14:12 <DIR> .
2021-12-02 14:12 <DIR> ..
2021-10-20 10:23 3 482 288 libcrypto-1_1-x64.dll
2021-10-20 10:23 93 872 libpkcs11-helper-1.dll
2021-10-20 10:23 694 448 libssl-1_1-x64.dll
2021-10-20 10:23 121 008 lzo2.dll
2021-10-20 10:23 811 696 openvpn-gui.exe
2021-10-20 10:23 840 880 openvpn.exe
2021-10-20 10:23 64 176 openvpnserv.exe
2021-10-20 10:23 37 040 tapctl.exe
2021-09-10 12:24 97 152 vcruntime140.dll
9 файлов 6 242 560 байт
2 папок 81 250 205 696 байт свободно
C:PROGRA~1OpenVPNbin>tapctl.exe create
tap_create_adapter: DiInstallDevice failed
Error 0xe0000203
Creating TUN/TAP adapter failed (error 0xe0000203).
C:PROGRA~1OpenVPNbin>-
sextant
- OpenVpn Newbie
- Posts: 10
- Joined: Wed Dec 01, 2021 8:29 am
Re: Error during installation of windows client OpenVPN 2.5.0 amd64 OpenVPNMSICA tap_create_adapter Error 536870397 solu
Post
by sextant » Thu Dec 02, 2021 11:44 am
Too early to rejoice… 
When I try to establish a tunnel I get the…
Code: Select all
2021-12-02 14:42:11 open_tun
2021-12-02 14:42:11 CreateFile failed on tap-windows6 device: \.Global{1D7A6C47-3E55-4568-A779-F4B4BE2AC5EE}.tap
2021-12-02 14:42:11 MANAGEMENT: Client disconnected
2021-12-02 14:42:11 All tap-windows6 adapters on this system are currently in use or disabled.
2021-12-02 14:42:11 Exiting due to fatal error-
TinCanTech
- OpenVPN Protagonist
- Posts: 11142
- Joined: Fri Jun 03, 2016 1:17 pm
Re: Error during installation of windows client OpenVPN 2.5.0 amd64 OpenVPNMSICA tap_create_adapter Error 536870397 solu
Post
by TinCanTech » Thu Dec 02, 2021 1:24 pm
Did you ever get a TAP Adapter to install ? If not, you could try wintun ?
-
sextant
- OpenVpn Newbie
- Posts: 10
- Joined: Wed Dec 01, 2021 8:29 am
Re: Error during installation of windows client OpenVPN 2.5.0 amd64 OpenVPNMSICA tap_create_adapter Error 536870397 solu
Post
by sextant » Thu Dec 02, 2021 4:08 pm
I do not know. I just run the MSI file.
After the KloneBlake’s trick I did not see any error messages during the installation. But the VPN does not work.
Содержание
- OpenVPN Support Forum
- Can’t install OpenVpn
- Can’t install OpenVpn
- Re: Can’t install OpenVpn
- Re: Can’t install OpenVpn
- OpenVPN и TAP-Windows adapter.
- OpenVPN 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
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:bb
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).
Источник
OpenVPN и TAP-Windows adapter.
Все новые темы
| Автор | ||||
|---|---|---|---|---|
| NickCo Новичок Зарегистрирован: 27.10.2010
|
|
|||
| Вернуться к началу |
|
|||
 |
||||
| Зарегистрируйтесь и реклама исчезнет!
|
||||
|
||||
| NotAvailable подпись на выбор, в личку sklifу Зарегистрирован: 24.10.2008 |
|
|||
| Вернуться к началу |
|
|||
|
||||
| NickCo Новичок Зарегистрирован: 27.10.2010
|
|
|||
| Вернуться к началу |
|
|||
|
||||
| Desv Активный участник
Зарегистрирован: 18.04.2007 |
|
|||
| Вернуться к началу |
|
|||
|
||||
| NickCo Новичок Зарегистрирован: 27.10.2010
|
|
|||
| Вернуться к началу |
|
|||
|
||||
| NotAvailable подпись на выбор, в личку sklifу Зарегистрирован: 24.10.2008 |
|
|||
| Вернуться к началу |
|
|||
|
||||
| Desv Активный участник
Зарегистрирован: 18.04.2007 |
|
|||
| Вернуться к началу |
|
|||
|
||||
| NotAvailable подпись на выбор, в личку sklifу Зарегистрирован: 24.10.2008 |
|
|||
| Вернуться к началу |
|
|||
|
||||
| NickCo Новичок Зарегистрирован: 27.10.2010 Источник OpenVPN Support ForumCommunity Support Forum Error during installation of windows client OpenVPN 2.5.0 amd64 OpenVPNMSICA tap_create_adapter Error 536870397 solutionError during installation of windows client OpenVPN 2.5.0 amd64 OpenVPNMSICA tap_create_adapter Error 536870397 solutionPost 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: No more explanations! The resolution: 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: 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. Источник Adblock |
Closed
Error during installation of windows client OpenVPN 2.5.8 amd64 OpenVPNMSICA tap_create_adapter Error 536870397 #549
Issue Opened
AR45H Opened Issue On Nov 30th 2022, 8:48
AR45H
Hi,
The installer fails to create a wintun adapter with error 536870397
Attempts to create the adapter through the tapctl executable with create --hwid wintun returns the following error:
tap_create_adapter: DiInstallDevice failed
Error 0xe0000203
Creating TUN/TAP adapter failed (error 0xe0000203). Workarounds mentioned in this forum post do not work
Comment
AR45H commented on 2 months ago
AR45H
I should add that unticking the TUN adapter in the installer will successfully install the client with only the TAP adapter
Lstipakov
Please open an issue here and provide relevant parts of C:WindowsINFsetupapi.dev.log.
About Repository
| OpenVPN GUI is a graphical frontend for OpenVPN running on Windows 7 / 8 / 10. It creates an icon in the notification area from which you can control OpenVPN to start/stop your VPN tunnels, view the log and do other useful things. |
|
Language: C |
|
Star: 1151 |
|
Fork: 378 |
|
Watchers: 1151 |
|
Open Issues: 44 |
| https://github.com/OpenVPN/openvpn-gui |
| Other |
| Last updated: 08 Feb 2023 |
| Tropics: |
Error during installation of windows client OpenVPN 2.5.8 amd64 OpenVPNMSICA tap_create_adapter Error 536870397
Hi,
The installer fails to create a wintun adapter with error 536870397
Attempts to create the adapter through the tapctl executable with create --hwid wintun returns the following error:
tap_create_adapter: DiInstallDevice failed
Error 0xe0000203
Creating TUN/TAP adapter failed (error 0xe0000203).
Workarounds mentioned in this forum post do not work
I should add that unticking the TUN adapter in the installer will successfully install the client with only the TAP adapter
Please open an issue here and provide relevant parts of C:WindowsINFsetupapi.dev.log.
0
0
22.04.2012, 04:04
Попробуйте использовать точку восстановления системы, возможно, вам повезет и вы сможете восстановить программу таким образом. Или идите на офсайт
www.zune.net
скачивайте последнюю версию программы и пробуйте снова ее установить.
0
0
22.04.2012, 04:48
ну так я оттуда и скачивал! система уверен не поможет…
1
1
22.04.2012, 05:01
тогда попробуйте это.
1. Скачайте и распакуйте
WICU
на рабочий стол
2. Установите WICU
Стоит отметить, что если вы используете Windows 7: То щелкните правой кнопкой мышки и выберите пункт «Свойства», затем перейдите на вкладку «совместимость» и выберите галочку запускать программу в режиме совместимости с Windows XP.
3. Нажмите Пуск -> Все программы -> Windows Clean Up Utility -> Remove Zune and languange packs
4. Снова попробуйте установить последнюю версию программы Zune.
0
1
28.04.2012, 10:18
у меня точно такая же проблема!!!!!! Помогите пожалуйста!!!!!!!!!!
1
0
02.05.2012, 09:30
Ирина, я выше написал, что можно сделать, попробуйте воспользоваться моими советами, возможно, они вам помогут, если нет, то пишите, будем вместе разбираться.
0
0
16.06.2012, 19:44
спасибо вам огромное,очень помог совет))
0
0
15.08.2012, 14:46
А что делать если после того как установил эту программу WICU хотел выполнить пункт 3. Нажмите Пуск -> Все программы -> Windows Clean Up Utility -> Remove Zune and languange packs. Но там нет Remove Zune and languange packs. Что ещё можно сделать?
0
0
20.09.2012, 09:22
дайте лучше архив с установленной zune
3
1
16.02.2013, 13:47
не могу понять что делать если в списке программ нету Zune and languange packs.Помогите!
0
0
22.04.2013, 16:59
у меня не устанавливает вот чё пишет Установщик Windows®. Версия 5.0.7601.17514
msiexec /Option <обязательный параметр> [необязательный параметр]
Параметры установки
</package | /i> <Product.msi>
Установка или настройка продукта
/a <Product.msi>
Административная установка — установка продукта в сеть
/j<u|m> <Product.msi> [/t <список преобразований>] [/g <код языка>]
Объявление о продукте: «m» — всем пользователям; «u» — текущему пользователю
</uninstall | /x> <Product.msi | Код_продукта>
Удаление продукта
Параметры отображения
/quiet
Тихий режим, без взаимодействия с пользователем
/passive
Автоматический режим — только указатель хода выполнения
/q[n|b|r|f]
Выбор уровня интерфейса пользователя
n — Без интерфейса
b — Основной интерфейс
r — Сокращенный интерфейс
f — Полный интерфейс (по умолчанию)
/help
Вывод справки по использованию
Параметры перезапуска
/norestart
Не перезапускать после завершения установки
/promptrestart
Запрашивать перезапуск при необходимости
/forcerestart
Всегда перезапускать компьютер после завершения установки
Параметры ведения журнала
/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <файл_журнала>
i — сообщения о состоянии
w — сообщения об устранимых ошибках
e — все сообщения об ошибках
a — запуски действий
r — записи, специфические для действий
u — запросы пользователя
c — начальные параметры интерфейса пользователя
m — сведения о выходе из-за недостатка памяти или неустранимой ошибки
o — сообщения о недостатке места на диске
p — свойства терминала
v — подробный вывод
x — дополнительные отладочные сведения
+ — добавление в существующий файл журнала
! — сбрасывание каждой строки в журнал
* — заносить в журнал все сведения, кроме параметров «v» и «x»
/log <файл_журнала>
Равнозначен /l* <файл_журнала>
Параметры обновления
/update <Update1.msp>[;Update2.msp]
Применение обновлений
/uninstall <Код_Guid_обновления>[;Update2.msp] /package <Product.msi | код_продукта>
Удаление обновлений продукта
Параметры восстановления
/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | код_продукта>
Восстановление продукта
p — только при отсутствии файла
o — если файл отсутствует или установлена старая версия (по умолчанию)
e — если файл отсутствует или установлена такая же либо старая версия
d — если файл отсутствует или установлена другая версия
c — если файл отсутствует или контрольная сумма не совпадает с подсчитанным значением
a — принудительная переустановка всех файлов
u — все необходимые элементы реестра, специфические для пользователя (по умолчанию)
m — все необходимые элементы реестра, специфические для компьютера (по умолчанию)
s — все существующие ярлыки (по умолчанию)
v — запуск из источника с повторным кэшированием локальных пакетов
Настройка общих свойств
[PROPERTY=PropertyValue]
Обратитесь к руководству разработчиков установщика Windows® за дополнительными
сведениями по использованию командной строки.
© Корпорация Майкрософт. Все права защищены.
В некоторых частях программы использованы разработки Independent JPEG Group.
Hi,
I have a signed 64-bit non-PnP KMDF driver, build with WDK 7600.16385.1, that runs under Windows 7..10. For the driver installation, I use a console application (devinst.exe), down stripped from the MS devcon sample code.
The driver installation works without any problem till Windows 10 1803.
Since Windows 10 1809, the driver installation fails when devinst.exe calls UpdateDriverForPlugAndPlayDevicesW(). GetLastError return the error code 0xe0000203 ERROR_NO_DRIVER_SELECTED.
The devinst.exe call looks like:
devinst.exe -i C:MENErtcSmbDriversAMD6413bb0370_smbpci.inf rootMEN_SMBPCI_FCH_SMBUS
with is functional the same as the devon call:
devcon.exe install C:MENErtcSmbDriversAMD6413bb0370_smbpci.inf rootMEN_SMBPCI_FCH_SMBUS
devcon.exe from the WDK for Windows 10, version 1809, produces the same error code as devinst.exe at the UpdateDriverForPlugAndPlayDevicesW() function call.
When I install the driver under 1803 and upgrade then to 1809, the driver works fine. So the problem is «only» the installation under 1809.
I compared the setupapi.dev.txt log file from 1803 with 1809. The logs are identical until:
[1803]
sto: {Setup Import Driver Package - exit (0x00000000)} 16:37:05.751 dvi: Searching for hardware ID(s): dvi: rootmen_smbpci_fch_smbus dvi: Class GUID of device remains: {3d9f85af-e5e4-4b14-aab9-c01473275b9b}. dvi: {Plug and Play Service: Device Install for ROOTMEN13BB0370_SMBPCI+INF&ROOT-MEN_SMBPCI_FCH_SMBUS}
...
[1809]
sto: {Setup Import Driver Package - exit (0x00000000)} 14:17:32.202
dvi: Searching for hardware ID(s):
dvi: rootmen_smbpci_fch_smbus
ndv: {Update Device Driver - exit(e0000203)}
!!! ndv: Failed to install device instance 'ROOTMEN13BB0370_SMBPCI+INF&ROOT-MEN_SMBPCI_FCH_SMBUS'. Error = 0xe0000203
dvi: {DIF_DESTROYPRIVATEDATA} 14:17:32.258
dvi: Class installer: Enter 14:17:32.266
dvi: Class installer: Exit
dvi: Default installer: Enter 14:17:32.280
dvi: Default installer: Exit
dvi: {DIF_DESTROYPRIVATEDATA - exit(0xe000020e)} 14:17:32.294
<<< Section end 2019/01/11 14:17:32.300
<<< [Exit status: FAILURE(0xe0000203)]
Have you any idea what can cause the error code 0xe0000203 ERROR_NO_DRIVER_SELECTED from UpdateDriverForPlugAndPlayDevices until Windows 10 1809?
Regards,
Dieter
Dieter
The options I’ve shown are really the only lines you need to add, don’t overthink it and just test it with curl —interface to verify the public IP.
That is because this ‘error message’ in particular tells you that OpenVPN is correctly ignoring the networking routes pushed to us by the server (this is ‘route-nopull’). In short: this is what it must show. Really, it’s correct.
Though for completeness’ sake, this is my complete log (redacted in a few places) and the config (auto-generated by AirVPN configurator + no-pull lines added).
client
dev tun
remote <AIRVPN SERVER IP> 1194
resolv-retry infinite
nobind
persist-key
persist-tun
auth-nocache
verb 3
explicit-exit-notify 5
rcvbuf 262144
sndbuf 262144
push-peer-info
setenv UV_IPV6 yes
remote-cert-tls server
comp-lzo no
data-ciphers AES-256-GCM:AES-256-CBC:AES-192-GCM:AES-192-CBC:AES-128-GCM:AES-128-CBC
data-ciphers-fallback AES-256-CBC
proto udp
key-direction 1
# NOPULL START
route-nopull
# «default»/»vpn_gateway»/»remote_host»/»net_gateway» are allowed placeholders. Since ipv6 has no other special words, use pushed «default»
# I SPECIFIED MY ROUTER IP EXPLICITLY: 192.168.69.1
# IF YOU DO NOT USE ANOTHER VPN THAT TAKES OVER ALL YOUR TRAFFIC, USE net_gateway
# net_gateway WILL BE AUTOMATICALLY DETERMINED AND WILL WORK IF YOU CONNECT THROUGH OTHER NETWORKS
# LIKE A PUBLIC WIFI
route remote_host 255.255.255.255 192.168.69.1
route 10.0.0.0 255.0.0.0 vpn_gateway
route 0.0.0.0 0.0.0.0 default 666
route-ipv6 ::/0 default 666
dev-node AirVPN-TAP
# MY OWN CUSTOM OPTION
link-mtu 1452
# END OF NOPULL
# THERE MAY FOLLOW THE BUNDLED CERTIFICATE FOR YOU
2021-02-27 10:25:21 OpenVPN 2.5.0 <openvpn_verson> [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on …
2021-02-27 10:25:21 Windows version 6.1 (Windows 7) 64bit
2021-02-27 10:25:21 library versions: OpenSSL 1.1.1h …, LZO 2.10
Enter Management Password:
2021-02-27 10:25:21 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25349
2021-02-27 10:25:21 Need hold release from management interface, waiting…
2021-02-27 10:25:21 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25349
2021-02-27 10:25:21 MANAGEMENT: CMD ‘state on’
2021-02-27 10:25:21 MANAGEMENT: CMD ‘log all on’
2021-02-27 10:25:21 MANAGEMENT: CMD ‘echo all on’
2021-02-27 10:25:21 MANAGEMENT: CMD ‘bytecount 5’
2021-02-27 10:25:21 MANAGEMENT: CMD ‘hold off’
2021-02-27 10:25:21 MANAGEMENT: CMD ‘hold release’
2021-02-27 10:25:21 Outgoing Control Channel Authentication: Using 160 bit message hash ‘SHA1’ for HMAC authentication
2021-02-27 10:25:21 Incoming Control Channel Authentication: Using 160 bit message hash ‘SHA1’ for HMAC authentication
== OPENVPN COMPLAINS DUE TO MY CUSTOM MTU OPTION, AIRVPN PUSHES/USES BAD MTU FOR ME
2021-02-27 10:25:21 WARNING: normally if you use —mssfix and/or —fragment, you should also set —tun-mtu 1500 (currently it is 1330)
2021-02-27 10:25:21 TCP/UDP: Preserving recently used remote address: [AF_INET]<Public AirVPN Server Address IPv4>:1194
2021-02-27 10:25:21 Socket Buffers: R=[8192->262144] S=[8192->262144]
2021-02-27 10:25:21 UDP link local: (not bound)
2021-02-27 10:25:21 UDP link remote: [AF_INET]<Public AirVPN Server Address IPv4>:1194
2021-02-27 10:25:21 MANAGEMENT: >STATE:1616667921,WAIT,,,,,,
2021-02-27 10:25:21 MANAGEMENT: >STATE:1616667921,AUTH,,,,,,
2021-02-27 10:25:21 TLS: Initial packet from [AF_INET]<Public AirVPN Server Address IPv4>:1194, sid=00cc3139 c640d892
2021-02-27 10:25:21 VERIFY KU OK
2021-02-27 10:25:21 Validating certificate extended key usage
2021-02-27 10:25:21 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
2021-02-27 10:25:21 VERIFY EKU OK
2021-02-27 10:25:21 VERIFY OK: depth=0, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=<AirVPN’s Server Certificate Name>, emailAddress=info@airvpn.org
== OPENVPN COMPLAINS DUE TO MY CUSTOM MTU OPTION, AIRVPN PUSHES/USES BAD MTU FOR ME
2021-02-27 10:25:22 WARNING: ‘link-mtu’ is used inconsistently, local=’link-mtu 1452′, remote=’link-mtu 1558′
2021-02-27 10:25:22 WARNING: ‘tun-mtu’ is used inconsistently, local=’tun-mtu 1330′, remote=’tun-mtu 1500′
2021-02-27 10:25:22 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_CHACHA20_POLY1305_SHA256, 4096 bit RSA
2021-02-27 10:25:22 [<AirVPN’s Server Name>] Peer Connection Initiated with [AF_INET]<Public AirVPN Server Address IPv4>:1194
== WHAT SERVER PUSHES TO US
2021-02-27 10:25:22 PUSH: Received control message: ‘PUSH_REPLY,comp-lzo no,redirect-gateway ipv6 def1 bypass-dhcp,dhcp-option DNS 10.26.124.1,tun-ipv6,route-gateway 10.26.124.1,topology subnet,ping 10,ping-restart 60,ifconfig-ipv6 fde6:7a:ZZZZ:XXXX::YYYY/64 fde6:7a:7d20:167c::1,ifconfig 10.26.124.XXX 255.255.255.0,peer-id 0,cipher AES-256-GCM’
== WHAT IS IGNORED DUE TO ROUTE-NOPULL (I.E. ROUTES AND DNS). IT SHOWS UP AS WARNINGS/ERRORS, BUT THIS IS CORRECT
2021-02-27 10:25:22 Options error: option ‘redirect-gateway’ cannot be used in this context ([PUSH-OPTIONS])
2021-02-27 10:25:22 Options error: option ‘dhcp-option’ cannot be used in this context ([PUSH-OPTIONS])
2021-02-27 10:25:22 OPTIONS IMPORT: timers and/or timeouts modified
2021-02-27 10:25:22 OPTIONS IMPORT: compression parms modified
2021-02-27 10:25:22 OPTIONS IMPORT: —ifconfig/up options modified
2021-02-27 10:25:22 OPTIONS IMPORT: route-related options modified
2021-02-27 10:25:22 OPTIONS IMPORT: peer-id set
== MY CUSTOM MTU IS ACTUALLY CORRECT, THANKS BUT NO THANKS
2021-02-27 10:25:22 OPTIONS IMPORT: WARNING: peer-id set, but link-mtu fixed by config — reducing tun-mtu to 1327, expect MTU problems
2021-02-27 10:25:22 OPTIONS IMPORT: data channel crypto options modified
2021-02-27 10:25:22 Data Channel: using negotiated cipher ‘AES-256-GCM’
2021-02-27 10:25:22 Outgoing Data Channel: Cipher ‘AES-256-GCM’ initialized with 256 bit key
2021-02-27 10:25:22 Incoming Data Channel: Cipher ‘AES-256-GCM’ initialized with 256 bit key
2021-02-27 10:25:22 interactive service msg_channel=356
== THIS SHOWS WHAT OPENVPN CONSIDERS YOUR DEFAULT GATEWAY (ROUTER) TO THE INTERNET
== IF YOU DON’T USE ANOTHER VPN SIMULANEOUSLY, USE net_gateway AND IT WILL BE AUTO-SELECTED
== IF YOU DO USE ANOTHER VPN, SPECIFY YOUR ROUTER IP MANUALLY AS PER GUIDE TO NOT ROUTE AIRVPN THROUGH ANOTHER VPN
2021-02-27 10:25:22 ROUTE_GATEWAY <default net_gateway as detected by OpenVPN aka your router>/255.255.255.0 I=19 HWADDR=00:11:22:33:44:55
2021-02-27 10:25:22 GDG6: remote_host_ipv6=n/a
2021-02-27 10:25:22 GetBestInterfaceEx() returned if=19
2021-02-27 10:25:22 GDG6: II=19 DP=::/3 NH=fe80::8
2021-02-27 10:25:22 GDG6: Metric=256, Loopback=0, AA=1, I=0
2021-02-27 10:25:22 ROUTE6_GATEWAY fe80::8 I=19
2021-02-27 10:25:22 open_tun
2021-02-27 10:25:22 tap-windows6 device [AirVPN-TAP] opened
2021-02-27 10:25:22 TAP-Windows Driver Version 9.24
2021-02-27 10:25:22 Set TAP-Windows TUN subnet mode network/local/netmask = 10.26.124.0/10.26.124.XXX/255.255.255.0 [SUCCEEDED]
2021-02-27 10:25:22 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.26.124.XXX/255.255.255.0 on interface {12345678-90AB-CDEF-1234-133769001234} [DHCP-serv: 10.26.124.254, lease-time: 31536000]
2021-02-27 10:25:22 Successful ARP Flush on interface [34] {12345678-90AB-CDEF-1234-133769001234}
2021-02-27 10:25:22 MANAGEMENT: >STATE:1616667922,ASSIGN_IP,,10.26.124.XXX,,,,,fde6:7a:ZZZZ:XXXX::YYYY
2021-02-27 10:25:22 IPv4 MTU set to 1399 on interface 34 using service
2021-02-27 10:25:22 INET6 address service: add fde6:7a:ZZZZ:XXXX::YYYY/128
2021-02-27 10:25:22 add_route_ipv6(fde6:7a:7d20:167c::/64 -> fde6:7a:ZZZZ:XXXX::YYYY metric 0) dev AirVPN-TAP
2021-02-27 10:25:22 IPv6 route addition via service succeeded
2021-02-27 10:25:22 IPv6 MTU set to 1399 on interface 34 using service
2021-02-27 10:25:28 TEST ROUTES: 3/3 succeeded len=3 ret=1 a=0 u/d=up
2021-02-27 10:25:28 MANAGEMENT: >STATE:1616667928,ADD_ROUTES,,,,,,
== EXPLICITLY ROUTE AIRVPN THROUGH ROUTER
2021-02-27 10:25:28 C:Windowssystem32route.exe ADD <Public AirVPN Server Address IPv4> MASK 255.255.255.255 192.168.69.1
2021-02-27 10:25:28 Route addition via service succeeded
== EXPLICITLY ROUTE 10.0.0.0-10.0.0.255 THROUGH VPN (THE MASK HERE IS WRONG, I HAD IT CORRECTED IN THE GUIDE)
2021-02-27 10:25:28 C:Windowssystem32route.exe ADD 10.0.0.0 MASK 255.255.255.0 10.26.124.1
2021-02-27 10:25:28 Route addition via service succeeded
== ANY IPv4 TRAFFIC IS ALLOWED THROUGH AIRVPN, BUT ONLY AS LAST CHOICE DUE TO METRIC
2021-02-27 10:25:28 C:Windowssystem32route.exe ADD 0.0.0.0 MASK 0.0.0.0 10.26.124.1 METRIC 666
2021-02-27 10:25:28 Route addition via service succeeded
== ANY IPv6 TRAFFIC IS ALLOWED THROUGH AIRVPN, BUT ONLY AS LAST CHOICE DUE TO METRIC
2021-02-27 10:25:28 add_route_ipv6(::/0 -> fde6:7a:7d20:167c::1 metric 666) dev AirVPN-TAP
2021-02-27 10:25:28 IPv6 route addition via service succeeded
2021-02-27 10:25:28 Initialization Sequence Completed
2021-02-27 10:25:28 MANAGEMENT: >STATE:1616667928,CONNECTED,SUCCESS,10.26.124.XXX,<Public AirVPN Server Address IPv4>,1194,,,fde6:7a:ZZZZ:XXXX::YYYY
2021-02-27 10:28:20 [<AirVPN’s Server Name>] Inactivity timeout (—ping-restart), restarting
2021-02-27 10:28:20 SIGUSR1[soft,ping-restart] received, process restarting
2021-02-27 10:28:20 MANAGEMENT: >STATE:1616668100,RECONNECTING,ping-restart,,,,,
2021-02-27 10:28:20 Restart pause, 5 second(s)
== THIS IS WHERE THE PREVIOUS TUNNEL TIMES OUT BY OPENVPN (DUE TO INCORRECT INTERNAL IP) AND A RECONNECT IS INITIATED
== AFTER THE RECONNECT I DO GET FULL CONNECTIVITY
== I DO NOT KNOW IF THIS IS A BUG WITH MY OS+SOFTWARE OR A PECULIARITY OF THIS CONFIGURATION, BUT THIS IS NOT NORMAL.
== BASICALLY, GIVE IT 1-3 MINUTES TO CONNECT NORMALLY. ANY SOFTWARE THAT YOU HAVE BOUND TO ONLY USE THIS INTERFACE IS OK
== AND CAN BE STARTED EARLIER (NO CONNECTION LEAKING) BUT THAT SOFTWARE WILL HAVE TO RESTART CONNECTIONS AUTOMATICALLY
== TO CONNECT SUCCESSFULLY ONCE THE FULL VPN LINK HAS BEEN ESTABLISHED
== PREVIOUSLY NOT WORKING INTERNAL IP: 10.26.124.XXX
== CORRECTLY WORKING INTERNAL IP AFTER AUTO-RECONNECT: 10.26.124.CCC
2021-02-27 10:28:25 Outgoing Control Channel Authentication: Using 160 bit message hash ‘SHA1’ for HMAC authentication
2021-02-27 10:28:25 Incoming Control Channel Authentication: Using 160 bit message hash ‘SHA1’ for HMAC authentication
2021-02-27 10:28:25 WARNING: normally if you use —mssfix and/or —fragment, you should also set —tun-mtu 1500 (currently it is 1330)
2021-02-27 10:28:25 TCP/UDP: Preserving recently used remote address: [AF_INET]<Public AirVPN Server Address IPv4>:1194
2021-02-27 10:28:25 Socket Buffers: R=[8192->262144] S=[8192->262144]
2021-02-27 10:28:25 UDP link local: (not bound)
2021-02-27 10:28:25 UDP link remote: [AF_INET]<Public AirVPN Server Address IPv4>:1194
2021-02-27 10:28:25 MANAGEMENT: >STATE:1616668105,WAIT,,,,,,
2021-02-27 10:28:25 MANAGEMENT: >STATE:1616668105,AUTH,,,,,,
2021-02-27 10:28:25 TLS: Initial packet from [AF_INET]<Public AirVPN Server Address IPv4>:1194, sid=42c04644 3263e3c6
2021-02-27 10:28:25 VERIFY KU OK
2021-02-27 10:28:25 Validating certificate extended key usage
2021-02-27 10:28:25 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
2021-02-27 10:28:25 VERIFY EKU OK
2021-02-27 10:28:25 VERIFY OK: depth=0, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=<AirVPN’s Server Name>, emailAddress=info@airvpn.org
2021-02-27 10:28:25 WARNING: ‘link-mtu’ is used inconsistently, local=’link-mtu 1452′, remote=’link-mtu 1558′
2021-02-27 10:28:25 WARNING: ‘tun-mtu’ is used inconsistently, local=’tun-mtu 1330′, remote=’tun-mtu 1500′
2021-02-27 10:28:25 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_CHACHA20_POLY1305_SHA256, 4096 bit RSA
2021-02-27 10:28:25 [<AirVPN’s Server Name>] Peer Connection Initiated with [AF_INET]<Public AirVPN Server Address IPv4>:1194
2021-02-27 10:28:25 PUSH: Received control message: ‘PUSH_REPLY,comp-lzo no,redirect-gateway ipv6 def1 bypass-dhcp,dhcp-option DNS 10.26.112.1,tun-ipv6,route-gateway 10.26.112.1,topology subnet,ping 10,ping-restart 60,ifconfig-ipv6 fde6:7a:ZZZZ:XXXX::YYYY/64 fde6:7a:7d20:1670::1,ifconfig 10.26.112.CCC 255.255.255.0,peer-id 1,cipher AES-256-GCM’
2021-02-27 10:28:25 Options error: option ‘redirect-gateway’ cannot be used in this context ([PUSH-OPTIONS])
2021-02-27 10:28:25 Options error: option ‘dhcp-option’ cannot be used in this context ([PUSH-OPTIONS])
2021-02-27 10:28:25 OPTIONS IMPORT: timers and/or timeouts modified
2021-02-27 10:28:25 OPTIONS IMPORT: compression parms modified
2021-02-27 10:28:25 OPTIONS IMPORT: —ifconfig/up options modified
2021-02-27 10:28:25 OPTIONS IMPORT: route-related options modified
2021-02-27 10:28:25 OPTIONS IMPORT: peer-id set
2021-02-27 10:28:25 OPTIONS IMPORT: WARNING: peer-id set, but link-mtu fixed by config — reducing tun-mtu to 1327, expect MTU problems
2021-02-27 10:28:25 OPTIONS IMPORT: data channel crypto options modified
2021-02-27 10:28:25 Data Channel: using negotiated cipher ‘AES-256-GCM’
2021-02-27 10:28:25 Outgoing Data Channel: Cipher ‘AES-256-GCM’ initialized with 256 bit key
2021-02-27 10:28:25 Incoming Data Channel: Cipher ‘AES-256-GCM’ initialized with 256 bit key
2021-02-27 10:28:25 Preserving previous TUN/TAP instance: AirVPN-TAP
2021-02-27 10:28:25 NOTE: Pulled options changed on restart, will need to close and reopen TUN/TAP device.
2021-02-27 10:28:25 C:Windowssystem32route.exe DELETE <Public AirVPN Server Address IPv4> MASK 255.255.255.255 192.168.69.1
2021-02-27 10:28:25 Route deletion via service succeeded
2021-02-27 10:28:25 C:Windowssystem32route.exe DELETE 10.0.0.0 MASK 255.255.255.0 10.26.124.1
2021-02-27 10:28:25 Route deletion via service succeeded
2021-02-27 10:28:25 C:Windowssystem32route.exe DELETE 0.0.0.0 MASK 0.0.0.0 10.26.124.1
2021-02-27 10:28:25 Route deletion via service succeeded
2021-02-27 10:28:25 delete_route_ipv6(::/0)
2021-02-27 10:28:25 IPv6 route deletion via service succeeded
2021-02-27 10:28:25 Closing TUN/TAP interface
2021-02-27 10:28:25 delete_route_ipv6(fde6:7a:7d20:167c::/64)
2021-02-27 10:28:25 IPv6 route deletion via service succeeded
2021-02-27 10:28:25 INET6 address service: remove fde6:7a:ZZZZ:XXXX::YYYY/128
2021-02-27 10:28:25 TAP: DHCP address released
2021-02-27 10:28:26 interactive service msg_channel=356
2021-02-27 10:28:26 ROUTE_GATEWAY <default net_gateway as detected by OpenVPN aka your router>/255.255.255.0 I=19 HWADDR=00:11:22:33:44:55
2021-02-27 10:28:26 GDG6: remote_host_ipv6=n/a
2021-02-27 10:28:26 GetBestInterfaceEx() returned if=19
2021-02-27 10:28:26 GDG6: II=19 DP=::/3 NH=fe80::8
2021-02-27 10:28:26 GDG6: Metric=256, Loopback=0, AA=1, I=0
2021-02-27 10:28:26 ROUTE6_GATEWAY fe80::8 I=19
2021-02-27 10:28:26 open_tun
2021-02-27 10:28:26 tap-windows6 device [AirVPN-TAP] opened
2021-02-27 10:28:26 TAP-Windows Driver Version 9.24
2021-02-27 10:28:26 Set TAP-Windows TUN subnet mode network/local/netmask = 10.26.112.0/10.26.112.CCC/255.255.255.0 [SUCCEEDED]
2021-02-27 10:28:26 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.26.112.CCC/255.255.255.0 on interface {12345678-90AB-CDEF-1234-133769001234} [DHCP-serv: 10.26.112.254, lease-time: 31536000]
2021-02-27 10:28:26 Successful ARP Flush on interface [34] {12345678-90AB-CDEF-1234-133769001234}
2021-02-27 10:28:26 MANAGEMENT: >STATE:1616668106,ASSIGN_IP,,10.26.112.CCC,,,,,fde6:7a:ZZZZ:XXXX::YYYY
2021-02-27 10:28:26 IPv4 MTU set to 1399 on interface 34 using service
2021-02-27 10:28:26 INET6 address service: add fde6:7a:ZZZZ:XXXX::YYYY/128
2021-02-27 10:28:26 add_route_ipv6(fde6:7a:7d20:1670::/64 -> fde6:7a:ZZZZ:XXXX::YYYY metric 0) dev AirVPN-TAP
2021-02-27 10:28:26 IPv6 route addition via service succeeded
2021-02-27 10:28:26 IPv6 MTU set to 1399 on interface 34 using service
2021-02-27 10:28:31 TEST ROUTES: 3/3 succeeded len=3 ret=1 a=0 u/d=up
2021-02-27 10:28:31 MANAGEMENT: >STATE:1616668111,ADD_ROUTES,,,,,,
2021-02-27 10:28:31 C:Windowssystem32route.exe ADD <Public AirVPN Server Address IPv4> MASK 255.255.255.255 192.168.69.1
2021-02-27 10:28:31 Route addition via service succeeded
2021-02-27 10:28:31 C:Windowssystem32route.exe ADD 10.0.0.0 MASK 255.255.255.0 10.26.112.1
2021-02-27 10:28:31 Route addition via service succeeded
2021-02-27 10:28:31 C:Windowssystem32route.exe ADD 0.0.0.0 MASK 0.0.0.0 10.26.112.1 METRIC 666
2021-02-27 10:28:31 Route addition via service succeeded
2021-02-27 10:28:31 add_route_ipv6(::/0 -> fde6:7a:7d20:1670::1 metric 666) dev AirVPN-TAP
2021-02-27 10:28:31 IPv6 route addition via service succeeded
2021-02-27 10:28:31 Initialization Sequence Completed
2021-02-27 10:28:31 MANAGEMENT: >STATE:1616668111,CONNECTED,SUCCESS,10.26.112.CCC,<Public AirVPN Server Address IPv4>,1194,,,fde6:7a:ZZZZ:XXXX::YYYY
Edited … by guidance