Windows – Microsoft Kernel Debug Network Adapter

What appears to have been the problem is that the bridging protocol was not supported by the AP (access points) of my university.

Here is the workaround (as far as I can tell this way is more robust than the bridging way that is done by default, but there might be some additional overhead (not sure how much)):

1. Create an internal network switch
2. Connect it to the guest OS
3. Connect the internal virtual adapter to the virtual adapter created by Hyper-V like so: .
   Go to the adapter that provides internet access to the machine, and then click sharing. Select the adapter created in step 1.
4. Everything should work well.

Credit for this solution goes to the networking people at Binghamton University, more specifically Joe and Alan.

I'm having a similar issue on my work wireless. I can connect at home but not at work. The issue is because Cisco wireless use a different encryption of security than windows 8. There are two solutions. Either:

1. Change your drivers back to windows 7 like mentioned above.
2. Have your school update their wireless to the latest Cisco drivers.

Here is a link to the blog post