r/HyperV • • Aug 30 '21

Microsoft is discontinuing the free Hyper-V Server

74 Upvotes

In today's news, Microsoft is discontinuing the free Hyper-V Server product beginning with 2022. Here it is straight from the horse's mouth.

Microsoft Hyper-V Server 2019 is that's products last version and will continue to be supported under its lifecycle policy until January 2029. This will give customers many years to plan and transition to Azure Stack HCI**.**

*Credit to Gustav at Veeam.

https://techcommunity.microsoft.com/t5/windows-server-insiders/hyper-v-server-2022/m-p/2679949


r/HyperV • • Jul 24 '25

Ultimate Hyper-V Deployment Guide (v2)

70 Upvotes

The v2 deployment guide is finally finished, if anyone read my original article there was definitely a few things that could have been improved
Here is the old article, which you can still view
https://www.reddit.com/r/HyperV/comments/1dxqsdy/hyperv_deployment_guide_scvmm_gui/

Hopefully this helps anyone looking to get their cluster spun up to best practices, or as close as I think you can get, Microsoft dont quite have the best documentation for referencing things

Here is the new guide
https://blog.leaha.co.uk/2025/07/23/ultimate-hyper-v-deployment-guide/

Key improvements vs the original are:
Removal of SCVMM in place of WAC
Overhauled the networking
Physical hardware vs VMs for the guide
Removal of all LFBO teams
iSCSI networking improved
Changed the general order to improve the flow
Common cluster validation errors removed, solutions baked into the deployment for best practices
Physical switch configuration included

I am open to suggestions for tweaks and improvements, though there should be a practical reason with a focus on improving stability in mind, I know there are a few bits in there for how I like to do things and others have ways they prefer for some bits

Just to address a few things I suspect will get commented on

vSAN iSCSI Target
I dont have an enterprise SAN so I cant include documentation for this, and even if I did, I certainly dont have a few
So I included some info from the vSAN iSCSI setup as the principles for deploying iSCSI on any SAN is the same
And it would be a largely similar story if I used TrueNas, as I have the vSAN environment, I didnt setup TrueNas

4 NIC Deployment
Yes having live migration, management, cluster heart beat and VM traffic on one SET switch isnt ideal, though it will run fine and iSCSI needs to be separate
I also see customers having fewer NICs in smaller Hyper-V deployments and this setup has been more common

Storage
I know some people love S2D as a HCI approach, but having seen a lot of issues on environment customers have implemented, and several cluster failures on Azure Stack HCI, now Azure Local, deployed by Dell I am sticking with a hard recommendation against the use of it and so its not covered in this article

GUI
Yes, a lot of the steps can be done in PowerShell, the GUI was used to make the guide the most accessible, as most people are familiar with the desktop vs Server Core
Some bits were included with PowerShell as well as another option like the features because its a lot easier


r/HyperV • • Nov 13 '21

I made a Powershell script to automate the creation of GPU-P enabled Hyper-V VMs

66 Upvotes

https://github.com/jamesstringerparsec/Easy-GPU-P

I work for Parsec (high performance remote desktop app) and I have been following Windows GPU partitioning for a while, being able to share a GPU between multiple VM and Hosts has been my dream forever, NVIDIA GRID is expensive and buying a GPUs per VM is also expensive.

If you've used GPU-P before however, it's time consuming, from spinning up a VM, doing some trickery to copy driver files over, get your GPU's GUID and partition it correctly.

My goal with this project to make it as simple as proving an ISO, the name of the GPU you want to partition and what other resources you want to assign the VM - the script takes it from there and build and boot the VM, copy all the drivers and partition the GPU.

I needed Windows 11 to be able to do this (new Powershell APIs) so the requirements are Windows 11 on the hyper-v host as well as a Windows 11 ISO, along with an NVIDIA or Intel consumer GPUs with hardware video encoders (GTX / RTX NVIDIA GPUs, Intel HD Graphics and AMD dedicated GPUs from the last 5 years). Doesn't work with NVIDIA cards on laptops.

I also include Parsec, our remote desktop app which should be a great option for anyone who wants high performance access.

I'll improve this repo over time.


r/HyperV • • Aug 27 '25

Released: Microsoft’s VMware to HyperV converter

63 Upvotes

