Hyper-V virtualization - Setup and Use in Windows 10  

johngalt said:

No worries on the delays.

As for hypervisorlaunchtype = OFF, that is not surprising, as that is showing in the right direction, indicatin the Hyper-V is, in fact, installed. For example, When I run BCDEDIT I don't even show that hypervisorlaunchtype setting - but that makes sense for me because I do not have Hyper-V enabled in the first place.

I'm also running Insider Preview builds, currently WinX x64 Pro 1809 (Build 18312.1007), but this weekend I may have enough time available to enable Hyper-V items as you did and see if mine remained blocked or actually get checked.

Nothing helped. All the trials to solve didn't prevent the Hyper-V installation problem.
Also, on another forum somebody said that by others' experience, antivirus usually prevents installing Hyper-V.
Disabling the antivirus may solve the issue, but he said that many times that's not enough and it's required
to completely uninstall the antivirus, install the Hyper-V and then to reinstall the antivirus.

He was right. I disabled my antivirus but that was not enough as he said. But I am not going
to uninstall my antivirus for that. I don't want any new unexpected surprises, because my trust on Windows 10
is now at its lowest level. This is the worst Windows edition I have seen until today. It's unexpected, complicated, unreliable and unfriendly to whatever concerned with smooth functioning. Windows 10 is better perhaps just with its recovery & restore tools compared to the older Windows editions.

So I give up now the Hyper-V virtualization. Thanks for your efforts.

Thanks for the useful tutorial.

I now have a working Windows XP SP3 VM. What are the best options for transferring files / folders from the host PC to the VM? I can't access the internet from the VM despite installing a legacy network connection as described in Part 5. Any tips to solve? Is it safe to browse the internet from a Hyper V Windows XP VM?

Kari said:

Setting up networking between XP VM and W10 host can be tricky. Best option (in my opinion) to transfer files is to mount XP VHD on host and copy & paste.

I just installed XP on Hyper-V VM, using legacy network adapter connected to Default Switch. Internet connection works without issues:


Last but not least: no, XP is not safe, be it a physical or virtual machine. I would not use it to download anything, and would only visit known, safe websites.

Kari

Transferring the files via the .vhd virtual drive worked fine.
The default network switch seems to be linked to an internal network and can't be changed. I created an external switch and linked it to a default legacy network adapter in the XP VM. This has now downloaded 121 updates! so it sees the Windows update server but I can't browse the internet using Internet Explorer.

I also installed Guest services from the vmguest.iso file using the method here https://social.technet.microsoft.com...inserverhyperv

Steve C said:

The default network switch seems to be linked to an internal network and can't be changed. I created an external switch and linked it to a default legacy network adapter in the XP VM. This has now downloaded 121 updates! so it sees the Windows update server but I can't browse the internet using Internet Explorer...

I don't use the default switch either, I like to see and use all my physical and VM machines on my network, each sharing out its own C:\Temp folder for easy file transfer.

Sharing can even be done in XP (VM or real) but any W10 machine that wants to connect to an XP share must have the 'SMB 1.0/CIFS Client' enabled in Windows Features. For XP to connect to a share on another machine, that machine must have the 'SMB 1.0/CIFS Server' enabled. You may not want to have SMB1 enabled so the .vxd is a good solution.

...but I can't browse the internet using Internet Explorer...

Too old, XP's IE doesn't know what HTTPS is

You can see (the few remaining) http web servers, Google for example still supports http and can be seen in my XP VM's IE (but none of the search result links work, they all point to https servers).

Bree said:

I don't use the default switch either, I like to see and use all my physical and VM machines on my network, each sharing out its own C:\Temp folder for easy file transfer.

Sharing can even be done in XP (VM or real) but any W10 machine that wants to connect to an XP share must have the 'SMB 1.0/CIFS Client' enabled in Windows Features. For XP to connect to a share on another machine, that machine must have the 'SMB 1.0/CIFS Server' enabled. You may not want to have SMB1 enabled so the .vxd is a good solution.



Too old, XP's IE doesn't know what HTTPS is

You can see (the few remaining) http web servers, Google for example still supports http and can be seen in my XP VM's IE (but none of the search result links work, they all point to https servers).

Thanks.

After installing the updates including IE8. I found I could browse http sites but not https sites. I just installed Firefox which works fine. I also found many antivirus programs don't work but I discovered an XP version of AVG which is sufficient. I now have a working activated XP VM with internet support for experimental use and supporting legacy programs should they stop working in Windows 10.