I'm asking this in Windows Server sub-forum because my actual host OS Windows 10 does not have a dedicated Hyper-V sub-forum.

Late last year I was running a couple of Windows 10 client VMs on my home desktop PC to test Windows Autopilot and MDM. I would access my home computer from outside via RDC and had no problems operating the VMs (Virtual Machine Connection).

This year, I'm not exactly sure what's changed, but it seems like accessing the VM display console cannot succeed. Either the VMC window would get stuck resizing the window to the VM's desktop resolution and eventually close by itself, or it'd hang with corrupted display.

There are corresponding crash events in Application log.

Log Name:      Application
Source:        .NET Runtime
Date:          15/1/2020 15:22:16
Event ID:      1026
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      HYPERVHOST
Description:
Application: VmConnect.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FFA5C994060

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name=".NET Runtime" />
    <EventID Qualifiers="0">1026</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2020-01-15T07:22:16.616712500Z" />
    <EventRecordID>42127</EventRecordID>
    <Channel>Application</Channel>
    <Computer>HYPERVHOST</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Application: VmConnect.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FFA5C994060
</Data>
  </EventData>
</Event>

Log Name:      Application
Source:        Application Error
Date:          15/1/2020 15:22:16
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      HYPERVHOST
Description:
Faulting application name: VmConnect.exe, version: 10.0.18362.1, time stamp: 0xa8d2f2dc
Faulting module name: atidxx64.dll, version: 26.20.15003.5016, time stamp: 0x5df7d2d3
Exception code: 0xc0000005
Fault offset: 0x0000000000014060
Faulting process id: 0x32b4
Faulting application start time: 0x01d5cb7481d2a7df
Faulting application path: C:\WINDOWS\system32\VmConnect.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\c0349841.inf_amd64_d70567d658937ff8\B349895\atidxx64.dll
Report Id: e506f08b-f1b7-418f-a14e-5a7df056b38a
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2020-01-15T07:22:16.833742200Z" />
    <EventRecordID>42128</EventRecordID>
    <Channel>Application</Channel>
    <Computer>HYPERVHOST</Computer>
    <Security />
  </System>
  <EventData>
    <Data>VmConnect.exe</Data>
    <Data>10.0.18362.1</Data>
    <Data>a8d2f2dc</Data>
    <Data>atidxx64.dll</Data>
    <Data>26.20.15003.5016</Data>
    <Data>5df7d2d3</Data>
    <Data>c0000005</Data>
    <Data>0000000000014060</Data>
    <Data>32b4</Data>
    <Data>01d5cb7481d2a7df</Data>
    <Data>C:\WINDOWS\system32\VmConnect.exe</Data>
    <Data>C:\WINDOWS\System32\DriverStore\FileRepository\c0349841.inf_amd64_d70567d658937ff8\B349895\atidxx64.dll</Data>
    <Data>e506f08b-f1b7-418f-a14e-5a7df056b38a</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Worse is if that corrupt VMC window appears, I could very well lose RDC connection to my computer.

I have to get back home to re-gain access to the OS via physical monitor displays. In the physical logon session, I have connect and vmconnect.exe can render the VM screens. The error below probably explains the RDC failure.

Log Name:      System
Source:        Microsoft-Windows-DriverFrameworks-UserMode
Date:          15/1/2020 17:21:51
Event ID:      10110
Task Category: User-mode Driver problems.
Level:         Critical
Keywords:      
User:          SYSTEM
Computer:      HYPERVHOST
Description:
A problem has occurred with one or more user-mode drivers and the hosting process has been terminated.  This may temporarily interrupt your ability to access the devices.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-DriverFrameworks-UserMode" Guid="{2e35aaeb-857f-4beb-a418-2e6c0e54d988}" />
    <EventID>10110</EventID>
    <Version>1</Version>
    <Level>1</Level>
    <Task>64</Task>
    <Opcode>0</Opcode>
    <Keywords>0x2000000000000000</Keywords>
    <TimeCreated SystemTime="2020-01-15T09:21:51.166245800Z" />
    <EventRecordID>29917</EventRecordID>
    <Correlation />
    <Execution ProcessID="952" ThreadID="700" />
    <Channel>System</Channel>
    <Computer>HYPERVHOST</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <UserData>
    <UMDFHostProblem xmlns="http://www.microsoft.com/DriverFrameworks/UserMode/Event">
      <LifetimeId>{b125172c-e769-468f-ac22-28b8331ebce8}</LifetimeId>
      <Problem>8</Problem>
      <DetectedBy>2</DetectedBy>
      <ActiveOperation>0</ActiveOperation>
      <ExitCode>1879048193</ExitCode>
      <Message>0</Message>
      <Status>4294967295</Status>
    </UMDFHostProblem>
  </UserData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-DriverFrameworks-UserMode
