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

I set up 3 Windows Server 2019 Standard systems.  
On each machine, the first OS install was set up as a Hyper-V manager.  
The second (VM) OS install was a Server VM for a DC.  
I plan on a 3rd VM OS install for a Server VM perhaps for file serving - yet TBD.

I've been in and out of these machines fairly regularly but have been away from them for the last month.
Now, it appears, none of the VMs will boot - not on any of the 3 systems.
The VMs had been running but I believe I encountered them today Stopped.
(The Hyper-V systems were running).
And, oh yes, there was a power outage a few days ago.  But I did try to take down the systems gracefully.
So that's probably why the VMs weren't running.
And, maybe the power cycle triggered an update.

Anyway, The message says that a boot device wasn't found and seems to go to PXE.
Then it suggests that the VM be configured.

I have a bit of investment in the configurations but haven't yet reached the point where I've set up the backups.
I'd like to keep them as-is.

What is the recommended procedure to get these VMs booting?
From what I've read, it seems to be possible but most things I've seen seem rather tentative or on a slightly different issue.

On a slightly different subject, why the heck did I decide on VMs IF the 3rd install is still tentative?  
This doesn't seem robust enough for real time.
Announcing the Winners!
LVL 13
Announcing the Winners!

The results are in for the 15th Annual Expert Awards! Congratulations to the winners, and thank you to everyone who participated in the nominations. We are so grateful for the valuable contributions experts make on a daily basis. Click to read more about this year’s recipients!

Black screen with Hyper V-2012

Cannot boot into any version of safe mode or last known good configuration (no error just black screen remains)

Any ideas on this tried below, would be great to hear from someone who has got this working without having to reinstall
I have used vCheck before found it fine, just wondering from a scripting point of view whats a good way to automate morning checks for say 40-50 customers

What are the options?

Any open source options available?

Much appreciated , would be great if someone had done something similar themselves and had first hand experience
Hi all and happy Sysadmin Day!

I have a hyper-v 2012 R2 host. I'm backing up one of the VMs and noticed that Veeam is only backing up the C: VHD disk, it's not backing up the other VHD disk which is H:
what could I look at to determine why it's not backing up the 2nd VHD disk on this VM?

 I have a Hyper-V virtual machine "TS3" running Windows Server 2008 with 278GB space allocated, but only using 100GB of space.

So I wanted to shrink the VHDX size. When I ran "Shrink" option in Disk Mgmt.msc, I got an error "Access denied".

I tried different suggestions on Google, but to no avail. So I ran Disk2VHD in TS3 and it created 72GB VHDX file.
Then I created a new VM "TS3 - VHDX" using existing 72GB VHDX file. But when I fired up the new VM, it still shows that hard drive size is 278GB in "My Computer".

Furthermore, when I tried to shrink it using DiskMgmt.msc, I still get "Access denied"error.
I don't mind seeing 278GB in "My Computer" of the VM as long as real size of VHDX is till 72GB.

My objective is to reduce the VHDX file and free up overall hard drive space on HyperV server.
But I am curious why the VM would not display current HD size based on VHDX file size?
Core 2016 Hyper-V with VM DC, network adaptor showing no IP address. The hyper V management console will no longer connect from my workstation. It is the only DC in our network which is just a few computers. I can see the machine is running on the host but the IP address is showing as {}

Is there a way I can set the IP address of the adaptor on the host? All searches on Google say it should be done from the Management console.
I want to setup a Hyper-V virtual server on a Server 2012 or 2016.  My understanding is that they both allow for 2 VM licenses.  Do these licenses include the server license to install on the VM.  Do you use the same product key as the server.  Having a difficult time finding the information on the Hyper-V licensing.  Seems like there are many different opinions on what is included and how it all works.
Any help would be appreciated.
I am running Hyper-V with 6 virtual machines.  One virtual machine is running MSSQL Server 2012.  The network speed for 4 of the servers connecting to the sql server are the same but the 5th server's connecting to the SQL server takes about twice as long.