Saw this earlier and didn’t think to post here. Microsoft’s. Converter is now in preview. Hope it’s as fast as claimed.

https://learn.microsoft.com/en-us/windows-server/manage/windows-admin-center/use/migrate-vmware-to-hyper-v


r/HyperV • • Dec 03 '25

Looking for real world Hyper-v experiences.

51 Upvotes

So I just got my vmware renewal and I think Broadcom is smoking crack. Needless to say, I am looking at ESXi alternatives. I currently manage three datacenters across our campus. We own Pure Flasharrays for storage and Cisco UCSx M7 blade servers. We manage about 1000 vms.

Here is my question...is Hyper-v a real/reliable replacement for enterprise? I used it (on a single host) about 10-12 years ago in a lab, and it worked fine but it wasnt production/ nobody was really relying on it. I keep hearing horror stories about Hyper-v, but would really like some real-world reviews.

Thanks in advance!


r/HyperV • • Nov 19 '25

New Windows Admin Center vMode for managing Hyper-V Servers

49 Upvotes

r/HyperV • • Feb 11 '26

Hyperv is a concrete possibility?

47 Upvotes

Hi all, at my company we have about 200 VMs on esxi, we are evaluating an exit strategy, my colleague that uses HV 10 years ago says that is not a good options because is not stable, full of issue etc. Is this true? What the state of this product nowadays? I've experience only in VMware virtualization Thanks


r/HyperV • • Aug 15 '26

Hyper-V Manager now lets you set the number of vCPUs when creating a VM

46 Upvotes

Hey it seems MS took at least one suggestion out of https://www.reddit.com/r/HyperV/comments/1o9siyz/comment/nk83qgb/ . It's the smallest QoL fix ever but who would have expected we would get an update 😄

Found this on Windows Insider builds (29639.1000), you can enable it with the following but it'll likely come in the next release or something:

.\ViVeTool.exe /enable /id:55721547


r/HyperV • • Jun 23 '25

A (not-so) Short Guide on (quick and dirty) Hyper-V Networking with SC VMM

46 Upvotes

A lot of people are starting to deploy Hyper-V these days because, well, we all know why. And in the last few years there have been some really good questions about how to setup the networking properly. But nearly all of those posts and comments refer to doing it manually on the host with PowerShell. But this is going to be about how to do this with VMM.

There are almost NO good guides or videos on any of this, and most videos on Hyper-V networking are just flat out wrong, bad or just plain irrelevant nowadays.

Just like any System Center product, it takes time to learn the ropes in VMM. This is going to be a lot of information, and will be incomplete, but it's a good start for most. I have been wanting to post a good guide for some time now on this sub for how to get VMM networking configured. I intended to write this as a comment in response to u/eagle6705 question about vlans in VMM. But this is long and reddit said it couldn't comment. I think there is a character limit for comments, so I decided to just make a new post. This is topic is where VMM becomes a bit weird, and where most people give up on it because they can't wrap their minds around it.

There are 4 critical pieces in VMM that need to be configured. I've been doing this a long time and even I have to click around these pieces to link everything up correctly.

There will be A LOT of trial and error here when trying to decide how you want to break things out for networking. But start thinking about your deployment in terms of being a "virtualization tenant" like Azure or AWS, and it will start to make a lot more sense on why it's built this complicated way.

First, create and organize Host Groups (in VMs and Services, Host Groups are the folders you see there, the root is "All Hosts") to break out your clusters or branch offices, if applicable. If you ever want to scope areas to certain vlans, a good host group structure is critical.

Next, in Fabric, you need to create a Logical Network. There are several combinations you can make, and they aren't really clear on which is best suited for your needs. But know this, for simple deployments, where you and your team are the only admins for VMs, maybe start with a "Connected Network". Use "Independent Network" if you want to delegate VM creation to other teams AND you want to restrict what vlans those teams can select. You can delegate VM management with Connected Networks, but you get less networking flexibility. The third type is Virtualized Network, where you are utilizing FULL SDN capabilities, and that is an entirely different beast.

I am only going to quickly walk though creating a Connected Network.