Date:          15/1/2020 17:21:51
Event ID:      10111
Task Category: User-mode Driver problems.
Level:         Critical
Keywords:      
User:          SYSTEM
Computer:      HYPERVHOST
Description:
The device Microsoft Remote Display Adapter (location (unknown)) is offline due to a user-mode driver crash.  Windows will attempt to restart the device 5 more times.  Please contact the device manufacturer for more information about this problem.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-DriverFrameworks-UserMode" Guid="{2e35aaeb-857f-4beb-a418-2e6c0e54d988}" />
    <EventID>10111</EventID>
    <Version>1</Version>
    <Level>1</Level>
    <Task>64</Task>
    <Opcode>0</Opcode>
    <Keywords>0x2000000000000000</Keywords>
    <TimeCreated SystemTime="2020-01-15T09:21:51.195286600Z" />
    <EventRecordID>29918</EventRecordID>
    <Correlation />
    <Execution ProcessID="952" ThreadID="700" />
    <Channel>System</Channel>
    <Computer>HYPERVHOST</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <UserData>
    <UmdfDeviceOffline xmlns="http://www.microsoft.com/DriverFrameworks/UserMode/Event">
      <LifetimeId>{b125172c-e769-468f-ac22-28b8331ebce8}</LifetimeId>
      <FriendlyName>Microsoft Remote Display Adapter</FriendlyName>
      <Location>(unknown)</Location>
      <InstanceId>SWD\REMOTEDISPLAYENUM\RDPIDD_INDIRECTDISPLAY&amp;SESSIONID_0001</InstanceId>
      <RestartCount>5</RestartCount>
    </UmdfDeviceOffline>
  </UserData>
</Event>

And even worse scenario is when I get the corrupted VMC window, lose connection, and cannot even get into the OS via physical means; the monitors keep sleeping and waking with blank screens. I might be able to connect to the VMs via RDC Manager (with VM mode) from another computer to interact and shut them down, but since the host OS is inaccessible at this state I have to hard reset the computer.

I later found scores of display driver restarts, and even broken dwm.exe which likely explains the loss of physical access.

Log Name:      System
Source:        Display
Date:          15/1/2020 22:31:50
Event ID:      4101
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      HYPERVHOST
Description:
Display driver amdkmdap stopped responding and has successfully recovered.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Display" />
    <EventID Qualifiers="0">4101</EventID>
    <Level>3</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2020-01-15T14:31:50.403185900Z" />
    <EventRecordID>30166</EventRecordID>
    <Channel>System</Channel>
    <Computer>HYPERVHOST</Computer>
    <Security />
  </System>
  <EventData>
    <Data>amdkmdap</Data>
    <Data>
    </Data>
  </EventData>
</Event>

Log Name:      Application
Source:        Application Error
Date:          15/1/2020 22:31:53
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      HYPERVHOST
Description:
Faulting application name: dwm.exe, version: 10.0.18362.387, time stamp: 0x8e064b77
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xe0464645
Fault offset: 0x0000000000000000
Faulting process id: 0x4718
Faulting application start time: 0x01d5cbb05c00d5c0
Faulting application path: C:\WINDOWS\system32\dwm.exe
Faulting module path: unknown
Report Id: 350b442b-5588-4cee-a1ca-cf09d0254be7
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2020-01-15T14:31:53.223643800Z" />
    <EventRecordID>42330</EventRecordID>
    <Channel>Application</Channel>
    <Computer>HYPERVHOST</Computer>
    <Security />
  </System>
  <EventData>
    <Data>dwm.exe</Data>
    <Data>10.0.18362.387</Data>
    <Data>8e064b77</Data>
    <Data>unknown</Data>
    <Data>0.0.0.0</Data>
    <Data>00000000</Data>
    <Data>e0464645</Data>
    <Data>0000000000000000</Data>
    <Data>4718</Data>
    <Data>01d5cbb05c00d5c0</Data>
    <Data>C:\WINDOWS\system32\dwm.exe</Data>
    <Data>unknown</Data>
    <Data>350b442b-5588-4cee-a1ca-cf09d0254be7</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Log Name:      Application
