Hyper-V is a native hypervisor; it can create virtual machines on x86-64 systems and supersedes Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks. Hyper-V Server supports remote access via Remote Desktop Connection. Administration and configuration of the host OS and the guest virtual machines is generally done over the network.

Share tech news, updates, or what's on your mind.

Sign up to Post


We have problems with Microsoft Definition Updates on Windows 7 Clients. According to Woody there is a problem:

Error 1
Error 2
All physical devices are affected. Are you also affected? Are there any workarounds?

Hyper-V running out of space. In my physical server's hard drive I have the following:
D:\hyper-V\SQLHYPERV\Virtual Hard Disks\SQLHYPERV which is a Hard Disk Image File and it is 717,131,776 kb

The Physical D drive is only 917GB. Is there anyway to shrink this file?  Or is there anything I can do to free up space or stop it from running out of space.
The physical server is running windows server 2012R2 with 4 600gb SAS drives in a raid-10 configuration so I'm only getting a little less over 11gb total space.
I have a 200GB C: boot/windows drive and the balance of about 917GB on D: drive.
I have 173GB free on C: and 130GB free on D: drive.

I'm running two Hyper-Vs on the one physical server. SQLhyper is using 685GB and APPShyper is using 100GB.
I've been running these hyper-Vs for just over three years with no problem.
Is it possible that I have a setting wrong. Any help would be greatly appreciated.

I know I'm going to need larger drives but that is not easy to do with a raid-10 configuration. I need a fix for now until we can find the time to
replace or add more drives.
How do I remove the snapshots on a hyper-v. Can not edit the disk because- Edit is not available because checkpoints exist for this virtual machine.
I inadvertently removed the virtual switch on a Hyper-V installation.  I installed another one, but the virtual machines cannot start.  Is there a method to restore the virtual switch on the server.  The )S is Server 2016 Standard.  The server is a Lenovo TS550

I have a Dell PowerEdge R430 server with Broadcom Network Adapter, Server 2012 R2 OS.
I am unable to ping or remote to the physical server, but strangely the VMs hosted on it are fine and I can reach them.

Any idea as to the cause and possible solutions?
Is there a stripped down windows 10 solution ideal for virtualization?  Either a premade image or legit and safe software to make a lite ISO using an original media?  I see lots of stuff on the internet but much of it looks suspect. I also see one by microsoft, but it's actually preloaded for development and kind of the opposite of that I am looking for.
I have a VM (Windows Server 2016 R2) created from a Hyper-V server running NIC Teaming. The server in question can see the internal network on its virtual NIC but cannot surf the Internet no matter how I configure the NIC. Even when I add other virtual NIC's to the server, I still can't get to the Internet. The NIC reads 'unknown network'. All other VM servers on this same Hyper-V server and using the same NIC Teaming works fine and can connect to the Internet.
I'm trying to test a Live migration between clustered Hyper-V Hosts and each time i try i get the following error

Live migration of 'Virtual Machine NPCARDAX' failed.

Virtual machine migration operation for 'NPCARDAX' failed at migration destination 'NPMPVH04'. (Virtual machine ID 20916DA3-F57D-4DA4-80C9-9B700EC3D5F2)

The virtual machine 'NPCARDAX' is using processor-specific features not supported on physical computer 'NPMPVH04'. To allow for migration of this virtual machine to physical computers with different processors, modify the virtual machine settings to limit the processor features used by the virtual machine. (Virtual machine ID 20916DA3-F57D-4DA4-80C9-9B700EC3D5F2)

I can confirm i have ticket the Processor compatibility box under cpu settings, both servers are HP DL360 Gen10 that were purchased at the same time and are both Dual CPU

I am "cleaning up" a messy VM in Hyper-V 2016 (on Server 2016 STD), it is a "Generation 2",

It has server checkpoints but some are not giving the option to be deleted in order to merge them with the .vhdx of the VM.

The icons of the checkpoints are remarkably different to the standard Checkpoints, any one knows what these different icons means? See three blue arrows pointing to them and I highlighted the last one in yellow...

Funny Checkpoints
I need to get rid of these checkpoints but never seen these different ones that cannot be deleted.

Thanks for any assistance.

I have a 3 nodes HyperV HA Cluster, with Starwind storage.
One of the main vm's is a SQL Server 2016, which i would like to have working in a "Always On Availability Group"
I thought it would be a matter of just adding a new SQL vm in another node and set it as replica, but while trying to install, i see SQL Server needs it's own cluster to work this way.
How can i install it in this scenario?

