When converted vhd is attached, hyper-v vm does not boot. Even not from ISO

I have been rolling out Hyper-V hosts and creating Hyper-V VM’s for quite a while now. Everything fine, until this case. I need some greater minds to shed some light on this. 

I need to convert a running Windows 2008 R2 server with 8 GB RAM into a Hyper-V VM. We need this machine so we can run a specific old software (from time to time), and the physical machine is acting up. My Hyper-V host runs Windows 2019 Hyper-V host, has
enough physical RAM (16 GB). It has been used to create and run all kinds of VM’s (Windows 2008 server -> Windows 2019 server), Windows 10 etc.. Never failed. RAID 10 on harddisks and enough room.

I have tried a few ways to create the VHD file for this running server. Straight from the server with disk2vhd, and from system recovery backups created by Veritas Back-up Exec System Recovery (tried a few versions of the software). My VHD’s contain all
the files I see on the real server, and the real server has only one partition. No hidden partitions (checked with diskpart). 

The VM I create has the same amount of RAM as the real one, Generation 1. When I attach an iso to it, with the Windows 2008 R2 boot disk, it boots just as expected. Once I attach the VHD to it, it never boots. Black screen, blinking cursor (if the VHD is
the first boot drive), sentence showing I need to push any key to start booting from DVD if the DVD is the first boot device. But the VM does not boot. Once I disconnect the VHD, the same VM boots fine. 

Tried creating a blank VHD for the same VM: VM boots fine. 

I have never has this experience with Hyper-V and none of my Google searches bring this scenario up. Any ideas? 

Next up I will try a competitive system to boot the VHD.

Kind regards,

Wouter Pinkhof


Wouter Pinkhof PINKH bvba, PC-Hulp.com

Read full post . . . .

Import VMs Exported from Hyper-V 2019 to Hyper-V 2012 R2


We have a situation that we have to do the following:

  1. Move (Export/Import) VMs from Hyper-V 2012 R2 (Old Site) to new Hyper-V 2019 (new site)
  2. Add some VHDX to the moved VMs at Hyper-V 2019, and do some upgrade with the custom applications inside VMs
  3. Will keep Hyper-V 2012 R2 (old site) (that host other Apps/VMs) as a disaster recovery platform, so they will keep exporting VMs from Hyper-V 2019 (new site), and import it at Hyper-V 2012 R2 (old site)

Questions are:

  • Is it supported to move (Export/Import) VMs from Hyper-V 2019 to Hyper-V 2012 R2?
  • What  we need to consider when creating/attaching new Virtual Disks at Hyper-V 2019 (new site) to VMs that maybe later imported at Hyper-V 2012 (old site) in case of disaster?
  • Any other points that need to be considered in this scenario?

To share more thought related to this scenario:

  • We have to keep all VMs at Hyper-V 2019 (new site) as G1 including any new VM this to avoid any issue when move it back to Hyper-V 2012 R2 (old site).

Any other points related to disk type, whatever configuration, supportability….? knowing that this will be temp scenario till they build Hyper-V 2019 at old site.



Read full post . . . .

Windows 1709 HyperV replication to Windows 2016 is getting failed

Hello Team,

Windows 1709 HyperV VM replication to Windows 2016 HyperV is getting failed. Giving below error

Please suggest…



Read full post . . . .

Failover Cluster Shared Volume Failing IO Error – Help!

