New
#460
I really need to get Hyper-V working. I'm considering a refresh/reset/repair procedure to see if that straightens things out and allows me to install Hyper-V. Any advice on which route I should choose?
I really need to get Hyper-V working. I'm considering a refresh/reset/repair procedure to see if that straightens things out and allows me to install Hyper-V. Any advice on which route I should choose?
Welcome to Ten Forums.
I think you are confusing 'switch' with 'adapter'. For an XP virtual machine, you need to set it up with a legacy network adapter.
See 'Part Five: Create a legacy Windows vm (Windows Vista or earlier)' in the tutorial for how to add the legacy network adapter hardware to your VM. Connect it to the external switch you created and all should work.
The Legacy Adapter will appear to XP as a generic Intel adapter for which it already has the drivers.
![]()
Last edited by Bree; 21 Apr 2021 at 18:38.
EDITED BELOW
Kari - Many thanks for your videos and this thread. On my Win 10 Pro 64-bit host, I have created a Hyper-V VM for the first time and installed Win 11 Pro in it. Had a glitch along the way but fixed it.
Question: How can I configure my new Win 11 VM to "see" the files and additional hard drives on my Win 10 Pro host? WOuld be a great way to share some files, etc.
FYI - I followed your Part Three to create the three network connections - External, Internal and Private. But the Win 11 doesn't see any disk in the Win 10 host in its "Network".
EDIT - on my Win 10 "host", Task Manager shows my External New Switch, which is active even when the VM is off, my Internal New Switch and my Default Switch, but not my Private New Switch. I wonder why.
Per a different thread, I might delete or remove the Internal and Private, leaving the External. Does that sound right?
Last edited by glnz; 10 Oct 2021 at 22:55.