I would like to learn about virtualization. I'm thinking about purchasing a Type 1 virtualization software, for home use. Any good recommendations?
Also, can anyone point me to some good learning resources (books, websites, etc.)?
Hello everyone, I am hoping someone might be able to help with an odd NLB issue we seem to be experiencing on our ADFS farm setup. This environment has been setup for at least a year and this issue could have been going on for a while without being noticed. Both servers are Hyper-V guests with two network cards attached and MAC Spoofing enabled on the second NIC (Cluster Operation Mode Unicast). The issue that we are having is that we are able to add ADFS-1 to the cluster with no issues, however when we add AFDS-2 into the cluster the Network Location Awareness (NLA) changes from Domain Network to Public Network (Images below). No errors are displayed as it joins the cluster, but the NLB NIC is no longer reachable on the network.

Host NIC: x.x.x.33
NLB NIC: x.x.x.151
NLB VIP: x.x.x.150

Host NIC: x.x.x.10
NLB NIC: x.x.x.152 (Unreachable after Joining to cluster)
NLB VIP: x.x.x.150

Before NLB Join
After NLB Join
I have already verified the IP configurations before and after the addition to the cluster and restarted NLA, and nothing has changed. When you drop the NIC from the cluster it returns to its normal state of Domain Network. I have also deleted the cluster completely and rejoin the servers in a different order but the same server/same NIC does the exact same thing. Anybody Expert ideas on where to go next?
Is there anyone able to provide a download link for the (free) hyper-v core server 2019?
Microsoft has wrong links below https://www.microsoft.com/en-us/evalcenter/evaluate-hyper-v-server-2019 - those point to hyper-v-server 2012 R2! *
https://software-download.microsoft.com/download/pr/17763.1.180914-1434.rs5_release_SERVERHYPERCORE_OEM_X64FRE_EN-US.ISO is mentioned elsewhere on the net, however the setup is defective (no, not my download, the setup itself is faulty).

* LOL! In this very minute, the links were corrected, however, still, they only lead to https://cloudblogs.microsoft.com/windowsserver/2018/11/13/update-on-windows-server-2019-availability/ which leads back to 2012 R2
My Hyper-V Host is running Windows Server 2012 R2 Datacenter, and on here I have about 15 VMs.

I just purchased a Windows Server 2019 Datacenter license. I'm ready to start creating 2019 VMs but I am not ready to rebuild the host with Server 2019. Is that a requirement for activating VMs running Server 2019? I believe best practice is to install Server 2019 Datacenter on the host, activate it using the unique activation key; then, any VMs I create on that host are activated using AVMA (Automatic Virtual Machine Activation) https://docs.microsoft.com/en-us/windows-server/get-started-19/vm-activation-19

But in my scenario, the host is running Datacenter 2012 R2. My plan was to (one at a time) start creating VMs running 2019 to replace the older VMs running 2012. (For example, I have a file server VM running 2012. I am going to create a new VM running 2019, configure it the same was as my 2012 VM and then decommission (delete) the 2012 VM). The end result is that one at a time, the VMs get replaced with new VMs. But the host (at least for now) will continue running 2012.

Is there another way to activate the VMs when the host is not running the first 2019 Datacenter instance? Can I create my first 2019 server as a VM and use that VM as the 'server' from where all of the other VMs are activated using AVMA? Or does AVMA only work if it can authenticate (activate) against a host that is ALREADY running (and activated) with 2019 datacenter? I am probably…
We would like to buy new server for our application but not too sure how the license works

OS:window server 2016 standard
Processor : 2 x 16(cores)
VM Host :Window server 2016
VM guest: 4 x window server 2016
We are considering moving to Hyper-V from ESX, but that could be up to 1 yr in the future. In the meantime, I want to create my VMs in a way that is easy to move.

In this case we are reviewing the use of Win 2016 Datacenter vs. Standard. We will definitely be using Datacenter for the Hyper-V host, but have questions about the guest OS to use.
Many of the additional features of Datacenter seem to be focused on using it as the Hyper-V server

1. If we use Standard as the guest OS will we lose access to any of the additional Datacenter features
2. Does Datacenter use significantly more resources than Standard?
3. Does Datacenter licensing apply to all guests even if they are Standard?
HYPER-V Host capactiy - VM capacity (Windows Server 2012)

I have a Host Server with 16 Cores- 32 processors, 128GB Memory and 1TB Storage.  

I have a request for a new VM to be created on this server with the exact same spec as the host has.  There will be only 1 vm on this server.

Realistically what is the most that I can allocate to the new vm, taking into account the requirements of the host server ie. cores, memory, checkpoint storage, harddrive etc.

Thank you
SBS2011 VM Memory Usage

  I converted a physical SBS2011 server as a virtual machine in Hyper-V server. A standalone SBS2011 had 24GB of RAM and I assigned the same amount when creating a virtual machine for it.
  Recently we migrated Exchange from SBS to Online and I disabled all Exchange related services in Services.msc.
  Do I still need to assign 24GB of RAM for this virtual machine? Sharepoint is probably still running in the background although we don't use it.


