How to Set Up Hyper-V in Windows 10 Insider Preview (Historical)

This historical guide combines the May 2015 Windows 10 preview articles on enabling Hyper-V and configuring its local host. Follow the workflow in order: check eligibility, enable the platform, connect Manager, then choose storage. Opening Manager alone does not establish that the PC can run virtual machines.

1. Establish which part of setup is missing

Record the host's Windows edition and build, whether Hyper-V has been enabled, and whether Windows has restarted since that change. On a managed PC, have the administrator authorize feature or firmware changes before proceeding.

2. Check eligibility before enabling the feature

For later Windows clients, Microsoft's installation guidance lists Windows 10/11 Pro or Enterprise; the full Hyper-V role is unavailable on Home. Hardware requirements include a 64-bit processor with SLAT, VM Monitor Mode extensions, firmware virtualization and hardware-enforced DEP. Plan for at least 4 GB RAM, with enough additional capacity for the host and the intended guests.

Inspect the requirements using this read-only command in Command Prompt:

systeminfo.exe

Read the Hyper-V requirement results individually. A No needs investigation of that particular prerequisite. If the report says a hypervisor is already detected, the usual requirement lines may be omitted; that is not a failed hardware test. Do not change unrelated firmware settings to make every field appear.

3. Enable Hyper-V and complete the restart

The original preview workflow used Start → Programs and Features → Turn Windows features on or off → Hyper-V → OK. Save open work and complete the requested restart. For local virtualization, distinguish the Hyper-V platform from its management tools.

Microsoft also documents this alternative for later eligible Windows clients. Use PowerShell as administrator, only if installation is needed:

Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All

Complete the restart when prompted. If installation fails, retain the exact error and Windows build before trying repairs. Repeating enablement commands is not a substitute for finding an edition, prerequisite or servicing problem.

4. Connect Manager to this computer

Search Start for Hyper-V Manager. If this PC is not listed, choose Connect to Server → Local computer → OK. Check the selected host name before changing settings; a console can manage another computer too.

If local connection fails, Microsoft's guidance distinguishes tools-only installation, hardware requirements and account permissions. In Services, look for Hyper-V Virtual Machine Management; its absence is a reason to check platform installation. Use an authorized Administrators or Hyper-V Administrators account. Do not enable remote management or relax remote authentication to solve a local-host selection problem.

5. Choose storage defaults without moving existing VMs

Select the local host and open Hyper-V Settings. Record both existing values before editing:

• Virtual Hard Disks: the default destination for new virtual disks.
• Virtual Machines: the default base location for new VM configuration data.

Keep the defaults unless a different location addresses an actual capacity or organization need. If changing them, use a stable, accessible drive with room for the planned workload, and apply the settings. A different drive letter alone does not establish better performance.

To undo a default-location change, restore the recorded host settings. Separately inspect any VM created during the interval: restoring defaults does not move that VM back.

6. Verify the result before installing a guest

On the selected host, open New → Virtual Machine. Review the proposed configuration location and the disk location in the wizard. You can cancel before Finish if you only want to inspect defaults. An explicit per-VM path can differ from the host default, so compare the actual proposed values.

When ready to create a VM, plan its guest OS/media, generation, memory, disk and networking using the current creation reference. Import an existing VM only as a separate, planned operation. For networking choices, see the Hyper-V virtual-switch guide. A visible host and correct storage paths verify setup choices; they do not prove that a guest boots or has network access.

Keep a short completion record: host/build → prerequisite result → feature installation/restart → local connection → original and selected paths → wizard verification. This makes a later failure easier to locate without reinstalling everything.

Documentation review: 2 November 2026. Combines the original enablement and setup workflows with clearly separated Microsoft references. No 2015 preview installation, firmware change or VM deployment was performed for this revision.

Official references