Opened 4 years ago

Closed 4 years ago

#766 closed Bug / Defect (notabug)

GUI says no TAP-Win adapters; log not saved; subsequently connects OK

Reported by: Norman Henderson Owned by:
Priority: major Milestone:
Component: Windows GUI Version: OpenVPN 2.3.12 (Community Ed)
Severity: Not set (select this one, unless your'e a OpenVPN developer) Keywords: TAP-Windows, greyed
Cc: Samuli Seppänen

Description

I have been using OpenVPN for years but just bought a new laptop. Installation from openvpn-install-2.3.12-I602-x86_64.exe seemed to go OK.
On both PC’s my user account has admin privileges.

  • When I try to “connect” it pops up “connecting to cem05w01 has failed” and the log display behind it says “all TAP-Windows adapters on this system are currently in use”. Time 05:52:38.
  • None of the contents of that log display are written to the file. When I open the log file, I get completely different entries starting with “Connection reset, restarting [0]” at 05:52:36 (!!!) and ending some seconds later with “Initialization Sequence Completed.”
  • Indeed, the tunnel is up and working, and an appropriate TAP-Windows adapter shows in ipconfig.
  • The GUI remains greyed out and offering the “connect” option; this means there is no clean way to disconnect.

This does not change with reboot etc.

Attachments (2)

OpenVPN-cem05w01.jpg (188.3 KB) - added by Norman Henderson 4 years ago.
GUI with pop-up error
OpenVPN-cem05w01.log (5.7 KB) - added by Norman Henderson 4 years ago.
Log file with successful connect

Download all attachments as: .zip

Change History (8)

Changed 4 years ago by Norman Henderson

Attachment: OpenVPN-cem05w01.jpg added

GUI with pop-up error

Changed 4 years ago by Norman Henderson

Attachment: OpenVPN-cem05w01.log added

Log file with successful connect

comment:1 Changed 4 years ago by Gert Döring

Cc: Samuli Seppänen added
Version: 2.3.12

I assume this is Windows10... from 8.1 onwards, we've had occasional reports about the tap driver not being willing to get installed - and retrying after a reboot usually fixed things.

You might want to try 2.3.13, as it has a few fixes to 2.3.12 (but none that are really related to windows or tap), but just "if you do a reinstall, why install an old version" :-)

comment:2 Changed 4 years ago by Norman Henderson

Sorry should have specified: Win 7 Pro SP1.
Reboots didn't help.
I have another system running Win 10 and OpenVPN 2.3.7 which works correctly!
2.3.12 was current when this issue started but I will try 2.3.13 now - full uninstall/reinstall. Could have been some anomaly I didn't notice.

comment:3 Changed 4 years ago by Norman Henderson

SO... uninstall 2.3.12 / install 2.3.13 fixed it. Probably just something went wrong in the original install.

comment:4 Changed 4 years ago by Samuli Seppänen

Ok, so I take it this ticket can then be closed?

comment:5 Changed 4 years ago by Norman Henderson

Yes it can be closed. Sorry for adding to the noise level.

comment:6 Changed 4 years ago by Gert Döring

Resolution: notabug
Status: newclosed

Thanks for re-testing. Sometimes windows stuff is just plain weird... :-(

Note: See TracTickets for help on using tickets.