Source:        Dwminit
Date:          15/1/2020 22:32:00
Event ID:      0
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      HYPERVHOST
Description:
The Desktop Window Manager process has exited. (Process exit code: 0x000000ff, Restart count: 1, Primary display device ID: )
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Dwminit" />
    <EventID Qualifiers="32770">0</EventID>
    <Level>3</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2020-01-15T14:32:00.717644300Z" />
    <EventRecordID>42332</EventRecordID>
    <Channel>Application</Channel>
    <Computer>HYPERVHOST</Computer>
    <Security />
  </System>
  <EventData>
    <Data>0x000000ff</Data>
    <Data>1</Data>
    <Data>
    </Data>
  </EventData>
</Event>

Seems like I'm forced to work with Hyper-V only through physical display now. What is it about Hyper-V services and components that can make it (now) unsuitable for control over RDC?

The melody of logic will always play out the truth. ~ Narumi Ayumu, Spiral

I might be in the wrong category for this but my issue is really about enabling WinRM so that I can connect to my hyper-v server.

I have set my network connection type to private, but when I try to do winrm quickconfig it reports that it wont work because its public.

PS C:\Windows\system32> Get-NetConnectionProfile                                                                        

Name             : Network
InterfaceAlias   : Ethernet
InterfaceIndex   : 13
NetworkCategory  : Private
IPv4Connectivity : Internet
IPv6Connectivity : NoTraffic

PS C:\Windows\system32> winrm quickconfig                                                                               WinRM service is already running on this machine.
WSManFault
    Message
        ProviderFault
            WSManFault
                Message = WinRM firewall exception will not work since one of the network connection types on this machine is set to Public. Change the network connection type to either Domain or Private and try again.

Error number:  -2144108183 0x80338169
WinRM firewall exception will not work since one of the network connection types on this machine is set to Public. Change the network connection type to either Domain or Private and try again.

I'm really stuck on this one. Maybe it would help to connect through a domain but my plan was to run my domain server on this hyper-v host that I'm unable to connect to.

Hello Everyone:

Actually i have a Hyper-v cluster on Windows Server 2012 and i have a server that i use for connecting to this using Hyper-v tools .  Connection in this schema is fine.  Few month we created a new cluster on Windows Server 2016 and in this case i have other server with win server 2016 that we are using for connecting us to this.  Final idea, would be, this new server allows me connecting to Windows Server 2012 hosts (from first cluster) and Windows Server 2016 (Corresponding new cluster).

Using Failover and trying to connecting me from Win server 2016 to Host on Windows server 2012 (Node or nodes from first cluster).  I obtain the following error:

Actually when i am trying to connect me from Win 2016 (Hyper V Console Server) to Win server 2008 hosts via hyper v Manager and i am not using an administrator user i get the following error

But, if i use a server administrator and i am trying using same console i can to access both servers: Win 2016 and win 2008

So my questions are: 

1) Win 2016 Hyper V Manager Console is not compatible for connecting me old versions hosts?

2) If connection could be possible Would i need a special priviledges?. Because when i trying to do the same connection with an Administrator the error doesn't appear

Please help me with this

Kind regards

Hi,

Can i move virtual machine with Windows Server 2016 evaluation (180days) from one Hyper-V host to other?

Will I lost my evaluation time? I had to do lot of changes and installed many programs so I don't want to do it again, but i have to move this machine to other host.

Hi.

For some time I have a problem with VM (Windows Server 2016) on the HP Proliant DL360 Gen9 server.

The machine has been freezing for some time. I can't get to it through RDP, SSH. When I want VM shutdown on Hypervisor, I get the error "VM state does not allow it to close".

