New
#1
May I ask why you would like to enable the Hyper-V Extensible Switch? It is needed only when you have created Hyper-V virtual network switches, which your screenshot clearly shows you have not done. Even then it does not need to be manually enabled, the Hyper-V Virtual Switch Manager does that for you, disabling everything else in your native physical network adapter's properties, only enabling the Hyper-V Extensible Switch.
Screenshots from my PC showing how the properties are set when an external virtual switch has been correctly set up. Notice that these changes have been automatically made by the Hyper-V Virtual Switch Manager, I have had no need to edit the properties manually.
The host physical NIC properties, everything else disabled, only the Hyper-V Extensible Switch enabled:
And the properties of the Hyper-V external virtual switch which at the moment takes care of my network traffic, over the Hyper-V Extensible Switch on my host NIC:
Kari
I read somewhere that this flag needed to get set manually to allow a Hyper-V guest OS to access the Network. I got it done in Hyper-V manager which as you point out takes care of all those flags. Thanks for your help.
So after much research, I haven't found a solution yet to this error message (see screenshot) in Hyper V while trying to set up virtual switches. I have uninstalled all 3 of the virtual switches I had before yesterday as they suddenly became disabled after installing the replacement router (original has been RMA'd) yesterday. I uninstalled Hyper V and reinstalled it today but I still am getting this same message. I also had two ethernet adaptors listed in my system and they were working until today (see screenshots) My primary is fine. Ethernet 2 says the cable has been disconnected but it doesn't have a physical cable plugged into it. This is a logical network adaptor as far as I know installed by my then Win10 home OS. I have since upgraded to Win10 Pro within the last two weeks. If anyone has any ideas I am up for it.
Yes, I found out that I had a corrupted NVMe hard drive and between that and corrupted files, it finally gave up the ghost. I replaced it with a better SSD and reinstalled the OS. No problems since. Thank you
- - - Updated - - -
So I also wanted to add that Win10 OS Hyper V does not support any VM's using WinXP anymore. That may have been part of my trouble to begin with. I learned this from a Microsoft tech site after everything went bust and I had posted my original thread here.
I very much dislike it when people spread false information as facts. "I heard that..." or "I think that..." suddenly becomes "This is a fact".
In screenshot, taken just now as the date and time shows (bottom left corner), two Windows XP Hyper-V virtual machines running at the same time. One, showing Opera Speed Dial page is a Windows XP Mode VM imported from Virtual PC in Windows 7, the other showing today's Coronavirus news at BBC in Internet Explorer is a clean installed and fully updated original Windows XP Pro SP 3.
(Click to pop out, click again to enlarge.)
Kari
I stand corrected. As I mentioned, I read that off of a Microsoft tech site posted by one of their techs. So, with that said, if I try to reinstall WinXP using Hyper-V, are there any set up issues I should be aware of? I couldn't get XP to work with any of my host physical parts so I was left with no sound and a very small desktop because I couldn't get the video to cooperate with my hardware. Any lessons to be learned?