When I open the Hyper-V manager and look at the network adapter settings for the slow connecting machine, the settings are identical to the other machines.
Dear Experts,

What is the best practice of exporting a virtual machine(Hyper-V) of production environment. After shutdown the machine or During running? I have read blogs people prefer if after shut down.

If we export it to another server on another hyper-V do we need some extra configuration?
Customer engaged us because their physical server was down completely (hardware failure).  Old server was 2012 R2 Hyper-V server, running three VMs, one of which was SBS 2011 acting as their DC, file and exchange server.  We recovered the VHD files from failed server's disk and copied to another server, this one running 2019.  FYI - There is NO backup of the guest operating systems, just the VHDs we pulled and file-level backups.
Created new VMs on the new box and attached the recovered VHDs.  Everything seemed fine.  One server (the SBS and most important) has issues thoguh.  It boots fine and SMB shares, Active Directory, DNS, and everything work OK.  Exchange 2010 is a totally different story.  It keeps throwing errors about being unable to connect to a DC.
Server occasionally boots to blank desktop backgound with cursor (temporary) access to task manager, and all-around sluggishness.  Also likes to hang on Applying Settings - almost like it's looking for something that's just not there.
The DNS on the VMs NIC points to itself, and nslookup returns the local DC.
Among the errors received:
Process MAD.EXE (PID=3736). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." Use the information in that article to learn more about the cause and resolution to …
Fundamentals of JavaScript
LVL 13
Fundamentals of JavaScript

Learn the fundamentals of the popular programming language JavaScript so that you can explore the realm of web development.


I have a Hyper-V VM (Host an VM are Windows 2012 R2) that work fine this morning and after 1 hour after employed begin to work, it began to have many problem, most are network specific. It is a DC. This week-end we had a power outage, so I think first that it come from there. I tried to find the problem but it that something is stuck somewhere. many service seem to initialising but stay there or many doesnt seem to start. But there nothing in event log. I have a remote access program on the vm and it is not start, Sql server don't respond, RDP don't respond and many other service don't respond but all share work fine. Internet access is working.

When I check windows activation it said product id unavailable. I tried to reinsert the key but it seem to work without stopping. The key come from an open licence account and it is use on the host and it work fine on it. When I check the maintenance manager it said maintenance running. I tried DISM.exe /Online /Cleanup-image /Scanhealth but it did nothing after 2 hours.

I have in server manager I have problem with managability, it said, online - data retrieval failures occured. I have an other problem reported by server manager for the automatic refresh: Configuration refresh failed with the following error: Call was cancelled by the message filter.

When I shut down the server it stuck on Stopping service  :

I tried restore a 1 month old vm backup and start from there but it does the same thing. That's very weird. …
Customer has one physical box with Server 2016 running Active Directory and all services needed for that, and File/Print/ redirected folders, etc. They now have need for an RDS server. Is it possible to add the Hyper-V role to that server, create 2 new Virtual Windows Server 2016 Machines - one for RDS and the other to migrate everything that the current server is doing at the moment? It would be like an in place migration project. Their network has less than 20 users and the physical server is quite nice. In the end they would have a Hyper-V host, with 2 VMs, one Server running AD, File Print , DNS DHCP and another running RDS. Does that sound doable?
I asked a question some time ago that was about a Server testbed I set up.
It's still up and running and useful.
But I perhaps went about setting the static IP addresses on the Server VMs in an overly complicated and dysfunctional way.
So, I'd like to try once more to make it more "conventional".
The network diagram is attached.

The VM setup was the original concern.  But I also notice something in the Hyper-V machine interface.  So, I'll start with that:
There is a physical interface getting via DHCP AND a virtual interface with static IP  Is that normal or is that odd?  I wouldn't think that having two IP addresses used up would be normal.  BOTH interfaces have the same MAC address.