When creating the Logical Network, create a "Network Site." This is where you actually group vlans together. Sometimes you create a site for each branch office, or a different site for vlans used only for Hyper-V hosts or even things like VDI. For Connected Network, break it out however you want. But I will mention you shoud put the vlans that are meant for Host connectivity in their own Logical Network and likewise, its own VM Network. (I mention this almost every time someone asks about Hyper-V networking; ALWAYS make separate vlans for your hosts: one for management, one for live migrations, and one for inter-cluster communication.) When you select a site, you need to add the vlans there. Click Insert Row and enter the vlan ID for each row, also don't forget to check the checkbox on each Host Group that you want to use the Network Site. This is easily missed, if you don't select host groups, the hosts there cannot use them. Also, if you are not using the IP Pools feature, then completely ignore the "IP subnet" column when adding vlans.

Next, you need to create a Port Profile. Think of these like configurations on ports on a switch. There are two types, "Virtual Network Adapters" and "Uplinks".

Create an Uplink for your hosts that defines the kind of bond they will have and how to load balance traffic across the uplink ports. The "Host Default" for Server 2016 and above is "Dynamic", but I'm just going to tell you to select Hyper-V Port every time. Here is why; one VERY important note about the LB Algorithm in Hyper-V, is that IF YOU EVER want to put VMs behind a load balancer, the LB algorithm MUST be "Hyper-V Port." I don't remember the exact reason for this, but I think it's because how traffic goes TO and RETURNS FROM a VM on the host can come back on via a different port. Traffic that goes through a load balancers have issues with that. The new algorithms break connections to VMs that are from a load balancer.

You now select which Network Sites, the Uplink port profile has access to, which (because of previous choices made when making the sites) in turn allows hosts in the select it.

Next, we create the Logical Switch. The name you give this switch will be the name of the Switch on the Host. (IF you created a switch manually on the host beforehand and you want to "convert" it, the NAME MUST MATCH EXACTLY). Select "Embedded Team" uplink mode and go through the wizard. Once you get to the "Virtual Port" section, this is where it gets weird. What you are doing here is defining what virtual adapters will be created on the host for its own connectivity. You will need at least "Host management", "Live migration" and "Cluster", and select the corresponding Port Classification. (This is only for "classifying" there are no settings associated with them.) What you are adding here are "Virtual Network Adapter" Port Profiles that should already exist by default. If they don't exist, go create them, or even better, make your own with your own specifications. Settings for those enable things like IPsec, RDMA, VMQ, SR-IOV, and vRSS etc. Personally, I wouldn't modify the built-in profiles if you need different settings. Make your own.

Now finally, go back to VMs and Services, find "VM Networks" and create two, one should be for host vlans Logical Network, the other one using the Logical Network with vlans for VMs. It's hard for me to write this part out right now because so far, I have been going through my own environment, but the Isolation setting when creating a VM Network is done only at creation, and you can't create one without an available Logical Network to assign to it. I can't even go look at the properties to see what I selected. However, this is the doc that might help make the choice that's right for you, but chances are, you will want 'no isolation'. https://learn.microsoft.com/en-us/system-center/vmm/network-virtual?view=sc-vmm-2025

Now, we're at the fun part, go to a host that is in a Host group scoped to your Logical Network. Open properties and selected Virtual Switches. If you created a switch manually on the host, it should appear as a "Standard" switch, and if you did everything correctly, I'm pretty sure at this point, there is a button you can click to convert/merge it with a VMM Logical Switch.

If not, then add a new switch, select the logical switch from the drop-down menu, add the physical adapters you want, and select the Uplink Port Profile that we created. In the lower area, you should also see the list of virtual network adapters that will be created as well as a checkbox to indicate which adapter will be the management interface that will inherit the host current network settings.

The reason for this is because in Hyper-V you should only need two physical interfaces, 10G or better, and when you bond those interfaces together you are probably using one already for temporary connectivity to get it added to the domain and joined to VMM. Selecting that box will make sure that after the adapter is taken as part of the team, the IP, MAC address etc. are then cloned to the newly created host management virtual adapter to maintain connectivity with VMM. After the "Job" is run, VMM will lose connectivity momentarily while the agent does some work, and when the job completes, you can go into the Host Properties again and select which vlans the host adapters will be on.

This should be a good start for a first deployment. Maybe someday I'll do a video or blog post with images but I'm a bit lazy these days.


