Microsoft Client Hyper-V

Contributor(s): Tayla Holman

Microsoft Client Hyper-V is a type-1 hypervisor for the Windows 8.x and Windows 10 operating systems (OSes) that allows users to run multiple operating systems inside a virtual machine (VM).

Microsoft introduced Client Hyper-V in 2012 with the release of Windows 8 as a replacement for the Type-2 hypervisor Windows Virtual PC.

Developers and IT professional can use Client Hyper-V to build a test environment. A developer can create a VM hosted on a laptop and then export it to the Windows Server production environment once it has passed inspection. Client Hyper-V can also be used to test software on multiple OSes by creating separate VMs for each.

When a user enables Client Hyper-V, Hyper-V Manager is also installed. Hyper-V Manager creates and manages VMs; it also has switch capabilities to connect a VM to an external network connection.

There are some limitations to Client Hyper-V as opposed to the server version of Hyper-V. Client Hyper-V does not support Hyper-V Replica, Virtual Fibre Channel, VM live migration, SR-IOV networking or RemoteFX capability.

Client Hyper-V can only be enabled on 64-bit versions of Windows 10, or Windows 8.x Pro or Enterprise editions. For hardware requirements, Client Hyper-V requires a 64-bit processor with second-level address translation, the CPU must support VM Monitor Mode Extension and 4 GB of RAM.

This was last updated in October 2015

Continue Reading About Microsoft Client Hyper-V

Dig Deeper on Microsoft Hyper-V management

Join the conversation

1 comment

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

How do you use Client Hyper-V in your data center?


File Extensions and File Formats