I need to replace a six year old Dell Poweredge T620 server.  I was thinking about replacing it with another Poweredge T630, with this CPU:  Intel® Xeon® E5-2630 v4 2.2GHz,25M Cache,8.0 GT/s QPI,Turbo,HT,10C/20T (85W) Max Mem 2133MHz.  I want to use Hyper-V but I'm not sure if I should use RAID or if there really is a big enough performance advantage for the extra cost.  I was thinking about going RAID10 using the PERC H730 RAID Controller with 1GB NV Cache but is that a good idea to have the VHDX and host all on the same RAID10?

Would there be performance problems if I just had two stand alone SSDs?  One would have the host Windows Server 2019 and the VMs would be on the second SSD.  I understand that the speed difference between stand along drives and RAID10 (with 4 drives) is 4 times faster the read and 2 times the write.  But with the SSDs being so fast now, is it necessary to go with RAID10 for a small office?  I will be running an Active Directory/Application VM and a Remote Desktop VM.  There are a total of 15 users and 5 of them will occasional work on the Remote Desktop VM.  Thanks in advance for any and all suggestions, recommendations and criticisms!
Installing Exchange on a VM and installed the .NET4.7 and C++ prerequesits. Server's been sitting at "Getting Windows ready, don't turn off your computer" for over an hour. Both VM's took awhile longer to install updates after installation but nothing like this. Any ideas? Don't have much choice but to leave it. Sadly I'm reading allot online where 2016 Server has serious update issues.
My organization currently has a physical server with 256gb RAM and 2 x 4tb internal Intel P4500 SSD cards. It's a Hyper-V host and all of the VMs live on the internal SSD cards. Performance is great but I'm exploring options for expanding our storage.

Rather than having all of the storage within the server box, one obvious alternative is a SAN. But the SAN configurations I'm looking at are over $30,000. Boooo.

It seems like NAS devices are getting a lot more powerful, robust and (with Flash drives) faster.

So my question: Is it feasible to load up a Synology with Solid State drives (or a hybrid combination), connect it directly to the server and then run all of the VMs off of there? And would it be best to connect using dual 10GbE direct Ethernet connections and iSCSI?

I fully understand a NAS is not a SAN. I am trying to consider in-between solutions. I know how my VMs run with internal storage. I know how my VMs will run on a SAN. But what if I ran all of my VMs on a NAS? (the SAN solution I am looking at blows away my current solution as far as IOPS so I might even say a SAN is overkill. With my current solution we are not experiencing any latency or speed issues)

Another question - if this is feasible, then would I be able to connect TWO or THREE servers to the NAS and have them all share the same NAS volume?

White papers or actual real-world examples would be great.
How to increase drive size of a VM in Hyper-V manager? Windows 2012 Server. Went into SETTINGS of Hyper-V Manger for the VM while the VM is shut down. Then IDE Controller (name of VM.vhdx. Clicked EDIT in the Virtual Hard Disk that is radial selected and chose EXPAND. Put in the desired new size and clicked finish. Did this over 30 days ago and the disk size in the VM never expanded. Is there a post process command I need to do or do I have to wait a while while the VM is shut down for the dish to expand to desired new input size? Thanks
My customer formatted a CSV (Clustered shared Volume).
Now I need to recover a VHDx file from that .
is it possible to recover VHDx?

I have a exchange 2013 server as a VM in Hyper-V, Server 2012R2, that I had a issue with several months ago. My Backup Exec 16 -the full version was backing it up and by default it creates a checkpoint to speedup the backup (this can be disabled and I have now). The issue was several more checkpoints 4 of them were created possibly by backup errors and I started to loose drive space. Well I worked with Microsoft to roll all the checkpoints in the right order in to one .VHDX and all I have is one file now with no checkpoints which is how I want it. I don't like using checkpoints for obvious reasons, better to have a good backup or an export than create a differencing disk.

My issue is that in hyper-v manager 2 of the old checkpoints are still listed and I cant get rid of them See pics.

This is causing a Issue with backup exec were I cant do a virtual based backup because Backup exec thinks the exchange VHDK is corrupted.
I can do a agent backup but this is not the best way to backup exchange.

I still have the old checkpoints saved, but like I said they have been already rolled in so I don't want to put them back where hyper-v can find them, and have the delete checkpoint roll them in again. Seems like that would cause a problem.

Its almost like I have some old configuration data some were in Hyper-V

Any ideas on how to get rid of these old checkpoints?

Old checkpoints
cant delete
I have the following error message on my Hyper-V host event log.Just wanted to find out this is something to do with the Raid driver ?

An error was detected on device \Device\Harddisk2\DR2 during a paging operation.Event ID 51


Hyper-V is a native hypervisor; it can create virtual machines on x86-64 systems and supersedes Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks. Hyper-V Server supports remote access via Remote Desktop Connection. Administration and configuration of the host OS and the guest virtual machines is generally done over the network.