I get errors on VM:

DCOM 10010 - "The server did not register in DCOM within the required time."

and

WAS 5010 - "The process serving the application pool did not respond to the ping command. The process identifier.

The problem repeats every few days or once a month.

The problem usually lasts 30 minutes.

I have already tried many solutions. Unfortunately, no result ...

Thanks for any help.

Hi all,

Looking around I haven't seen any elegant way to determine that  VM has booted successfully to the desktop (assuming autologon).

Is there a Microsoft approved way of detecting this? Or is it only "check if a service is running", etc semi-hacks?

Thanks for any insights

m

Hi,

Is it possible to have hyper-v replica between hyper-v server 2016 (core) and windows server 2019?

Consider that VM configuration versions are the same.

Hello, does a tool exist that I can connect my hyperv machine to an existing vmware environment and run it so it can convert the virtual machines into a VHD format. 

I'm being asked this question and unfortunately I don't know the answer. If it does exist, is there one that runs like vmware converter where it does it on the fly while the machine is on and I simply have to turn the machine on after it is done converting?

Thanks!

Hey,

The goal of the project that I am working on is to create a subnet, with DHCP and NAT, of virtual adapters on the management OS.

(Please do not question why I would do such a thing)

To accomplish this I created a hyper-v Internal Virtual Switch with the command

New-VMSwitch -SwitchName "V Switch" -SwitchType Internal

and I also created multiple virtual adapters connected to that switch.

Add-VMNetworkAdapter –ManagementOS -Name "V Adapter1" –SwitchName "V Switch”

Add-VMNetworkAdapter –ManagementOS -Name "V Adapter2" –SwitchName "V Switch”

Add-VMNetworkAdapter –ManagementOS -Name "V Adapter3" –SwitchName "V Switch”

Then connected a physical adapter (connected to the internet) to the internal virtual switch using Internet connection sharing (ICS). Which turned the internal virtual switch's adapter into a gateway with Ip address 192.168.137.1. The other adapters, V Adapter1 ect..., should be apart of the subnet and get an Ip address in the range 192.168.137.xxx but they do not get responses from Internet connection sharing's DHCP server and have APIPA addresses.

I tested to see if I could get an Ip address from a VM attached to the internal virtual switch and the VM was able to get the Ip address 192.168.137.142 from the DHCP server just fine.

I also tested to see if I could get an Ip address using the ManagementOs virtual adapter "V Adapter1" by using a custom protocol driver that spoofed the source mac address (send DHCP discover with different MAC) and set the adapter in promiscuous mode(Receive messages with MACs other than the adapters own MAC). It was also able to get an Ip address.

Does anyone have any idea why the ManagementOs virtual adapters are not able to get an Ip address from ICS's DHCP server?

Also forgot to mention that if I set a static Ip address for the ManagementOs virtual adapters they work all perfectly fine. It just seems like the DHCP discover message is ignored by ICS if it is from the ManagementOs virtual adapters.

Any ideas of why this happens or a way to get Ip address for ManagementOs virtual adapters from the ICS DHCP server would be a great help.

Thanks!

On a server that previously had the Hyper-V role installed but since removed. Trying to install Hyper-V role again and on reboot no Microsoft Virtual Network Switch Adapter is not created and original nic cannot be accessed or properties viewed. No access to Hyper-V Manager.

How do I start figuring this issue out?

Hi,

I have three Hyper-V hosts - two are Hyper-V Server 2016, and one is Server 2016 Standard edition. Each server holds two VMs - a domain controller, and an application server. I use Nakivo for backing up all three hosts, which supports Hyper-V RCT and is configured to create "forever incremental" daily backups. It usually works great, but there is one weird issue with it, and it happens only on the Server 2016 Standard edition host - after I reboot one of the VMs it hosts, the next backup will be huge - as if it was the first time I am backing up this VM.

It is also worth mentioning that this specific host is of an older hardware model (new R440 vs. R510), and is physically located on a site which is different to the other Hyper-V hosts and the backup server (symmetrical 100Mb FC, though).

Has anyone ever seen anything like this?

Hi, 

I'm trying to send traffic of replication over my 10Gig NIC, and regular traffic on 1 Gig. 

