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 created a VHDX file from Windows 2012 Server running as VM on ESXi Host. Then I copied the VHDX file into the Virtual Hard Disk folder in Hyper-V 2016 Server and created  a VM using existing VHDX file, assigned RAM, CPU  and Virtual Network Adapter. When I start this VM, it only shows a blinking cursor at the beginning and stays that way.
 I have tried Legacy Network Adapter and tried to press [F8] to start in safe mode, but to no avail.
 What else can I try?

Fundamentals of JavaScript
LVL 12
Fundamentals of JavaScript

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

Hi All

Hope someone can help me. I have a server running with Hyper-V Server 2012 with a Windows VM running on it.

I need to be able to redirect the physical COM port of the server to my VM.

How does one go about doing that?

I have a Windows 2012 R2 Hyper-V server with 3 VMs.  One of the VMs is setup for Remote Desktop Services and we have about 13 users connect into this server to work.  Most of them connect to it from within the office.  Some of the users connect from outside of the office.  The managers asked me if there's a way that I can restrict remote access for some of the users.  They would be able to work at their computer within the office but if they go home and feel like they want to remote into their session, they would be restricted from logging into their session when they're out of the office.  What's the best and most simple way to accomplish this?  Thanks in advance for your help!
I have a failover cluster- it is a 2-node Hyper-V Windows Server 2012, and one of the nodes had failed. I rebuilt the node, and have had weird issues seemingly related to the CNO ever since. One current problem is that failover doesn't work- I have to slow-migrate between nodes, which defeats most of the purpose of the cluster. The cluster consists of two nodes using a 10TB SAN for CSV. What risks to I run by deleting the cluster object and rebuilding it? I would do this off-hours of course, but I'm just curious what issues are likely to surface- I'll be doing this late at night, so I'd like to make sure I am as poised as possible with solutions in hand.
The cluster service on Server 2016 causes the server to hard lock upon start.  I cannot seem to get anywhere with any of the articles I read.
We are using Windows 10 in a office environment and will soon go to office 365.  How can I remove the unnecessary software from Windows 10.   Also this will act as a golden image for Hyper-V VDI.
MVMC Connection Option Screeb Warning on Summary ScreenConvertion Process Screen
 I am trying to convert Windows 2003 Server running virtual machine "FS1_W2003-recovered"  in VMWare ESXi server into Hyper-v virtual machine using Microsoft Virtual Machine Converter and have some questions:
 (1) In Connection option screen, I am not sure if the message means or applies to my situation?
 (2) In Connection option screen, why I can't select "On" for "Final state of source virtual machine"?
 (3) In Summary Screen, should I be concerned about the warnings (1. OS not supported  2. having one USB device) ?
(4) In Completion screen, I see "Uninstall tools" on the 3rd line. I assume it will uninstall VMWare tools? If so, why does it do that? Will it alter or harm existing VMWare VM in any shape or form?  This is where I CANCELLED the conversion because I was not sure what would happen to source VM.
Your PC needs to restart.
Please hold down the power button
Error CodeL 0x000000C4

Windows 2012 R2 Hyper-V Image w/ SQL Server 2017 boots to Repair Startup after updates

Tried running:

dism.exe /image:C:\ /cleanup-image /revertpendingactions

from command prompt and got an error about the scratch disk might not be large enough, but no option to change it and said it succeeded.

Rebooted, same error


bootrec /mbr and bootrec /fixboot

This is a new vm and I forgot to check the backup to add it. It is not being backed up so I cannot restore. I do have a backup of the existing state now, but I would prefer tor ecover it if possible

I have also checked hyper-v processor settings, as some posts I found, seem to suggest that it is due to a cpu settings, but options there seem to be limited
Windows Server Backup SummaryRecovery Option ScreenHi,
I am backup Hyper-V server using Windows Server Backup. The size of the backup is about 1,600GB (C drive for OS, E drive for VMs files) and external USB hard drive  size is 3,725GB.
It ran the backup for three days and it only used up so far 1,594GB.
As I understand it, Windows Server Backup program does not do "incremental" backup on virtual machines; therefore it has to do a full backup each and every time. I noticed that it literally took 9-11 hours to complete the backup in the past 3 days. Very slow considering that the server has USB 3.0 ports and USB hard drive is also 3.0.

