
close
close
Hyper-V is Microsoft’s native hypervisor stack that can be used to create and run virtual machines (VMs). This allows administrators, developers, power users, and others to share their computer’s resources with one or more VMs for testing, development, security, legacy support, labs, and much more.
Note that on a server host, these guest VMs can be naturally used to actually provide services and workloads for client computers. Hyper-V also provides virtualization on Windows, which include Windows Server and Windows desktop clients.
You should also note that although the term “Hyper-V” may seem identical regardless of where it’s used, Microsoft now differentiates the term: “Hyper-V on server” is used for Server operating system, and “Hyper-V on Windows” is used for desktop operating systems.
There are some feature differences between the two, and the following features will not function on Windows 10: Remote FX capability to virtualize GPUs, live migration of VMs from one host to another, Hyper-V Replica, Virtual Fibre Channel, SR-IOV networking, and Shared .VHDX.
There are several different system requirements you must be aware of before attempting to install Hyper-V on Windows 10:
Operating system edition: On Windows 10, Hyper-V can only be enabled on the Pro and Enterprise editions of Windows 10.
CPU Architecture: Hyper-V can only run on a 64-bit system. The CPU must have support for Second Level Address Translation (SLAT). SLAT is a feature present in the current generation of 64-bit processors by Intel and AMD. Also note that Hyper-V does support creation of both 32-bit and 64-bit guest operating systems in the VMs, but the host itself must be running a 64-bit operating system.
Memory: You need to have at least 4GB of RAM.
Hyper-V has a feature called Dynamic Memory, which allows you to assign a dynamic range of memory allocation to the guest VMs, where you specify a minimum and maximum. This enables you to actually assign more memory to the guest VMs that you actually have on the host computer and share unused memory between guest VMs.
A good method of finding if your existing CPU can run Hyper-V is to use a free tool by Microsoft called CoreInfo.
Execute the following command from an elevated command prompt (Run as Administrator):
advertisment
coreinfo -v
You’ll get results like this one:
In the screenshot above, you can see that my existing processor does support Intel hardware-assisted virtualization, and Intel’s extended page tables/second level address translation (SLAT).
These are the operating systems that can run as guest VMs on a Windows 10 Hyper-V host:
Windows Vista SP2, Windows 7 and Windows 7 SP1, Windows 8, Windows 8.1, Windows 10, Windows Server 2008 SP2, Windows Server 2008 R2 SP1, Windows Server 2012, Windows Server 2012 R2, plus several versions of UNIX/Linux including CentOS and Red Hat Enterprise Linux, Debian, SUSE, Oracle Linux, Ubuntu and FreeBSD.
So with that said, let’s install Hyper-V. There are three different ways to do that, choose the one that fits you most.
This approach is the easiest for most users. Right-click on the Start button and choose “Programs and Features”.
Selecting programs and features. (Image Credit: Daniel Petri)
Programs and Features in Windows 10. (Image Credit: Daniel Petri)
Enabling Hyper-V on Windows 10. (Image Credit: Daniel Petri)
Open a PowerShell console with elevated permissions.
Run the following command:
advertisment
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V –All
Once again, you’ll need to reboot twice after the installation has completed.
Like in previous Windows versions starting from Windows Server 2008, the Deployment Image Servicing and Management (DISM) tool can be used to service Windows images and enable features.
Open a PowerShell console or Command Prompt console with elevated permissions, and type the following command:
DISM /Online /Enable-Feature /All /FeatureName:Microsoft-Hyper-V
Again, reboot the computer twice after completing the install.
Regardless on how you perform the installation of the Hyper-V role, there are some cases where you may need to completely shut down the system after these reboots, disconnect the power cable, and wait a couple of minutes. Then you can connect the power cable and turn it on. Only then will the role function properly. Note that this is a CPU issue, not a Windows-specific issue.
More from Daniel Petri
advertisment
Petri Newsletters
Whether it’s Security or Cloud Computing, we have the know-how for you. Sign up for our newsletters here.
advertisment
More in Windows 10
IT Admins Report Issues With Microsoft Store Version of Quick Assist App
May 16, 2022 | Rabia Noureen
This Week in IT - Windows 10 Gets Search Highlights and Is Microsoft in Hot Water Over Windows Cloud Pricing?
Apr 15, 2022 | Russell Smith
Most popular on petri
Log in to save content to your profile.
Article saved!
Access saved content from your profile page. View Saved
Join The Conversation
Create a free account today to participate in forum conversations, comment on posts and more.
Copyright ©2019 BWW Media Group