Hyper-V Virtual Switch Broke my Network Card

Question

What I did:

1. Activated Hyper-V (Enable Virtualisation / Enable Hyper-V Feature ect.)
2. Downloaded the Fedora iso 64bit
3. Created Hyper-V VM and Installed Fedora
4. Created a Virtual Switch for my VM
5. Decided Hyper-V is total bullocks, decided to opt for a different VM Manager
6. Removed my VM
7. Deactivated Hyper-V
8. Uninstalled the Hyper-V Switch Via Device Manager
9. Restarted PC
10. Lost Connectivity via my one network adaptor (my motherboard has 2).

Here's the funny bit. I'm running dual boot Ubuntu. When I try to use my 2nd network adaptor in Ubuntu it doesn't work. insert mind blown gif

Did Windows f#!k with my Firmware? Did I just lose my 6GB network card because some intern at Microsoft f#!ked up?

Link to Motherboard's Page

Answer 1

Okay so it sprung back to life. I'm not going to mark this answer as correct, since I'm not ENTIRELY sure what I did that fixed it. I did so many things... So.. So many things.

1. Re-Enable Hyper-V (Virtualization / Feature Activation)
2. Create Virtual Switch (While being plugged in to your network adapter that ISN'T working)
3. Remove Virtual Switch (While being plugged in to your network adapter that ISN'T working)
4. De-Activate Hyper-V on Feature List
5. Wait for restart loop to finish
6. Go into BIOS De-activate virtualization
7. If your BIOS has the option, install LAN Drivers via your BIOS

Conclusion:

My implementation of Hyper-V was probably incorrect (unrelated). I'm not saying Hyper-V is stupid, I'm saying the way Windows handles it's network interfaces is. Somewhere along the lines I think Windows tried some sort of Firmware hack to bridge connection between my Network Adapter and Virtual Switch and me removing things "incorrectly" did something strange to it.

Advice for the Lost Soul

If you're not a masochist like myself and you don't thoroughly enjoy banging your head against a sour stone wall, see if you can't re-flash the firmware of your network adapter you're trying to recover.