I have turned Hyper-V feature on and off (twice) and reinstalled Hyper-V and XP, but cannot get the virtual switch to access a Wifi connection. I have followed Kari's tutorial applying to the legacy switch, but no connection. Does Hyper-V not work on a laptop?
Version 1909 Build 18363.959
Only a question, does the Notebook support Hyper-V? This is mine using systeminfo in the Command Prompt window:
The Legacy Network Adapter is connected to an external switch that I created; and I have tried the default switch, but neither works.
- - - Updated - - -
My systeminfo reports: "Hyper-V Requirements: A hypervisor has been detected. Features required for Hyper-V will not be displayed."
Turn Windows features on or off are all checked.
Last edited by Tipiford; 18 Jul 2020 at 06:35. Reason: Additional info
Hi there
Have you enabled SMB1 on your Windows HOST machine -- it's not set by default -- so networking won't see things like XP that need SMB1 for networking.
For XP Virtual Machines another idea might be to use VMWare player or Virtual Box -- both these Virtual machine systems (free BTW) have proven track records with XP Virtual machines -- It's possible that HYPER-V could have problems with XP security or whatever -- HYPER-V wasn't even thought of when XP was a mainstream OS -- in theory it should work but there's nothing wrong in trying another approach if you can't find a solution to the original problem.
Note you might find some tips here in this old post of mine
XP and NAS (Samba) access
Cheers
jimbo
That's what I got as well, with Hyper-V enabled.
So it's looking good.
The fact that you got a VM installed and running means this is OK.
For the networking issue it's just a matter of proper VM settings. I'm als sort of 'new' to Hyper-V since I've began to use it more recently.
Will definitely begin with Kari's tutorials if XP is on the list of VMs you need to run with networking. There is a legacy switch you need instead of the default one.
Part 5 here:
Hyper-V virtualization - Setup and Use in Windows 10
EDIT:
I see.
I'll need to test that on my own to confirm but I believe it; XP might behave diferently unlike newer OSes since Hyper-V does't 'know' it that well.
I'll go with Bree's post (5) for a custom switch for XP.
Quote