Anyone can help me out. Unable to start replication. 

Scenario: 

Serv1 - 10.36.250.91- 1 Gig
Serv1 - 10.10.10.11 - 10gig    connected to internal 10 Gig switch and no internet. 

Serv2 - 10.10.10.12 - 10Gig   connected to same 10Gig switch no internet. 

i can ping from host server 2 to server 1 - Successful - Vice versa as well.

i can ping from server 2 Vm to server 1 - successful. - Vice versa as well.

host file is also updated with 10.10.10.x - able to ping as well. 

1 Gig

Hi all, I am trying to build a lab server on a old Dell R515 with Hyper-V core 2016.
Installation goes well but not all Hyper-V services are being started.

The vmgid service is complaining that a device attached is not responding. which device might that be?

Here are some events for the logging and how can I troubleshoot any deeper?!

TimeCreated  : 21-1-2020 01:46:05

ProviderName : Service Control Manager​

Id           : 7000​

Message      : The Microsoft Hyper-V Guest Infrastructure Driver service failed to start due to the following error:​

               A device attached to the system is not functioning.​

​

Index              : 776​

EntryType          : Error​

InstanceId         : 3221232473​

Message            : The Hyper-V Time Synchronization Service service depends on the Microsoft Hyper-V Guest Infrastructure Driver service which failed to start because of​

                      the following error:​

                     %%31​

Category           : (0)​

CategoryNumber     : 0​

ReplacementStrings : {Hyper-V Time Synchronization Service, Microsoft Hyper-V Guest Infrastructure Driver, %%31}​

Source             : Service Control Manager​

TimeGenerated      : 21-1-2020 01:47:29​

TimeWritten        : 21-1-2020 01:47:29​

UserName           :​

​

Index              : 775​

EntryType          : Error​

InstanceId         : 3221232472​

Message            : The Microsoft Hyper-V Guest Infrastructure Driver service failed to start due to the following error:​

                     %%31​

Category           : (0)​

CategoryNumber     : 0​

ReplacementStrings : {Microsoft Hyper-V Guest Infrastructure Driver, %%31}​

Source             : Service Control Manager​

TimeGenerated      : 21-1-2020 01:47:29​

TimeWritten        : 21-1-2020 01:47:29​

UserName           :​

​

​Also very strange. When I request all the service for VM*, the vmgid is not listed below. But only when requested seperately.

PS C:\Users\Administrator> Get-Service  vm* | ft -a​

Status  Name               DisplayName​

------  ----               -----------​

Running vmcompute          Hyper-V Host Compute Service​

Stopped vmicguestinterface Hyper-V Guest Service Interface​

Stopped vmicheartbeat      Hyper-V Heartbeat Service​

Stopped vmickvpexchange    Hyper-V Data Exchange Service​

Stopped vmicrdv            Hyper-V Remote Desktop Virtualization Service​

Stopped vmicshutdown       Hyper-V Guest Shutdown Service​

Stopped vmictimesync       Hyper-V Time Synchronization Service​

Stopped vmicvmsession      Hyper-V PowerShell Direct Service​

Stopped vmicvss            Hyper-V Volume Shadow Copy Requestor​

Running vmms               Hyper-V Virtual Machine Management​

​

​

PS C:\Users\Administrator> Get-Service  vmgid | ft -a​

​Status  Name  DisplayName​

------  ----  -----------​

Stopped vmgid Microsoft Hyper-V Guest Infrastructure Driver

How can investigate any further.
Thanks in advance...

Hi,

I have a server 2016 where the windows backup kept creating recovery points.  We noticed to late and now we are stuck with 50 recovery points which we cannot delete.

It looks like this and the tree just goes deeper.

When trying to delete them from the GUI or powershell we get the following error on every checkpoint:

Cannot delete checkpoint: Catastrophic failure (0x8000FFFF). Checkpoint ID C5403A69-C9E9-4EDC-A441-46BFCBDF8CA8.
Virtual machine failed to generate VHD tree: 'Catastrophic failure'('0x8000FFFF').

I'm unable to create a new recovery point and export from there as I hit the limit of 50 recovery points.

