amnezia-vpn/amnezia-client

Fork 0

mirror of https://github.com/amnezia-vpn/amnezia-client.git synced 2026-10-14 21:34:26 +00:00

[GH-ISSUE #1874] The client removes Wintun adapter of OpenVPN 2.6.1 #805

New issue

Open

opened 2026-10-13 20:28:56 +00:00 by bsakaguchi · 5 comments

bsakaguchi commented

2026-10-13 20:28:56 +00:00

Owner

Originally created by @VladiStep on GitHub (Sep 21, 2025).
Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/1874

Describe the bug
I have OpenVPN 2.6.1 installed, and its OVPN config uses Wintun (dev tun).
When I connect to AmneziaVPN, it removes the "OpenVPN Wintun" ("Wintun Userspace Tunnel", which seems to use the same WireGuard driver) adapter.
And after disconnecting, I can't connect to OpenVPN anymore, it shows this error:
"All wintun adapters on this system are currently in use or disabled."

To Reproduce
Steps to reproduce the behavior:

Have OpenVPN 2.6.1 (or newer?) installed.
Connect to AmneziaVPN.
Disconnect.
Try to connect to OpenVPN with a config that uses Wintun.

Expected behavior
I think it should either create a separate adapter somehow, or re-create the removed one.

Log files
IDK where to find them.

Desktop:

OS: Windows 10 22H2
Version: 4.8.10.0

Originally created by @VladiStep on GitHub (Sep 21, 2025). Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/1874 **Describe the bug** I have OpenVPN 2.6.1 installed, and its OVPN config uses Wintun (`dev tun`). When I connect to AmneziaVPN, it removes the "OpenVPN Wintun" ("Wintun Userspace Tunnel", which seems to use the same WireGuard driver) adapter. And after disconnecting, I can't connect to OpenVPN anymore, it shows this error: "All wintun adapters on this system are currently in use or disabled." **To Reproduce** Steps to reproduce the behavior: 1. Have OpenVPN 2.6.1 (or newer?) installed. 2. Connect to AmneziaVPN. 3. Disconnect. 4. Try to connect to OpenVPN with a config that uses Wintun. **Expected behavior** I think it should either create a separate adapter somehow, or re-create the removed one. **Log files** IDK where to find them. **Desktop:** - OS: Windows 10 22H2 - Version: 4.8.10.0

bsakaguchi commented

2026-10-13 20:28:58 +00:00

Author

Owner

@dezgasting commented on GitHub (Nov 24, 2025):

Still relevant, but fixes itself via reinstalling openVPN, until you run Amnezia again anyway.

@dezgasting commented on GitHub (Nov 24, 2025): Still relevant, but fixes itself via reinstalling openVPN, until you run Amnezia again anyway.

bsakaguchi commented

2026-10-13 20:28:58 +00:00

Author

Owner

@Yabashiri commented on GitHub (Dec 3, 2025):

Same issue

@Yabashiri commented on GitHub (Dec 3, 2025): Same issue

bsakaguchi commented

2026-10-13 20:28:58 +00:00

Author

Owner

@BoDDEneR commented on GitHub (Apr 6, 2026):

Same issue. One fact does not give me peace - this issue started appearing after fresh windows install. On the old system I was able to use OpenVPN and Amnezia simultaneously.

I am too using OpenVPN to work, and work config has not changed for several years. I tried old Amnezia versions - no success. So what have suddenly changed? No idea.

@BoDDEneR commented on GitHub (Apr 6, 2026): Same issue. One fact does not give me peace - this issue started appearing after fresh windows install. On the old system I was able to use OpenVPN and Amnezia simultaneously. I am too using OpenVPN to work, and work config has not changed for several years. I tried old Amnezia versions - no success. So what have suddenly changed? No idea.

bsakaguchi commented

2026-10-13 20:28:59 +00:00

Author

Owner

@BoDDEneR commented on GitHub (Apr 6, 2026):

Workaround can be found here.

TL:DR
Open regedit, then open Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\ROOT\NET\. Locate Wintun adapter (probably 000), then change value of HardwareID from «wintun» to something else.

@BoDDEneR commented on GitHub (Apr 6, 2026): Workaround can be found [here.](https://gitlab.com/openconnect/openconnect/-/work_items/699#note_2010707130) TL:DR Open regedit, then open Computer\\HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Enum\\ROOT\\NET\\. Locate Wintun adapter (probably 000), then change value of HardwareID from «wintun» to something else.

bsakaguchi commented

2026-10-13 20:28:59 +00:00

Author

Owner

@VladiStep commented on GitHub (Apr 7, 2026):

Workaround can be found here.

TL:DR Open regedit, then open Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\ROOT\NET. Locate Wintun adapter (probably 000), then change value of HardwareID from «wintun» to something else.

I knew this was solvable something like this!
Thank you very much!

Update: if you already have the OpenVPN adapter, you need to reinstall AmneziaVPN after renaming, otherwise it doesn't start

@VladiStep commented on GitHub (Apr 7, 2026): > Workaround can be found [here.](https://gitlab.com/openconnect/openconnect/-/work_items/699#note_2010707130) > > TL:DR Open regedit, then open Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\ROOT\NET\. Locate Wintun adapter (probably 000), then change value of HardwareID from «wintun» to something else. I knew this was solvable something like this! Thank you very much! _Update:_ if you already have the OpenVPN adapter, you need to reinstall AmneziaVPN after renaming, otherwise it doesn't start

bsakaguchi referenced this issue

2026-10-13 21:18:48 +00:00

[PR #805] [MERGED] fixed qml warnings and hindi language warnings #2123