Windows 10: Why i cant able to open my hyper v virtual machine windows 10

please tell how to fix this issue i try most time and also i see this in youtube but i can't find solution please help meI have 4GB ram is it enough to run hyper v virtual machine in windows 10 please give Please help me to give the solution

:)

 

Hyper-V Virtual Machine not recognised

The folder where your VM is do you see a .vhd file?

Here is a great article step by step on how to import VM into hyper-v.

https://social.technet.microsoft.com/wiki/conte...

 

Cannot turn off Hyper V, cannot run Virtual Box machines or VMWare machines

Since the latest update:

Edition: Windows 10 Pro

Verion: 1607

OS Build: 14393.222

I can no longer turn off Hyper V and thus cannot run Virtual Box machines or VMware machines.

When I attempt to turn off Hyper V and restart Windows as requested, Windows simply re-enables Hyper V.

Then when I try to run a Virtual Box machine, I get an error like this:

Failed to open a session for the virtual machine Centos 70.

VT-x is not available (VERR_VMX_NO_VMX).

Result Code:

Component:
ConsoleWrap

Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

When I try to start a VMware machine, I get this:

VMware Player and Hyper-V are not compatible. Remove the Hyper-V role from the system before running VMware Player.

But as I have noted, I am not able to turn off Hyper-V since the Anniversary Update.

Any suggestions would be greatly appreciated.

 

Where is the Hyper V Manager, How to I start it ?

I am trying to setup an XP virtual Machine on Windows 10 Pro.

I followed the steps in Neil Peterson article of 5/9/2016.

System Requirements - done - ok

Install Hyper-V - done - ok

Create a Virtual Switch - skip

Create a Virtual Machine

Create a Virtual Machine with Hyper-V Manager

These steps walk through how to manually create a virtual machine and deploy an operating system to this virtual machine.

• 
  In Hyper-V Manager, click Action > New >
  Virtual Machine to bring up the New
  

Uhhhhhhhhh - this step obviously implies one knows

1) Where the Hyper-V Manager is

2) How to start the Hyper-V Manager

Isn't that odd ?