r/HyperV • • Jan 13 '26

Hyper-V "got ya's" for newbies

43 Upvotes

We get a lot of clearly new admins asking questions here. Let's make a thread of things that sound good to a newbie but are dangerous.

  1. ReFS has a lot of cool features, but a lot of bugs. Don't use it unless you absolutely need a feature from it. NTFS is good for most purposes.

  2. Networking, walk before you run. Start simple with a virtual switch hooked up to your primary ethernet. Save multi-WAN, dedicated hardware bindings, and such for later.


r/HyperV • • May 26 '15

Hyper-V’s Biggest Weakness

Thumbnail
petri.com
42 Upvotes

r/HyperV • • Sep 01 '26

Hyper-V Environment Report

Post image
41 Upvotes

For a long time, I used the PowerShell script “get-HyperVReport” to quickly get an overview of my Hyper-V clusters in HTML format. Unfortunately, this script no longer worked properly on Windows Server 2022 and 2025.

Since I didn’t want to do without the reports, I forked the script and fixed the bugs I was aware of.

Maybe the revised script will be helpful to some of you:
https://github.com/martin-zh/Get-HyperVReport


r/HyperV • • Mar 29 '25

Hyper-V health value of 5 on Windows Server 2025

Post image
39 Upvotes

Cheers guys, first post here. I hope to come back and blow your mind in the future with great help, but for now I need the help.

I am working on a little stats page for Hyper-V (just for fun, nothing serious). It will be on github soon, but one thing is stopping me.

For some reason I am getting a health value of 5 on one of my Hyper-V hosts running Windows Server 2025. This is observed when gathering the performance counter object for Hyper-V health known asHyper-V Virtual Machine Health Summary\Health Ok.

## Example syntax

typeperf "Hyper-V Virtual Machine Health Summary\Health Ok"

Note: I am aware that the value mappings changed sinceWindows Server 2022, where previously a value of 16 was used to indicate healthy.

The valid values for Windows Server 2025 I have figured out thus far:

ValueDescription
0Health Okay
1Health Okay
2Warning
3Critical

## Question

What does a value of 5 mean for Hyper-V Virtual Machine Health Summary\Health Ok on Windows Server 2025?


r/HyperV • • Nov 03 '24

Hyper-V Windows Network Adapter is going crazy with chinese characters in name

38 Upvotes

Hyper-V is going crazy ... whats happen here?


r/HyperV • • Feb 13 '24

Regarding the discontinued Hyper-V Server and the future of Hyper-V environments

38 Upvotes

Hi,

I am looking at our options after the changes with VMWare licensing and obviously I don't even want to consider a dying platform.

But I am a little confused about the implications that Microsoft is not moving forward with Hyper-V Server (ending with 2019, with support ending 2029). I'm sure this is bad news for home labs, but don't all Windows Server Standard licenses come with one Hypervisor license and two Virtual Server licenses? And Datacenter obviously includes unlimited instances. So it seems to me that nothing changes in the enterprise, because you can just install Server Core with the Hyper-V Role on any host server.

In the posts that talk about this, I mostly see people suggest Proxmox or XCP-NG. Or do what Microsoft is clearly pushing and go to Azure Stack HCI, with a monthly subscription cost that quickly exceeds even VMWare. Am I missing something?


r/HyperV • • Apr 21 '26

Windows Admin Center Virtualization Mode – Public Preview 2 is out

37 Upvotes

Microsoft announced that Windows Admin Center’s Virtualization Mode (vMode) Public Preview 2 availability:
https://techcommunity.microsoft.com/blog/windows-admin-center-blog/announcing-windows-admin-center-virtualization-mode-public-preview-2/4508937

I will deploy it in a test environment and share my thoughts later.


r/HyperV • • Mar 04 '26

VMware to Hyper-V

37 Upvotes

Lately it seems to me some pretty hardcore VMware customers are trying to migrate to Hyper-V, with Windows 2025 standard server and, or Datacenter. Am I reading into this properly without seeing any numbers to back this claim up.


r/HyperV • • Apr 30 '24

Why Microsoft didn't add USB passthrough to the hypervisor?

37 Upvotes

I've come across numerous resources detailing how Hyper-V doesn't currently support USB device passthrough, but there's a lack of information on whether it might support it in the future.

