Install Hyper-V on Server 2012 Core

Server Core has no Server Manager GUI on the console, so the Hyper-V role is added from the command line. This guide gets a Windows Server 2012 Core host ready with sconfig, enables Hyper-V with DISM, reboots, checks that the hypervisor is running, and connects from a remote management console.

Prerequisites

  • A 64-bit CPU with hardware virtualization (Intel VT-x or AMD-V) and hardware DEP (Intel XD / AMD NX), both turned on in the BIOS/UEFI. Second Level Address Translation (SLAT) is not required for Hyper-V on Server 2012; it becomes mandatory with Windows Server 2016.
  • Windows Server 2012 installed in Server Core mode (see Install Server 2012 Core).
  • A local administrator account, and ideally a domain membership so remote management works without extra trust configuration.

1. Prepare the server with sconfig

Get your server all set up, with a static IP, fully patched, on the domain, etc., and ready to install Hyper-V. From there issue the following command to get into Server Config:

sconfig
sconfig Server Configuration menu on Windows Server 2012 Core host 09HYP11 before installing Hyper-V

The menu covers everything a new host needs before it runs virtual machines:

  • 8) Network Settings: give the management NIC a static IP and DNS servers.
  • 1) Domain/Workgroup and 2) Computer Name: name the host and join it to the domain.
  • 5) / 6) Windows Update: install updates before adding the role (see Install Windows Updates on Server Core).
  • 4) Configure Remote Management and 7) Remote Desktop: allow the remote tools you will use to manage the host.

Before installing, you can confirm the CPU is ready. On Server 2012, systeminfo ends with a Hyper-V Requirements section; VM Monitor Mode Extensions, Virtualization Enabled In Firmware and Data Execution Prevention Available should all say Yes.

systeminfo

2. Enable the Hyper-V feature with DISM

Install Hyper-V with the following command:

dism /online /enable-feature /FeatureName:Microsoft-Hyper-V
dism /online /enable-feature /featurename:Microsoft-Hyper-V completing at 100% and asking to restart

/online tells DISM to service the running operating system rather than an offline image, and /FeatureName is the internal name of the role. When the progress bar reaches 100% DISM asks to restart; answer Y, because the hypervisor only loads at boot.

The same result in PowerShell (type powershell first on Server Core):

Install-WindowsFeature -Name Hyper-V -Restart

From there, Hyper-V is installed. Go ahead and reboot, and connect with either SCVMM or Hyper-V Manager from a remote console.

3. Verify the role after the reboot

dism /online /get-featureinfo /featurename:Microsoft-Hyper-V

The output should show State : Enabled. Running systeminfo again now reports that a hypervisor has been detected instead of listing the requirements. In PowerShell, Get-WindowsFeature Hyper-V shows the role as Installed.

4. Manage the host remotely

Server Core has no Hyper-V Manager on the console. Use Hyper-V Manager on a Windows 8 / Server 2012 or newer machine with the Hyper-V management tools (RSAT) installed, choose Connect to Server and enter the host name, or add the host to System Center Virtual Machine Manager. Remote PowerShell also works; see Enable Remote Powershell Access.

Troubleshooting

  • The feature will not install, or the hypervisor does not start after reboot: virtualization or DEP is disabled in firmware. Enable Intel VT-x/AMD-V and XD/NX in the BIOS, power-cycle fully, and check systeminfo again.
  • Installing inside a virtual machine fails: the guest CPU does not expose virtualization extensions. Nested virtualization is not available for a Server 2012 host; install on physical hardware.
  • Hyper-V Manager cannot connect: make sure Remote Management is enabled in sconfig, the host resolves in DNS, and both machines are in the same or trusted domains. Workgroup setups need extra credential and firewall configuration.

Modern equivalent

On Windows Server 2019, 2022 and 2025 Core the role is still named Hyper-V. Install-WindowsFeature -Name Hyper-V -IncludeManagementTools -Restart or the same DISM command works, and Windows Admin Center is a common browser-based way to manage Core hosts. Newer releases require a CPU with SLAT.

If you are interested in a hosted Server 2012 server visit www.zwiegnet.com/go today!

Related guides: Install Server 2012 Core | Enable Remote Powershell Access

Leave a Reply

Your email address will not be published. Required fields are marked *