I'm unable to merge because it are recovery checkpoints and I heard you should not merge this.

What are my options to fix this, could anybody shed some light on this?

Thank you!
Chris

Hi,

I have Hyper-v Cluster and Standalone Hyper-V server.I want to move all the VM in Standalone environment to Cluster environment.

01.Standalone server have two VM.

02.Cluster have 3 physical node and 4 VM

03.Standalone Hyper-v server and Hyper-v cluster servers connected to HP Storage

Please share the step for how to move VM from Standalone Hyper-V to Hyper-v Cluster

Thanks,

Gayan

Hi all,

I have 2 Hyper-V Servers, one running Server Core 2016 and one running Server 2019 Datacenter w/ GUI.

On the 2019 server, all 5 of the VMs are Server 2019 Datacenter w/ GUI.  I back them all up with Task Scheduler running Powershell scripts to a network share on a dedicated backup server (running 2019 Datacenter w/ GUI).  They all work perfectly, with a variety of schedules and other options including different destinations, etc.  NO problems.

On the 2016 server, there are 10 VMs, 8 of which run Server 2016 Datacenter w/ GUI or Server 2019 Datacenter w/ GUI.  All 8 of these work beautifully with the powershell scripts with wbadmin and task scheduler.  (Same idea as the 2019 server.)

But on that 2016 host server, there are 2 VMs running Server 2012 R2 Standard w/ GUI.  They are not domain controllers, exchange servers, or have any other SQL based applications.  One hosts an encrypted file cabinet program and the other hosts nothing more than an old version of Quickbooks 2008 as a Remote Desktop web application.  Both of them act the same way with the exact same wbadmin powershell command as the working ones.  They both do the same thing whether it's run as a scheduled task or as a direct elevated Command Prompt command or an elevated Powershell command.  They both do the exact same thing whether the command is run as a "Domain Admin" or the dedicated "Backup User" that is used to initiate all the other scheduled tasks.  They both act the same with different target servers and different shares.  They both act the same whether they are online or offline.

Here is a sample powershell command like what I'm using (it works for all my 2016 and 2019 VMs):

wbadmin start backup -backupTarget:\\BackupServer\BackupShare -hyperv:"ServerName" -vssfull -quiet