So, needed to reboot a cluster yesterday and drained roles from one server, rebooted, moved roles over and rebooted other. However, now one of the CSV is showing as failed. It is not ReadOnly, I have tried in the Server Manager to attach the disk and get an
Access Denied error, tried via powershell as admin and get the same error. any advise? Tried to change the IsManualAttached as well get access denied for that too.

  • Usage : Other
  • NameFormat :
  • OperationalStatus : Detached
  • HealthStatus : Unknown
  • ProvisioningType : Fixed
  • ParityLayout : Unknown
  • Access : Read/Write
  • UniqueIdFormat : Vendor Specific
  • DetachedReason : By Policy
  • WriteCacheSize : 0
  • ObjectId : {1}SERV-HC-01root/Microsoft/Windows/Storage/Providers_v2SPACES_VirtualDisk.Objec tId="{533570b8-ec7e-4e22-XXXb-e6519f296089}:VD:{352a1d48-XXX2-11ea-80be-2477710262
  • PassThroughClass :
  • PassThroughIds :
  • PassThroughNamespace :
  • PassThroughServer :
  • UniqueId : 111E2A35A23EEA11XXX6E9610262D
  • AllocatedSize : 23991687315456
  • FootprintOnPool : 47983374630912
  • FriendlyName : SERV-HDD-VDISK01
  • Interleave : 262144
  • IsDeduplicationEnabled : False
  • IsEnclosureAware : False
  • IsManualAttach : True
  • IsSnapshot : False
  • LogicalSectorSize : 512
  • Name :
  • NumberOfAvailableCopies :
  • NumberOfColumns : 6
  • NumberOfDataCopies : 2
  • OtherOperationalStatusDescription :
  • OtherUsageDescription :
  • PhysicalDiskRedundancy : 1
  • PhysicalSectorSize : 4096
  • RequestNoSinglePointOfFailure : False
  • ResiliencySettingName : Mirror
  • Size : 23991687315456
  • UniqueIdFormatDescription :
  • PSComputerName :
  • CimClass : ROOT/Microsoft/Windows/Storage:MSFT_VirtualDisk CimInstanceProperties : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace…} CimSystemProperties : Microsoft.Management.Infrastructure.CimSystemProperties

Read full post . . . .

Loss internet connection after restart

I did lose my internet connection in VM (centOS 7) after I restart my PC (windows 10). 

I have created this network through virtual switch- type internal - connection type internal and it was working fine. But after I restarted my PC it doesn’t work.

Read full post . . . .

Reinitialize Virtual Hard Disk

I have a virtual hard disk (VHD) stored on an external USB drive. The external drive does not have a letter assigned; this is to protect its contents from viral attack. In Hyper-V Manager, I added the VHD to a VM by using the DeviceID of the external drive.
The virtual hard disk successfully appears in disk management of the VM. However, at some point the VHD becomes detached (perhaps due to a backup running on the Hyper-V host) and does not reattach unless I re-add it in the Hyper-V GUI or restart the VM.

Is there a Powershell method to reinitialize the detached VHD? I have tried using "Add-VMHardDiskDrive" but it will not accept the DeviceID in the Path argument. A Powershell command which reattaches the VHD seems better than restarting the VM
every time the backups run.

Read full post . . . .

HyperV Cluster Creation with live HyperV host

Its been a while since I created a HyperV cluster but need to set one up using 2 host nodes and storage spaces direct to use the local storage of each node.  The problem I face is 1 of the host nodes already has HyperV installed and about 5 live VMs
running.  Is there a way to configure the 2 node cluster without having to move the VMs onto a third temp HyperV server?

Read full post . . . .

Hyper -V Replication RODC Virtual Machine


we plan to install RODC as a VM in the branch office and replicate it using hyper v replica in another server , it is a problem or not, if we turn on vm replica rodc, if the main  VM RODC/ host server is down ?


Read full post . . . .

create Hyper V on surface pro 7

On surface pro 7 I need HyperV to run a win10 32 bits on the basic win 10 64 bits pro

I uploaded an official win 10 32 bits

I created an Hyper V using this .iso

I started the machine as requested.

It stops on:

"start PXE over IPV4

VM boot summary

1. SCSI DVD did not load an OS

2. SCSI disk idem

*3. Network adapter (00155D00AA03)

No operating system was loaded.

Your VM may be configured incorrectly"

The VM does not see the .iso or the .iso has not the right format.

Would you know what should be changed?

Thanks a lot

Read full post . . . .

Cannot activate Windows Server 2012 R2 Standard in Hyper-V VM

hi guys,
my host server are Windows server 2012 R2 Standard, i have install a Windows server 2012 standard in the hyper-v manager, but it cannot be activate by AVMA,
how can i activate it or should i need to buy another windows server 2012 standard license for it??

Read full post . . . .

Go Que Newsroom Categories

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 36 bytes)
in /home/content/36/8658336/html/goquecom/wp-includes/wp-db.php on line 2023

Query Monitor