Openvpn error 536870397

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

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 that

installing 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 :idea: ! 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 :idea: ! 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.


Содержание

  1. OpenVPN Support Forum
  2. Error during installation of windows client OpenVPN 2.5.0 amd64 OpenVPNMSICA tap_create_adapter Error 536870397 solution
  3. Error during installation of windows client OpenVPN 2.5.0 amd64 OpenVPNMSICA tap_create_adapter Error 536870397 solution
  4. OpenVPN Support Forum
  5. Error during installation of windows client OpenVPN 2.5.0 amd64 OpenVPNMSICA tap_create_adapter Error 536870397 solution
  6. Error during installation of windows client OpenVPN 2.5.0 amd64 OpenVPNMSICA tap_create_adapter Error 536870397 solution
  7. OpenVPN Support Forum
  8. Can’t install OpenVpn
  9. Can’t install OpenVpn
  10. Re: Can’t install OpenVpn
  11. Re: Can’t install OpenVpn
  12. tap_create_adapter: DinstallDevice failed error about openvpn-build HOT 3 OPEN
  13. Comments (3)
  14. Related Issues (20)
  15. Recommend Projects
  16. React
  17. Vue.js
  18. Typescript
  19. TensorFlow
  20. Django
  21. Laravel
  22. Recommend Topics
  23. javascript
  24. server
  25. Machine learning
  26. Visualization
  27. Recommend Org
  28. Facebook
  29. Microsoft
  30. Почему не устанавливается драйвер для penvpn(tap-windows)?

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.

Источник

Recommend Projects

  • React photo

    React

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

  • Vue.js photo

    Vue.js

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

  • Typescript photo

    Typescript

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

  • TensorFlow photo

    TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo

    Django

    The Web framework for perfectionists with deadlines.

  • Laravel photo

    Laravel

    A PHP framework for web artisans

  • D3 photo

    D3

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

Recommend Topics

  • javascript

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

  • web

    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

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo

    Facebook

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

  • Microsoft photo

    Microsoft

    Open source projects and samples from Microsoft.

  • Google photo

    Google

    Google ❤️ Open Source for everyone.

  • Alibaba photo

    Alibaba

    Alibaba Open Source for everyone

  • D3 photo

    D3

    Data-Driven Documents codes.

  • Tencent photo

    Tencent

    China tencent open source team.

Entretoize

Hello, I created a samba folder share on a linux server, and installer openvpn server on the same server.
The share is limited to local ip so I can only acces it though a vpn.

I tested with the android openvpn client and it work perfectly which means the server configuration is ok, but on windows the acces is rejected and on my server log I see the computer IP instead of the vpn one. As I checked in a browser that the server IP replaces my computer one when I access whatismyipaddress.com for example, I understand that OpenVPN GUI is working for HTTP but not for SMB.

Is it true or is there a setting I can change somewhere ? Is it a bug ?

Thanks

mcrite

I get this same error over and over again when trying to connect with multiple profiles. Any assistance would be great.

2020-11-13 16:05:38 OPTIONS ERROR: failed to negotiate cipher with server. Configure —data-ciphers-fallback if you want to connect to this server.
2020-11-13 16:05:38 ERROR: Failed to apply push options
2020-11-13 16:05:38 Failed to open tun/tap interface
2020-11-13 16:05:38 SIGUSR1[soft,process-push-msg-failed] received, process restarting
2020-11-13 16:05:38 Restart pause, 5 second(s)

matthewjameslord

yvan3869

Hello, as my title says, I set up an auto-config and everything just worked fine when I log out ; I saw the ovbn button on the logon screen, and then vpn connection was ok, before connection to my domain, and after in session mode.

But when I reboot my Dell, Windows stuck at startup. So I had to remove the config files in safe mode to be able to go back in my system….bye bye Pre logon access…

Anyone having an idea? I’m using OpenVPN 2.6 with Windows 10 22H2 (19045.2546)

thanks

torerobo

I imported a lot of profiles.ovpn Then I deleted them from the folder, but they all remained in the GUI. And it has grown. Openvpn gui does not have a delete profile button.

How to get rid of unnecessary profiles in gui at the moment?

Gulaschcowboy

Yesterday we pushed OpenVPN-2.6.0-I003-amd64 to our Dell Laptops with Windows 10, various builds.

On some of them an error message pops up during start of the OpenVPN-Gui.
«Error creating semaphore»:

grafik

It doesn’t seem to have an impact, and we couldn’t figure out yet, why some Laptops are affected and some not.

Downgrading to 2.5.8 doesn’t help, the error persists after downgrade.

Any hints?

EmmettF17

изображение
Windows server 22

chipitsine

we observe the following pattern in user behaviour: when they setup new PC, sometimes they forgot to press TAB to switch to «password» prompt and type password right after the login, i.e. userpassword.

thus, password itself is empty, and sent as empty.

I’m not sure whether empty password is legitimate, maybe we should change OpenVPN-GUI behaviour to disallow empty passwords ?

I’d suggest to make «password» field red if OK is pressed on empty password. Thus we even do not have to translate it.

@selvanair , what do you think ?

jdrch

Noticed the above behavior just now. If you right-click the system tray icon and then click Connect (when currently disconnected) or Disconnect (when current connected) nothing happens. The workaround is to double-click the icon to raise the main window and then use the Connect and Disconnect buttons there.

lstipakov

Steps to reproduce:

  • have a single VPN profile
  • click on tray icon -> Connect

Expected results:

  • connection starts

Actual results:

  • nothing happens

Same goes with «disconnect». However, if you open status window after connect attempt, it starts to connect. See the screencast.

Problem doesn’t reproduce with more than one VPN profile.

gui_bug

EmmettF17

  • OS: [Windows Server 22 and Windows 10/11]
  • OpenVPN version: [2.5.5 — 2.6_rc18]

There’s a problem that I’ve been seeing for over a year now, and I’m not the only one. I have a program to work with that uses.ovpn configs to change my IP. Every 10 minutes it is automatically disconnected from the previous config connects to a new random one which are found by the path C:Program FilesOpenVPNconfig Approximately after ~150 such reconnected OpenVPN stops working. A lot of yellow icons appear in the tray and if you swipe the mouse pointer over them, they will simply disappear. If you restart the OpenVPN GUI it will appear in the tray with the usual white icon. but if you try to connect to the config, the icon immediately disappears and the connection does not occur. Only rebooting the PC/Server helps, after which everything works without problems

2.6_rc18:
photo_2023-01-05_23-35-41

2.5.5: Accompanied by such a notification when the OpenVPN GUI was restarted — «OpenVPNServiceInteractive» is not started. Wintun driver will not work.
photo_2022-04-24_22-55-37

Also, around the same time, the clipboard stops working, and strange artifacts appear in the «Windows Explorer path.»
P.S. But this is a «Windows» problem (with an RDP connection), it periodically occurs without OpenVPN installed. Maybe these problems are interrelated?!
photo_2022-04-22_15-08-25

please help solve this problem!

kbdavis07

Keep getting this Error when connecting:

ROUTE: route addition failed using CreateIpForwardEntry: The parameter is incorrect. [status=87 if_index=6]

Full Error Log:

Tue Dec 03 17:40:47 2019 OpenVPN 2.4.8 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Oct 31 2019
Tue Dec 03 17:40:47 2019 Windows version 6.2 (Windows 8 or greater) 64bit
Tue Dec 03 17:40:47 2019 library versions: OpenSSL 1.1.0l 10 Sep 2019, LZO 2.10
Enter Management Password:
Tue Dec 03 17:40:47 2019 WARNING: this configuration may cache passwords in memory — use the auth-nocache option to prevent this
Tue Dec 03 17:40:47 2019 SIGUSR1[soft,private-key-password-failure] received, process restarting
Tue Dec 03 17:41:06 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]52.32.119.134:1194
Tue Dec 03 17:41:06 2019 UDP link local: (not bound)
Tue Dec 03 17:41:06 2019 UDP link remote: [AF_INET]52.32.11x.xxx:1194
Tue Dec 03 17:41:07 2019 [vpn.jxxxxxxxx.com] Peer Connection Initiated with [AF_INET]52.32.11x.xxx:1194
Tue Dec 03 17:41:08 2019 open_tun
Tue Dec 03 17:41:08 2019 TAP-WIN32 device [Local Area Connection] opened: .Global{BB2C7112-5991-40A7-821A-BD3A3EA5FAA5}.tap
Tue Dec 03 17:41:08 2019 Notified TAP-Windows driver to set a DHCP IP/netmask of 192.168.245.6/255.255.255.252 on interface {BB2C7112-5991-40A7-821A-BD3A3EA5FAA5} [DHCP-serv: 192.168.245.5, lease-time: 31536000]
Tue Dec 03 17:41:08 2019 Successful ARP Flush on interface [6] {BB2C7112-5991-40A7-821A-BD3A3EA5FAA5}
Tue Dec 03 17:41:13 2019 Warning: address 10.1.0.0 is not a network address in relation to netmask 255.0.0.0
Tue Dec 03 17:41:13 2019 ROUTE: route addition failed using CreateIpForwardEntry: The parameter is incorrect. [status=87 if_index=6]
Tue Dec 03 17:41:13 2019 env_block: add PATH=C:WINDOWSSystem32;C:WINDOWS;C:WINDOWSSystem32Wbem
Tue Dec 03 17:41:13 2019 Initialization Sequence Completed

