upgrade glitches

[zeroone1zero 0]

I tend to put off upgrading to newer versions of AirVPN/Eddie
as it always seems to turn into a little fiasco.

My most recent attempt is no different.  I am trying to upgrade from
2.20.0 to 2.21.6 and am failing miserably.  

I opened 2.20, deactivated the lock and removed the app from sys startup.
Restarted the computer.  I kept the app's folder in Program Files but renamed
it.

I extracted 2.21 portable to an 'AirVPN' folder in Program Files.  Started
Eddie-UI and it goes into a "restarting in..." loop from failing to install
"tunnel driver wintun".  I cancelled that.  I set the app to start with the system
and rebooted.

Same loop.  This is while the 'recommended server' is located in the
Netherlands.  I am not in Europe.  I am in N America.

Tried the 'force tap driver' option ... rebooted the computer.  Same loop.

Switched back to 2.20.

All this is a repeat of what was happening when I previously tried to
upgrade a couple of weeks ago.  I even tried the installer and got the
exact same loop re: wintun.

I am at a loss.  I could disable & remove the app ... clear out registry
entries and try installing from scratch, but I thought I would first ask if
I am missing an important step or something.

Any thoughts?

[OpenSourcerer 1435]

Try to connect (let it loop once), then in Logs tab click the lifebelt icon and upload/paste the output here or click the Upload to paste URL in support ticket button and post the link instead.

[zeroone1zero 0]

The generated log is:
! 2022.05.17 04:46:09 - Activation of Network Lock - Windows Filtering Platform
I 2022.05.17 04:46:13 - Checking login ...
! 2022.05.17 04:46:14 - Logged in.
I 2022.05.17 04:46:21 - Session starting.
I 2022.05.17 04:46:21 - Checking authorization ...
E 2022.05.17 04:46:24 - Exception: wintun.dll WintunCreateAdapter fail
I 2022.05.17 04:46:27 - Checking authorization ...
E 2022.05.17 04:46:29 - Exception: wintun.dll WintunCreateAdapter fail
I 2022.05.17 04:46:31 - Cancel requested.
! 2022.05.17 04:46:31 - Session terminated.

the copy/paste to txt is more detailed:

. 2022.05.17 04:44:32 - Eddie version: 2.21.6 / windows_x64, System: Windows, Name: Windows 10 Pro, Version: Microsoft Windows NT 10.0.19042.0, Mono/.Net: v4.0.30319
. 2022.05.17 04:44:32 - Raise system privileges
. 2022.05.17 04:44:33 - Profile options not found, using defaults.
. 2022.05.17 04:44:34 - OpenVPN - Version: 2.5.5 - OpenSSL 1.1.1l  24 Aug 2021, LZO 2.10 (C:\Program Files\AirVPN\openvpn.exe)
. 2022.05.17 04:44:34 - SSH - Version: plink 0.73 (C:\Program Files\AirVPN\plink.exe)
. 2022.05.17 04:44:34 - SSL - Version: stunnel 5.56 (C:\Program Files\AirVPN\stunnel.exe)
I 2022.05.17 04:44:34 - Ready
. 2022.05.17 04:44:35 - Collect information about AirVPN completed
! 2022.05.17 04:46:09 - Activation of Network Lock - Windows Filtering Platform
I 2022.05.17 04:46:13 - Checking login ...
! 2022.05.17 04:46:14 - Logged in.
I 2022.05.17 04:46:21 - Session starting.
I 2022.05.17 04:46:21 - Checking authorization ...
E 2022.05.17 04:46:24 - Exception: wintun.dll WintunCreateAdapter fail
I 2022.05.17 04:46:27 - Checking authorization ...
E 2022.05.17 04:46:29 - Exception: wintun.dll WintunCreateAdapter fail
I 2022.05.17 04:46:31 - Cancel requested.
! 2022.05.17 04:46:31 - Session terminated.

Thanks, I appreciate your time!

[OpenSourcerer 1435]

9 hours ago, zeroone1zero said:

Thanks, I appreciate your time!

You do not, as I specifically asked for the support file by clicking the lifebelt icon, not pasting what you think might be relevant.
 

On 5/16/2022 at 7:33 PM, OpenSourcerer said:

in Logs tab click the lifebelt icon and upload/paste the output here

Yes, the complete output is meant. I thought this goes without saying…

[zeroone1zero 0]

https://eddie.website/report/8592b7a1/

[OpenSourcerer 1435]

Thank you.
Quite curious, from all that info it's not apparent why it would fail… TAP is right there, so interface installations clearly work.
Do you have an antivirus program running in the background?

You can work around this problem by setting Force usage of old TAP driver in Eddie Preferences > Advanced. This will get you up and running again, since you wrote it worked with 2.20. With 2.21.6 wintun is the default driver used.

[zeroone1zero 0]

Yes, curious indeed.  I have contacted Support and they've forwarded the ticket
on to the Eddie Development team.  Hopefully they can suggest what the issue
might be.

No AV running in the background.  I even shut down my firewall (simplewall) incase
it was interfering somehow.

I do have a working copy of 2.2 that I restore/re-enable after trying to get 2.21.6
going.  And I have tried everything - installer vs portable, tried the 32Bit, tried in
Safe Mode.  Tried installing eddie-wintun-x64.msi independantly and it failed.
I've gone thru Windows Services and Device Manager looking for anything
related and found nada.

I even completely disabled and removed all things Airvpn & Eddie, removed all
related registry entries so I could try installing witha 'clean slate'.  Still got the
same loop.

I tried the 'Force useage of old TAP driver before and IIRC it got stuck on some-
thing about IPv4 and wouldn't connect to a server.  Strange again.

Anyhoo, I do have 2.20 running smoothy as always.  I can stick with that for now
but it would have been nice to have the upgrade.

Fingers crossed that Support comes thru with a solution.

[OpenSourcerer 1435]

16 hours ago, zeroone1zero said:

I tried the 'Force useage of old TAP driver before and IIRC it got stuck on some-
thing about IPv4 and wouldn't connect to a server.  Strange again.

This is very interesting because you're far from the first with this particular symptom on v2.21.6 on Windows. And so far the forums didn't yield a working solution for it.
 

16 hours ago, zeroone1zero said:

Fingers crossed that Support comes thru with a solution.

Could you please post the solution here, too, when it's there?

[Clodo 176]

On 5/19/2022 at 8:30 PM, OpenSourcerer said:

You can work around this problem by setting Force usage of old TAP driver in Eddie Preferences > Advanced. This will get you up and running again, since you wrote it worked with 2.20. With 2.21.6 wintun is the default driver used.

I understand you want to help resolve issue, but please don't suggest anymore to check the "Force usage of old TAP driver": it's a deprecated feature, and we need to resolve issue without this fallback. Thanks.

@zeroone1zero i will reply your ticket soon today

[zeroone1zero 0]

I heard back from Support on & they reiterated that the issue
was 'unique' to my system.  They provided me with a link to a
'special version' that dumps additional info and asked me to
install and run it.  Which I did. It still looped on "wintun".

If that did happen, I was asked to switch to the WinGuard protocol
That was also unsuccessful and again, looped on "wintun".

I provided both log files.  I did say that I was in no rush since v2.20
was still running smoothly with the TAP adapter.

I don't know if anything was found in the logs because I haven't
heard anything back as of yet.

===================

Update ... 4 days later...

Ok ... fine ... got it ...bye.

Edited ... by zeroone1zero
update