(I know the -vssfull is redundant when going to a network share but I don't want to have to remember to change this part if I temporarily send it to a local destination.)

What happens when it runs on the 2012 R2 servers:

It does the usual "Creating a shadow copy of the volumes specified for backup..." for a few minutes.  Then it says "Enumerating files for <ServerName>(Online)... 10 found" (ALL the ones that work have exactly 18 files, and never say this 'enumerating files verbiage... they just move straight to 'Starting application backup').  Then it says "Copying files for <ServerName>(Online)..." on one line only (for just a few seconds) with a percentage that will be somewhere randomly spaced between 0% and 25%.  Then it says "The backup operation successfully completed.  Backup of <ServerName>(Online) succeeded.  Application backup succeeded.  Log of files successfully backed up:  <path to log file>.  (Examples of log files from successful and unsuccessful attempts below, but the TL;DR version is that the backup completes successfully but just plain doesn't even try to backup the actual Virtual Hard Disks, like they aren't even there.)

But of course, the "successful" backup set is always roughly 150-250 MB and doesn't include ANY data at all. You know how if you dig into the folders you see the virtual hard drive file that is essentially the size of the data on the server VHD.  Then if you mount that and look inside it, you see the actual backup of the VHD?  Well... what I'm left with is a 150-250 MB VHD that if I mount it and look inside it, there is no virtual hard drive with the data.  It's just not there.

Some notes:  Both 2012 R2 servers are completely up to date and working perfectly otherwise.  Both are generation 2 and have SCSI controllers (not IDE).  One of these VMs is 670 GB and the other is only 21 GB, so size doesn't seem to matter (also, I have another VM that's 2 TB on that same server and it has no problem, so having enough free resources isn't the issue.)  The event viewer doesn't show any errors at all, because, like it said above, it thinks everything succeeded perfectly.

I've googled my little heart out and come up with dozens of postings and forums talking about generic fixes for wbadmin problems, and while I can't list everything I've tried here, it's been quite a bit.  I just haven't been able to find something specific enough to 2012 R2 on a 2016 host to get me where I'm going... which makes me think this is not a typical problem people face. Somebody out there has to have seen this right?  I feel like it's going to be an easy answer like, 'you can't do that, stupid' or 'check this box, silly' but I haven't found it.  Also, for various reasons, upgrading these servers to newer operating systems is out of the question for the next year or two.

Successful Log File Example (from one of the working 2016+ VMs):

Backed up V:\
Backed up V:\Snapshots\
Backed up V:\Snapshots\397F9C6A-9CFE-44D0-8D4F-5A17D4175090.vmcx
Backed up V:\Snapshots\397F9C6A-9CFE-44D0-8D4F-5A17D4175090.VMRS
Backed up V:\Virtual Hard Disks\
Backed up V:\Virtual Hard Disks\SLC-AD-02_Disk_2-AutoRecovery.avhdx
Backed up V:\Virtual Hard Disks\SLC-AD-02_Disk_2.vhdx
Backed up V:\Virtual Hard Disks\slc_ad_02_disk_1-AutoRecovery.avhdx
Backed up V:\Virtual Hard Disks\SLC_AD_02_Disk_1.vhdx
Backed up V:\Virtual Machines\
Backed up V:\Virtual Machines\5FA4A6CE-38C8-4977-ADFE-0EB1AECB5F96.VMRS
Backed up V:\Virtual Machines\5FA4A6CE-38C8-4977-ADFE-0EB1AECB5F96.vmcx
Application backup
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
   Component: 5FA4A6CE-38C8-4977-ADFE-0EB1AECB5F96
   Caption     : Online\SLC-AD-02
   Logical Path: 


*-----------------------------*

Log file from a 2012 R2 attempt (that obviously didn't work, you'll notice the lines where the VHDs should be listed between 'Virtual Hard Disks' and 'Virtual Machines', is nothing more than a carriage return: 

EVEN MORE DETAILS:  I went and tried including every combination of -include:c: -systemState -allCritical, etc. but all of those switches (of course) backup the specified resource for the hyperv host server, not the VM, and it works perfectly, but it's obviously not backing up what I want.  It looks like it's just plain failing to find the VHDs on the 2012 R2 VMs so it just backs up the VM component without the disks and then gives itself a pat on the back for job well done and heads off to its favorite pub for a mid-strength beer.

The even crazier thing:  IT USED TO WORK!  I have VM backups of these machines from 5 days ago from that same server to a different destination (before we upgraded the backup destination server) that worked perfectly.  So, just to prove the theory that the destination was somehow the problem, I hooked up the old backup server and tried to send it back to the destination where it worked successfully 5 days ago... and it does the same thing now... a backup with no virtual hard disks.

So to sum up:  It worked for all machines.  I added a completely different destination server and replaced the scripts with a version with a few extra lines of house-keeping for moving old backups out of the way before the new one runs, and changed the destination share.  It works for all 2016 and 2019 servers, never worked right for either 2012 R2 VMs after the new scripts and destination.  I tried sending it back to the old destination with the old script... and now that doesn't work either.  Tried rebooting 2012 VMs and the host server, no change.

WHAT AM I MISSING???

Any help is appreciated.  Thanks in advance.

I bought an old dell R710 to learn hyper-v, AD, VMware etc. only about a month ago. I installed hyper-v bare bones on the R710 - Windows hyper-v server 2016. The free version which has no GUI. So I'm learning powershell (ver 5.0) as I go along and I have the virtual switch installed. I have the VMmachine installed.

Hi all,

I'm running a Hyper-V host on a Windows 10 machine (beefy gaming type PC, 32GB ram, 1TB SSD) and attemping to spin up Windows 10 guests (as differencing disks off a parent disk). The problem is that often VMs start and often get stuck on the boot screen. I can often restart them and they boot in fine (though not always). I have looked around and none of the obvious problems/solutions seem to help.

If I were to get server class hardware and run e.g. Windows Server 2019 would this boost the reliability of the VMs i.e. fewer if any black screens?

Or should they run just as reliably on my Windows 10 gaming rig and my problem is most likely something else?

Any thoughts appreciated

m