Is there a possibility of Microsoft implementing this feature? Is it simply not a priority for them, or are there technical barriers within the structure of Hyper-V as a hosted hypervisor that make it challenging to enable?

It's worth noting that other Windows-based hypervisors are capable of USB passthrough.


r/HyperV • • Jul 28 '22

Free Training on the New Microsoft AZ-800 (Administering Windows Server Hybrid Core Infrastructure) Course

37 Upvotes

Howdy everyone

Hope this helps some folks who are in need of some study material for the new Microsoft AZ-800 course which covers Server 2022 and Azure amongst things.

I created free lessons covering this course which will hopefully helps some people out. I know the feeling of looking for study material and not being able to find any or not being able to afford any especially if your boss/company is forcing to write a exam. Maybe this will help relieve some of that stress. You don't have to pay me anything for this, the wife says it's keeps me out of trouble lol.

Anyway here you go, course is below

Microsoft AZ-800 (Administering Windows Server Hybrid Core Infrastructure) Course


r/HyperV • • Jul 02 '22

Windows Server 2022 GPU-P Virtualization working guide

37 Upvotes

Hey guys, after spending a week testing and failing, I've finally managed virtualise my GTX1060 into a Win Server 22 Hyper-V VM. The guide below assumes you already have Hyper-V role and have a basic understanding of GPU virtualization, and it's limitations. Let's get right into it:

  1. Install windows server 22 host, and update to latest build, install Hyper-V Role.

(21H2, OS Build: 20348.803 or later / Cumulative update KB5014665)

2. We'll be using Jamesstringerparsec Easy-GPU-PV's guide with a few tweaks, so download and extract the package to a folder.

GitHub - jamesstringerparsec/Easy-GPU-PV: A Project dedicated to making GPU Partitioning on Windows easier!

3. Run powershell ISE as an admin and set Execution policy to unrestricted

Set-ExecutionPolicy -ExecutionPolicy Unrestricted -force

4. Once done, go to File> Open > and open CopyFilesToVM.ps1

5. Firstly, modify the script to add your server info. Take a look at the Github values to understand what each settings does and which should not be changed. The settings are made with Win10/11 in mind. Below are the settings that must be changed to work with WinServer:

•Edition = to find out the number for your Windows edition, open a separate powershell window and run the following script after mounting your Server ISO to a drive letter:

dism /get-wiminfo /wimfile:<Drive Letter>:\sources\install.wim

Once you run the command there will be an index number for every windows version available. Choose your specific version and set that number as the Edition Value.

•GPUName = Leave as auto if the GPU you are virtualising is the only one available.

6. Once this is done, run the script. It should go through the creating on the VM, but will fail when trying to launch it. In my case, the error was somewhere along the lines of:

GPU Partition (Instance ID 69E7E377-A066-41D6-A03B-E610AC30DAA6): Failed to Power on with Error

'.'.Insufficient system resources exist to complete the requested service

'WS22PLEX' failed to start. (Virtual machine ID CAED9896-6895-4541-AC43-B25856D3B385)

'WS22PLEX' GPU Partition (Instance ID 69E7E377-A066-41D6-A03B-E610AC30DAA6): Failed to Power on with Error

'Insufficient system resources exist to complete the requested service.' (0x800705AA). (Virtual machine ID

CAED9896-6895-4541-AC43-B25856D3B385)

Could not allocate a GPU partition as no GPU devices are compliant with currently set group policy. See

HyperV\RequireSecureDeviceAssignment and HyperV\RequireSupportedDeviceAssignment for more details.

To get around this, you need to create 2 keys in Reg edit.

  1. HKLM:\SOFTWARE\Policies\Microsoft\Windows\HyperV" -Name "RequireSecureDeviceAssignment" -Type DWORD -Value 0

  2. HKLM:\SOFTWARE\Policies\Microsoft\Windows\HyperV" -Name "RequireSupportedDeviceAssignment" -Type DWORD -Value 0

  3. I closed off MMC.exe from Task Manager before attempting to run the VM again.

Try to launch the VM again by running the following command in Powershell: Start-VM Server123

(Replace "Server123" with your recently created guest server name).

Your server should now boot up with no error. I installed drivers in the guest and tested by running a 4K youtube video, and watched the resource spike up on the host machine's task manager.