I Right Click and «Run as Admin» still have same issue.

This is an AWS Server with VPN Set up, trying to connect as a client from a Windows 10 Pro Desktop.

Mac users seems not to have any issue, just with Windows seems to be the issue.

xuroka

I have no idea what is going on, but OpenVPN stopped working properly a few days ago.
OpenVPN
Please help!

res0nance

ProxyGramm

Hello. Why OpenVPN want enter login and password ? although the username and password are registered in the config folder, and in all connections. I have to enter my username and password every connection and save it.
And when i do this save login and pass, when there is an automatic reconnection from one IP to another, it does not happen immediately, but counts down for 5 seconds, and only then switches. please help solve these problems.
https://ibb.co/YTPKNvh

kq01526

Hi,

apparently OpenVPN seems to be able to establish a VPN connection before a user logs on to Windows. Apparently this is being done by having OpenVPN running as a service:

https://openvpn.net/index.php/open-source/documentation/howto.html#startup

Establishing a VPN connection before logging on to Windows is especially useful when needing to log on to a domain joined machine (i.e. having to authenticate on a domain controller).

Is OpenVPN also able to offer a prompt for the VPN credentials before logging on to Windows?

Cisco AnyConnect does have that feature, it’s called «Start Before Logon» or in short «SBL», see for example:

https://youtu.be/dkwC5lXu-HQ

Windows itself also does offer a similar feature:

https://blog.lan-tech.ca/2012/04/29/connect-to-windows-vpn-at-logon/
https://blog.lan-tech.ca/2013/03/02/windows-8-connect-to-vpn-before-logon/

So, Windows does seem to have a «native» button for this on the log on screen (which is also being utilized by Cisco AnyConnect).

So, would it also be possible to have OpenVPN prompt for the VPN credentials when clicking on that button, so that a user can enter his VPN credentials (username + password) and connect via VPN before logging on to Windows?

Regards

selvanair

Openvpn.exe started by the GUI fails to terminate if the user tries to exit while a modal dialog is open. The GUI exits after timing out waiting for openvpn to terminate.

To reproduce
Start a connection using the GUI with --auth-user-pass in the config file. When the user-pass dialog pops up, move it aside, right click on the tray icon and press exit. A message box will popup, click yes to proceed with the exit process. The GUI will appear to stall for about 5 seconds and then exit. Open taskmgr and to see that «openvpn.exe» is left running.

Sometimes one has to try this a couple of times to reproduce, indicating some timing issue that causes the WM_OVPN_STOP message to get lost.

Happens only if the modal dialog is running on the UI thread (like user-pass or some other config-specific dialog). Dailogs like «import from url» that runs in the main thread does not cause this.

LordBaal87

When you start the open vpn gui without administrator priviliges (which is the default) creating the new routes / ip forward entries, fails, but the tray icon turns green, which is suggesting that everything is fine.
I suggest turning it to red when not beeing able to create routes.

(Version openvpn-install-2.3.9-I601-x86_64)

TinCanTech

Observation only — This could be expected behavior.
Windows 10 — Updated..

The GUI-Menu does not recognise currently running persistent connections after upgrading.

Here is a screenshot:
ovpn-gui-persist

The connection dan-auto is fully operational.

DamianFekete

Понравилась статья? Поделить с друзьями:

Читайте также:

  • Opensdk string error 521009
  • Openscmanager function call failed error ioperm sys installation failed
  • Openvpn dns resolve error
  • Openscmanager failed как исправить
  • Openvpn connection to management interface failed как исправить

  • 0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии