Jump to content
Not connected, Your IP: 44.200.94.150

Search the Community

Showing results for tags 'hyperv'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • AirVPN
    • News and Announcement
    • How-To
    • Databases
  • Community
    • General & Suggestions
    • Troubleshooting and Problems
    • Blocked websites warning
    • Eddie - AirVPN Client
    • DNS Lists
    • Reviews
    • Other VPN competitors or features
    • Nonprofit
    • Off-Topic
  • Other Projects
    • IP Leak
    • XMPP

Product Groups

  • AirVPN Access
  • Coupons
  • Misc

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Twitter


Mastodon


AIM


MSN


ICQ


Yahoo


XMPP / Jabber


Skype


Location


Interests

Found 1 result

  1. Hey guys, So I spent the last few hours or so trying to figure out this bug I was getting while starting AirVPN, and I wanted to share my results in case some poor soul comes across this seemingly obscure situation in the future. I'll do bullet points as to try not to talk too much: AirVPN was working greatI installed Visual Studio 2013 ProAirVPN then stops working immediately after installI notice there are a few new network adaptersMUCH MUCH later I found that by uninstalling a feature called Hyper-V, which (I'm only guessing) came with Visual Studio, did the "Driver installation failed" error stop and I was able to connectSo yeah... I spent some time digging through the source and then utilizing the newly installed VS to compile and debug the lines surrounding the error. Well, I had never heard of Hyper-V before and so all I wanted was AirVPN to work with my current adapter situation. I thought it was because one C# library function was returning adapter descriptions that AirVPN wasn't expecting. But even when I tried forcing it to one of the 10 available adapters (some of which were labelled TAP) yieled pretty much the same result every time. I now think it was due to the bridging that Hyper-V forced upon me, and since my issue is resolved I don't care to look into this further. Tl;dr: Check if Hyper-V is installed in your Windows features. If so, uninstall it, reboot, and re-run AirVPN. If Hyper-V isn't installed try this: https://airvpn.org/topic/13126-driver-installation-failed/ Here's what my adapters looked like before uninstalling Hyper-V: Here's an image that shows how to uninstall Hyper-V:
×
×
  • Create New...