However if it has to do "complete" backup (because it can't perform incremental backup), then why do I see > 2,100GB space still available on external backup drive after 3 days of backup?
Does it overwrite previous backup? if that is the case, then I can only go back to previous day to restore?
Errors in FixMyNetworkTCPIP setting on SBS2011IPv6 SettingsResult from running FixMyNetworkDNS Forwarder in DNS ManagerHi,
I converted a physical SBS2011 server into a virtual machine in Hyper-V server 2016.
* Problem: SBS2011 VM ( can't surf the internet.

What is working:
- All workstation PCs can access shared folders from the SBS server.
- All workstation PCs can access the internet. I have backup Domain Controller (
- From all workstation PCs, I can ping the router ( or SBS server ( or any other network devices.

* What I attempted:
When I run FIX MY NETWORK TWICE in SBS console, I get IP 6 error. There is no IP 6 addresses given. When I checked two other SBS2011 servers that I manage, they all have IP 6 address assigned. Presumably automatically assigned during the SBS setup because I did not assign them.
(Fyi, I don't use Exchange related services because it has been migrated to online exchange.)
After running FixMyNetwork, it says it fixed IPv6 issue (please see the screenshot), but when I open IPv6 properties, there is no IP address assigned.

Can you help?
10 Holiday Gifts Perfect for Your Favorite Geeks
10 Holiday Gifts Perfect for Your Favorite Geeks

Still have some holiday shopping to do for the geeks in your life? While toys, clothing, games, and gift cards are still viable options for your friends and family, there’s more reason than ever to consider gadgets and software.

e have our BDR backup create hyper-v images of the hyper-v servers at a DR site using Solwarwinds Backup. Last year, we performed a test using these servers in an internal network successfully. This year, when we went to test it, we began having random issues with the network adapter not installing on servers. On any given day, either one of the 6 servers (mixture of 2008 R2 and 2012 R2) will not find a network adapter. We have tried using the legacy adapter for the Server 2008 boxes, but I have even seen this on the Server 2012 boxes. I have tried both an internal network switch, and a private network switch. If I try to add an adapter to the server via powershell, it seems to go through, and If I do the "Get-VMNetworkAdapter -VName" command, it shows the adapters attached to the machine, and if they are connected to one of the switches. I cannot figure out what is going on.
 To convert virtual machine (or physical machine) to Hyper-V server, I tried all three methods - Microsoft Virtual Machine Converter (MVMC), Disk2VHD and Restoring from Windows Backup.  They all worked except MVMC would not work on Windows 10 OS computers.
 Here are Pros and Cons:
(1)  MVMC had most errors to deal with. If you  can somehow figure out various errors, then this would be my choice for the conversion because it does pretty much every thing for you including creating a VM. Once the conversion program is run successfully, all you have to do is populate static IP information after virtual machine starts.
(2) Disk2VHD was with least of errors among three methods. After vhdx file is crated, all I had to do is to point the hard drive to existing (exported) VHDX file when creating a new virtual machine. That was it!
(3) Restoring from Windows (Server) backup required most steps. Create a new VM with right ISO file, start the VM and go to Repair mode/Advanced/Restore System Image ... etc. And if you can not enter correct path (to where Windows backup file is located),  then all bets are off. So I would say this is the least convenient among three methods.

Having said that, I have a few questions:
1. For testing so far, I always ran MVMC or Disk2VHD during offline hours (meaning late at night or during weekend). But is there a danger of running these programs during regular work hours (8am - 5pm) from "technical standpoint"? I know, if I run them during the …

  I have a network with 5 workstation PCs and 1 file server (running Windows Server 2012 Essentials on HP Proliant MicroServer Gen8, two 7200rpm SATA HDs, as a physical standalone server).
  I am going to upgrade this physical server to a virtual server and here is what I have in mind:
 1. On a new HP Proliant MicroServer Gen10 server with two 7200rpm SATA HDs, I will install Windows Server 2016 Essentials OS
 2. Add Hyper-V role to the OS.
 3. Convert an existing Windows Server 2012 Essential Server to a virtual server using Microsoft Virtual Machine Converter (MVMC)
 4. Turn on this virtual machine (running Windows Server 2012 Essential) and perform in-place Windows 2016 Essential upgrade.

 I guess I could perform in-place upgrade to Windows 2016 Essential on current physical server (running Windows Server 2012 Essential) before converting it to virtual server, but I thought it would be easier to upgrade OS in virtual environment.

 What do you think?
 Is this what you would recommend?

 The only other concern is that how responsive the new virtual machine (running WE 2016) would be in Hyper-V environment on a RAID 1 with two 7200rpm SATA hard drives.
 Currently HP MicroServer with two 7200rpm SATA hard drives are running just fine for average 3 users opening Word and Excel files. No one ever complained about the speed.

 I could also forget about setting up Hyper-V server and just set up another physical server running Windows Server 2016 Essentials …
I am in the market for an used computer for the purpose of having a "Lab purpose" Hyper-V server and I find these CPU mark/rating very confusing.
Unlike in the past when things were simpler (286,386, 486, Pen3, Pen4, I3, i5, i7 ... etc,), Xeon series are not all that simple to choose from.
Having said that, what is it that I need to consider? # of cores? Avg CPU Mark? Date that CPU was released in the market place?
For example Xeon E5-2640 @ 2.50GHz w/ 6 cores has highest Avg CPU mark of 14682 from the list below, but it has 6 core. Now compare it to Xeon E5-2660 @ 2.20GHz w/ 8 cores, but Avg CPU mark is only 11098 even with 8 cores.
Xeon E5-2609 v2 @ 2.50GHz has 4 cores and is the most recent release date of Q2 2014, but Avg CPU mark is only 5149.
Xeon E5-1620 @ 3.60GHz has the highest GHz, but but Avg CPU mark is only 9055.

CPU                                      Cores      First Seen      Average CPU Mark
-------------------------------------      --------  --------------       ----------------------------
Xeon E5-2650 @ 2.00GHz                8      Q1 2012       10145
Xeon E5-2609 v2 @ 2.50GHz      4      Q2 2014             5149
Xeon E5-2620 @ 2.00GHz            6      Q2 2012             7923
Xeon E5-1620 @ 3.60GHz             4      Q2 2012             9055
Xeon E5-1607 v2 3.00GHz               4      Q1 2014             6199
Xeon E5-2640 @ 2.50GHz            6       Q2 2012            14682       
Xeon E5-2660 @ 2.20GHz            8      Q2 2012            11098      
Xeon E5-1603 @ 2.80GHz            4      Q2 2012             5546
Xeon E5-2630 @ 2.30GHz            6      Q2 2012             8839
Xeon E5-2643 @ 3.30GHz            4      Q2 2012             8423
Xeon E5-2670 @ 2.60GHz             8      Q1 2012            …
I have archiving system with 100tb that is work with mssql
I have hp g10 with 2x 500gb ssd harddisk  that is work with Hyper-V and sql server will install on  vm that it will be on storage
we plan to get a storage. the storage will have ssd hard disk for Hight performance or sas regarding the cost
the san with ssd from hp will be so much so we planed to work with qnap nas storage
do you agree with that ?
I have server hp ml10 g9 with windows 2016 with Hyper-V and I have a mikrotik 951
I set the server to shutdown everyday @6pm
 I set a mikrotik to wake on lan script on 8am

the problem that is the windows 2016 not support wol on s5 state
its only on s4 and s3
regarding hp:
Press Win + x, select Run and type regedit in the run line.
Select OK to launch the Registry Editor.
Navigate to KEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NDIS\Parameters.
Right click on Parameters.
Select New DWORD (32-bit) Value.
Add the key AllowWakeFromS5.
Set the value to 1.
Close the Registry Editor.
Restart the computer.
but it's not work too I have last bios update and I enable wake on lan via bios.
any solution for that ?
I had a SBS2011 Server die, I am trying to do a bare metal restore to a hyper-v virtual.
Virtual is built; however, it will not boot.
Using installation media I go to command prompt and diskpart shows me that Vol 1 C: is now recovery and Vol 2 D: is now OS.

I have tried:

The automated StartRep.exe at least 4 times, no help.
Reassigning the drive letters via diskpart, then reboot. On reboot letters are back to c: recovery d: os
Reassigning drive letters via regedit mounteddevices, on reboot letters are back to c: recovery d: os
bootrec /fixboot
bootrec /fixmbr
bootrec /rebuildbcd It says there is no os so I did bootrec /scanos still said there is no os

How can I get the d: volume renamed back to c: so I can boot?

We have a fairly new Hyper-V installation and the guest server 'crashes' every time it is backed up.

The backup is a simple USB backup disk - they have a couple and they swap them out and it's set to run a full host, guest and bare metal backup every night.

The VM is a SQL guest and the management company for the SQL app requested that both the system and data drives were setup as fixed disks so it was setup with around 133GB on the system and 681GB on the data (or at least this is how they're shown in Explorer - Hyper-V sees them as 127GB and 650GB). The partition that houses them is 795GB in total and shows a little over 17GB free with the above usage. Note that this server is built with SSD's in RAID 10 hence the lack of disk space.

I have tested and confirmed that it is the backup and specifically the shadow copy part of the backup that causes the issue. When it is disabled or even when the backup integration option is unticked, it doesnt crash. When the backup runs we get some errors on the host event logs:

There was insufficient disk space on volume D: to grow the shadow copy storage for shadow copies of D:.  As a result of this failure all shadow copies of volume D: are at risk of being deleted.

The shadow copies of volume D: were aborted because the shadow copy storage failed to grow.

Open in new window

My question is obviously 'how do I fix this' as every morning the guest is powered off, but also, when using fixed VHDX's is there guidelines for …
Hyper-v Windows 2012r2 Slow performance with remote desktop services. Just converted my cloud-domain from vmware to hyper-v. My guests are running Windows 2008 r2. My Hyper-v Server is windows 2012r2.

We are getting complains about slow remote desktop services from our clients to the remote desktop services guest. With vmware there were no complains.

The server is a newer server (DL380 g8 than the Vmware server (DL380 g7).

We created 2x2 teaming adapters for more throughput. Both of the adapters have ip-addresses in the same vlan. The first teaming is used for the Hyper-v server, the second for the guests to connect to the internet, via another vlan.

Just to be sure: my teaming adapters are configured as 2 x 1 networkcard, teaming mode = switch independant, load balancing mode= Dynamic, No standby adapter

The users complain about slow typing text, slow emails, slow printing, etc.

We turned of virtual machine queue on all network adapters (virtual and physcial), but no solution to the slowness.

When i takeover the machine, i don't see any issues as admin.

Any suggestions, advice, to solve this?
Microsoft Azure 2017
LVL 12
Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

I have cisco slm224g switch
I have a windows server 2016 with Hyper-V rule
I have three vlans 2, 3
Hyper-V on port 1
adsl router on port 2
client work station on port 3
on Hyper-V I have a pfsense as vm with two network interface the first one with vlan id =2 and the second one vlan id=3 on the same interface.
I want to assign client ,Hyper-V to vlan 2 and should connect over port 1 to first interface on Hyper-V
I want to assign adsl router to vlan3 and should connect  over port 1 to second interface on Hyper-V
regarding above:
port 1 should be trunk  for vlan id 2,3
port 2 should be access to vlan 3
and port 3 should be access as vlan 2
I tried that but it's not working so what the basic configuration for that ?

I have a three windows server 2016 data center using cluster all of them have same problem. I have for everyone psychical RAM 256GB of memory, all the VM's host are using fixed memory a total used for each one 110GB approximately, at this moment hyper-v shows the assigned memory as it's configured, But if I open task manager shows the memory utilized between 96% to 99% in each servers.

Note: nothing service in the processor eating the remaining RAM everything it is normal...! and i can't used life-migration move for any VM to anther hyper-v server because no available RAM.

There is any one can help me?
Hyper-V Manager receiving Http 403 Error.  This occurs when trying to use Hyper-V Manager from a remote client do joined to the domain.  This was working fine at some point it stopped.

We used to label servers with make and model in the old days since they were physical.
We have almost all servers are VMs nowadays .
How do we describe the servers make and model when the vm runs on Hyper-v or Esxi?

I'm trying to look at the VMQ setup to improve networking on our 3 node Windows Server 2016 cluster.   The cluster runs 30 virtual machines of which 6 have real time requirements as they play out radio stations.  We suffer from occasional break up on the radio streams which is usually resolved by a restart of that particular virtual machine, however I want to improve the network to all the machines if possible.  If I run Get-NetAdapterVmq I get the following results which looks like all queues are running off processor 0 which from what I've read is not good.  

However when I run the command Get-NetAdapterVmqQueue to look at how the queues are distributed I get an generic RPC error CimException with a corresponding set of logs in the Application eventlog of Event ID 1000, 1001 indicating a NetAdapterCim.dll crash when wmiprvse.exe is run, presumambly as a results of the Get command

Faulting application name: wmiprvse.exe, version: 10.0.14393.2155, time stamp: 0x5a9e25d8
Faulting module name: NetAdapterCim.dll, version: 10.0.14393.1358, time stamp: 0x59327863
Exception code: 0xc0000005
Fault offset: 0x000000000003541b
Faulting process id: 0xe74
Faulting application start time: 0x01d471f797c244ff
Faulting application path: C:\Windows\system32\wbem\wmiprvse.exe
Faulting module path: C:\Windows\system32\wbem\NetAdapterCim.dll
Report Id: 5b48b0bc-8f71-4485-9438-d64c7ee34d38
Faulting package full name:
Faulting package-relative …

I would like to manage my Hyper-V-2016 from my Win10 entreprise PC.

For that I use the Windows 10 native Hyper-V Manager.

When trying to add the Hyper-V server I got an error : "Check if service of virtua pc managment is running and that you have rights to log on to the server".
See th attached file.

I need help. Thanks


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.