Now, on to the VMs:
There's a dual-NIC PCI card.
The physical NICs have no configuration.
The virtual NICs are configured with static addresses and have been manually assigned the MAC addresses from the physical NICs they relate to (presumably that's the overkill?)
If this is wrong, then how might I change it so things will continue to work?  I don't think that removing the MAC addresses from the VMs did the trick the first time I tried it.
I set up a Windows Server testbed and asked a question here:
In the midst of the discussion, I tried to set a static IP address for each of the two VMs that I had implemented.
I used a method where I used Advanced Features of the VMs network adapter and assigned a MAC address.
Cliff Galiher took exception to what I did and I took that advice seriously.

Later, I tried to set things back to what I thought had been suggested but doing this broke the testbed.
So, the testbed remains with what I did....

I should point out that in the original testbed, each Server VM was on a different subnet and had a separate physical NIC.

Now I'm setting up another testbed with the real Servers and similar Hyper-V VMs.
I need to make sure that the VM Servers have static IP addresses - as before.
I don't want to overthink this or to overdo it.  
So, what is the recommended approach?
In this case, the 2 VMs in the Hyper-V platform will be in the same subnet and I envision one physical NIC for the pair.
So, in that sense, it's just a little simpler than the original testbed.
I replaced a Server 2012 HyperV box with a new Server 2016 HyperV box - got all the VMs over and working using replication - had to use certificates which was very involved to generate due to issues with names of 2 servers in the certificates.
Now wish to have the new ServerV2016 box replicating all its VMs to a similar new Server2016 box so if Im correct if a VM stops working on the main it will switch to the second.

They are in a workgroup and not on the VMs domains.

Im trying to use kerberos in port 80 rather than doing certificates all over again - is this possible in a workgroup as when I try - it sees the replica box but upon finish I get error no credentials are available in the security package.
Have a HyperV 2016 Host running 5 Server 2012 VMs - recently installed. I thought Id take some checkpoints - all worked apart from one which states  Cannot take checkpoints because one or more pass through disks are attached.
Which I see means that VM is attached to a physical disk . I can see articles on how to convert physical disk to VHDX but how can I find where this physical disk is ? All the VMs are located on seperate physical drives as VHDX ? I cant see how this one is any different ?
We have a Windows 2019 Standard on-premises Hyper-V host with a single Windows 2012 guest.  We started Azure Site Recovery in order to migrate from this on-premises host to Azure.

The initial replication seemed to go well, but we have not completed the migration because we are concerned about some error messages we are receiving.

At exactly one hour apart we are receiving this error in Event Viewer on the host:  Reference point create operation failed.  Error 33800

Initially we had some corrupted (?) VSS writers, but we restarted some recommended services, and now those errors have disappeared, but we are still receiving the Error 33800 every hour.

When we review the Replication Health, we see this Warning:  "Time duration since the last successful application checkpoint has exceeded the warning limit for the virtual machine."
A.  This seems to be an old message, but Resetting Statistics in the Replication Health screen doesn't make this error go away.
B.  Other statistics regarding the replication look very good (i.e.currently 55 out of 56 successful replication cycles).

And gosh, I hate to mention these other screwy things, because I don't THINK they're the cause of this specific problem, but here goes:

1.  An application on the guest system is constantly creating EDI transaction reports (several per minute).  These are not needed and we're researching how to disable this process, but have been unable to.  As a result, at each 5 minute interval, there …
We've got a VM running on Hyper-V, for some reason Installed memory (RAM):  15.6 GB  (2.97 GB Usable).  Usually when i see this it make's me think it's x86 or shared with GPU. On a VM I'm unsure of why the system limits the usable amount of RAM.
Exploring SQL Server 2016: Fundamentals
LVL 13
Exploring SQL Server 2016: Fundamentals

Learn the fundamentals of Microsoft SQL Server, a relational database management system that stores and retrieves data when requested by other software applications.

I have a Dell Power Edge T620 Server, with Microsoft Server 2012 and Hyper-V server service installed. On my Hyper-V server I have a DC, Exchange server, File server, app server and 2 servers for a DNS service called Cisco Umbrella. Everything has been fine, but all of a sudden these servers are causing the Dell server to restart randomly.

I've logged into the Dell Server administrator and no errors, I've checked for errors in event viewer and nothing. I updated all drivers and firmware, I've made sure all window updates are done, but these servers still causing problems. This is the only error I receive right before the server restarts.

forwarder-va2' has encountered a fatal error.  The guest operating system reported that it failed with the following error codes: ErrorCode0: 0xB76FD775, ErrorCode1: 0x40000000, ErrorCode2: 0xBF8D7408, ErrorCode3: 0xB774C000, ErrorCode4: 0xB774ED5C.  If the problem persists, contact Product Support for the guest operating system.  (Virtual machine ID 18468AB3-F650-4EF7-B33E-F00B85FA1748)

Any help would be greatly appreciated. Have a good day.
I have a Windows Server 2016 running in Hyper-V.

From the Windows Update history log, I see:

2019-06 Cumulative Update for Windows Server 2016 for x64-based Systems. (KB4503267).
Successfully installed on 6/15/2015

The same log also has  10 entries (same or different dates):
2019-05 Cumulative Update for Windows Server 2016 for x64-based Systems. (KB4505052).
Failed to install on 6/15/2015

The same log also has  20 entries (same or different dates):
2019-02 Cumulative Update for Windows Server 2016 for x64-based Systems. (KB4487006).
Failed to install on 6/15/2015

Then has this entry:
2019-05 Cumulative Update for Windows Server 2016 for x64-based Systems. (KB4494440).
Successfully installed on 5/18/2019

What could be the problem for not installing the updates?  Is it necessary to go back and install a 2019-02 update, when its 2019-06 update has been installed successfully?

Note:  I also have a second Windows Server 2016 running in Hyper-V, which has these sames updates installed successfully.
i would like to seek expert advice for the licensing window 2016 standard.Recently we just purchase one OLP license to upgrade 3 server from 2008 to 2016.

 We purchased (qty=32) Windows Server 2016 Std ,i would like to provision another VM using window Server 2016.Do i need purchade additional license?How many VM i can provision based from 32 .

Let said the license above insufficient ,how many license need to purchase ?

we have running hyper-v cluster in our enviroment.

1.HV-Nodes 1
processor: 2 x processor with 6 cores each

2.HV-Nodes 2
processor: 2 x processor with 6 cores each
Hi, we have 10 Hyper-V Host server running on Server 2016. We have formatted the data drives as ReFS. On these ReFS volumes are the Hyper-V VM files located.

Is this good? Safe? I ask because yesterday we where at a customer and he has 1 Hyper-V host also with data drives in ReFS. He had a power failure and when the server booted his datadrives where corrupted in RAW format.

If i search the net i read alot saying that ReFS should never been done and that we should use NTFS. But this are comments from over 1 year old. Is it still the same today? Do i need to worry? What are your toughts on this? Microsoft says go ahead and use ReFS. But what is the production thing to do?
So I have a brand new server and a Server 2019 Datacenter license. Two small-ish drives working together in a RAID 1 will be for the OS. That will be formatted as NTFS and 2019 DC will be installed here with the Hyper-V role (and that's it!). Then ... I have 6 SSD drives working together in a RAID5 and the only things that will live on this drive are the actual Hyper-V VM files.

I've read about how ReFS has come a long way since it was released with 2012, yet when you format a data drive in Windows, NTFS is still the default. So I wanted to ask - who out there has embraced ReFS for Hyper-V? Should I keep it safe and stick with NTFS? Or should I use ReFS?

This drive will never be used for anything other than storing Hyper-V files.

Also: If I go with ReFS would there be any potential compatibility issues if, say, I had to migrate a VM from an older server (having only NTFS) to this new server (having only ReFS) or vice versa?
Looking for advice on using Generation 2 for Hyper-V VMs. As we are in the process of upgrading all of our servers, I was thinking it might be a good time to move to Generation 2. Can you tell me if there is a reason not to? All of my VM host are already Windows server 2012r2.

Great link with info on the differences between Generation 1 and 2.



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.