It means 10 can connect to XP but the same XP can't connect to the same 10. Logical conclusion: you have something wrong in your 10 network and sharing settings and / or firewall.
Have not heard from you all week. Vacation?
Incidentally this problem existed when I had win8.1 and carried over after upgrading to win10.
While waiting for a reply I went back to 4.6 and removed my virtual switch, continued with 5.1, the 4.9 onward. Reinstalled a local printer in virtual and still unable to print. Don't know what else to do except delete my virtual setup entirely and start over. Wondering if this would eliminated my xp setup to where I would have to install xp again, which would be a problem since I don't have my xp program disk anymore. Where would I get the program again? (I still have the key.}
Or do I need to do something else to discover the problem?
Since that you have not told anything new, anything that would change the situation, anything that would help me to find something else to suggest.
All of us here at the Ten Forums are doing this voluntarily, in addition to our real life. It's a hobby, not a profession. On these forums in general and my own tutorial threads in particular, I am as active as my real life and other stuff allows.
That being said, I have nothing else to suggest. I have no issues in getting a Windows XP Hyper-V virtual machine to work correctly in my network, including printing to host printer.
Sorry you feel that way. I don't see where I accused you of anything or meant to do it. Sorry.
Realize that I have been trying to resolve this problem for many days, feeling very frustrated, and is very time consuming to me as well as you. Frustration brings out a tone that is not normal for me. Sorry again and I really do appreciate all the time you also spent trying to resolve my difficult problem.
Hi - I am a newie and not too computer literate but trying hard to get my older desktop to start Hyper-V after doing the upgrade to Win 10 and this great tutorial. Upon starting Hyper-V I get the failing message that hypervision is not running. I noticed that it is grayed out in windows features. Running CoreInfo shows everything good, I think. In running another info program it says that I do not have SLAT capability, even though AMD says my Athlon X2 Dual Core 4850E processor is capable of running Hyper-V. I checked my bios and could not find anywhere to turn it on. Any approach to a solution or ability to fool the computer in thinking that it has or does not need SLAT?
Incidentally, I did have Virtual PC XP Mode running when I had Windows 7 Pro on the computer.
I forgot to include 3 views of the coreinfo output. Maybe it would be helpful to someone more knowledgeable than I.
Last edited by chirobeliever; 14 Sep 2015 at 22:38.
First of all thank you for the brilliant post.
I tried to follow all your instructions but got stuck at the very beginning. When I Turned on the Hyper-V feature it did not ask me to reboot. However I did. After the reboot when I started the Hyper-V Manager, it did not show my comp name in the left-hand pane. I said 'Connect to Server' and selected 'Local Computer' and got the following error:
An error occurred while attempting to connect to server "MyCompName". Check that the Virtual Machine Management service is running and that you are authorized to connect to the server.
The operation on computer 'MyCompName' failed: Invalid class
I verified in the Services and there were no such a service - Virtual Machine Management.