Notes:

• Make sure that you install GPU drivers on the host machine before doing any of the above.

• Make sure to install GPU drivers on the guest VM when after creation and booting into it.

• Normally, GPU resources are not visible in the guest VM.

• Check Device manager to make sure the GPU shows up and is enabled. If it isn't, you need to extract the drivers from the host machine and re-assign them to the VM. The link below should help: GPU Virtualization with Hyper-V – James' Personal Site (mu0.cc) , and possibly GPU Virtualization with Hyper-V – James' Personal Site (mu0.cc)

I'm not a very active user so getting back to comments may not be as quick as some would expect, but please do leave any issues, queries or observations in the comments so that other could potentially assist if I don't get back to you in time.

Please also feel free to start discussions on the comments, just try not to get off topic to make it easier for others to find answers for questions they may be looking for.


r/HyperV • • Jun 13 '25

Migrating from VMware to Hyper-V,

36 Upvotes

Hello everyone,

I'm looking for some advice on our organisation's virtualisation strategy. We're currently using VMware, but we're considering several options moving forward. Here's a quick overview of our current setup and the options we're exploring:

Current Setup:

  • vCentre Server 7 Standard

  • vSphere 7 Enterprise Plus for 6 Dell PowerEdge R640 servers

  • vSphere 7 Enterprise for 2 Cisco UCSC-C220-M6S servers

  • vSphere 8 Enterprise for 2 additional Dell servers

Multiple Networks and segments

  1. Migrate to Hyper-V

    • Pros: Integration with Microsoft products, potential cost savings As we are an education based environment we get significant savings on Microsoft

    • Cons: Migration complexity, learning curve

What We're Looking For:

  • Cost Efficiency: Balancing initial investment and long-term savings

  • Scalability: Ability to grow with our needs

  • Ease of Management: Simplifying operations and reducing complexity

  • Innovation: Access to new technologies and features

I'd love to hear from anyone who has experience with these platforms. What have been your experiences, and what would you recommend based on our needs? Any insights or advice would be greatly appreciated!

Thanks in advance!


r/HyperV • • Dec 14 '24

Error message when launching Hyper-V Quick Create on Windows 11 Pro 24H2 26120.2702

35 Upvotes

I'm getting the following error message:

Could not load file or assembly 'Newtonsoft.Json, Version=12.0.0.0,

Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its

dependencies. The located assembly's manifest definition does not

match the assembly reference. (Exception from HRESULT:

0x80131040)

Any idea how to rectify this? I've never seen this before.


r/HyperV • • Feb 01 '24

Windows Server 2025 Hyper-V & Storage updates

34 Upvotes

I made a summary of all Hyper-V & Storage updates coming in Windows Server 2025.
Might be useful for anyone already on Hyper-V or compilating on migrating.

• Windows Server vNext delivers 90% more IOPS on NVMe SSDs.

• NVMe over Fabric (NVMe-oF) support.

• Storage Replica 3x performance improvement.

• Thin Provisioned storage.

• Stretched Clustering support for Storage Spaces Direct (S2D).

• Certificate-based VM Live migration for AD-less cluster.

• Cluster Aware Updating enhancements to make it more resilient.

• GPU-P support for Hyper-V including support for Live Migration.

• NetworkATC support for Windows Server.

• New ReFS native deduplication and compression, optimized for hot-data such as virtual machines.

Microsoft plans to offer Windows Server 2025 on both perpetual-license and pay-as-you-go subscription bases via Azure Arc.

Download and preview license keys available here: https://techcommunity.microsoft.com/t5/windows-server-insiders/announcing-windows-server-preview-build-25206/m-p/3634220


r/HyperV • • Mar 23 '26

Moving from VMware vSphere to Hyper-V

32 Upvotes

I have been tasked with moving our two Dell PowerEdge R740 from vSphere to a Hyper-V cluster, and I am not sure if I can do this without a staging server. Maybe move all the VMs to one server host then. Remove the other server host and set it up as a Hyper-V host, then migrate the servers to Hyper VMs. After bringing the other server host to Hyper-V and making a cluster, then. Had anyone done this before?

Edit: I have learned that the two hosts are not currently in a cluster, and both are almost maxed out