VHD drive not detectd by after rebooting

I have made a drive image backup of my wife’s computer which I want to restore on my PC.
To this purpose, I have created and mounted a VHD drive on my Windows 10 Pro, with Disk Management . This Drive now shows un My PC .
My plan is to restore the Drive image to the VHD drive by using the Aomei Backupper ( or Reflect) boot disk and then restore this Drive Image into VBox.
Unfortunately, I hit a brickwall, because the VHD drive gets unmounted when I reboot and is no longer detected by the computer as the destination drive for the recovery
I wonder if there is a way around this.

Thanks

Ittiandro

cereberus said:

You do not need to boot from a boot disk to restore an image to a vhd.

Just mount vhd file, run Macrium Reflect or AOMEI from Windows restore image to vhd drive.


If you did boot from disk (hard way) it would be like as follows.

Boot into Macrium Reflect

2. Select Command Prompt from icon in bottom left of screen

Type following


Suppose vhdx file was E:\vhds\win10.vhdx
then type (substuting drive, path, name for your vhdx file)

diskpart

select vdisk file=E:\vhds\win10.vhdx

attach vdisk

exit

exit

Then refresh drives and restore to vhd.

Thank you so much. I was finally able to recover that drive following your hint!!
This being said, I ran into anither problem: shortly after recovering the Drive image, the VBox machine became all os a sudden inccessible. In the haste, I removed it. I found it in the VM machine folder, but I cannot access it. Here is the message I get:

Failed to open virtual machine located in C:/Users/gundobaldo/VirtualBox VMs/Danh_/Danh.vbox.
Could not find an open hard disk with UUID {afb05e6a-01d8-42bb-b933-8185c5f26f10}.
Result Code: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
Component: VirtualBoxWrap
Interface: IVirtualBox {9570b9d5-f1a1-448a-10c5-e12f5285adad}

I'll do a new VBox machine and rebuild the recovery, but I'm just curious why this happened.
Thanks

Ittiandro

cereberus said:

I would not use virtualbox - Hyper-V is so much better when dealing with Windows and virtual hard drive (faster too).

Thanks
I have enabled Hyper-V and opened the Hyper-V Manager. It prompts me to connect to the ( local) server, but I get an error message that I have to check that the Virtual Machine Management service is running..
The Virtual Disk Service is running, but none of the other Hyper-V- connected serviceis is running and I am unable to start them. They are listed as “ Manual(Trig)
I ran an elevated DISM command to enable the Hyper-V feature, if necessary. It returns a message that Microsoft Hyper-V is an unknown feature.

I am on Windows 10 Pro v 10240. The Hyper-V feature is supposed to run on this 2015 build.
Why this problem?

THanks

Ittiandro

cereberus said:

Follow steps in this tutorial precisely, particularly in Section 2.2.

Hyper-V virtualization - Setup and Use in Windows 10

Also, why on earth are you still using 2015 build - that is unsupported and buggy, and a security risk?

Thanks so much . I read the tutorial, ran the BCD Edit command, rebooted the computer. Still unable to connect to the server. It prompts me to to check I am authorized to connect to local server..It says: Operation failed because of “ invalid class” whatever it means.
As to my 2015 Windows 10 build being too old and possibly still having a few bugs that affect the Hyper-V feature , you have a point. IÂ’ll see if I can put my hands on a more recent version, but I wonder why MS have not been able to fix them once for all, eight years(!) after, without requiring an almost endless bombardment of updates: yesterday I had two coming in and 6 (!) on February 2nd ( all listed with their code number) .
They reboot my computer in the most inappropriate moments. This is why I had blocked them !
Now I have enabled them again, just in case this is the reason why I cannot connect with the Hyper-v Virtual server..
Ittiandro

cereberus said:

Things have moved a long way since 8 years ago - updates are not as frequent, much more reliable etc. The bad old days of forced reboots has long gone.

I am sorry, until you are on a modern version of Windows, people cannot really help you as we do not know if its old bugs, system corruption etc.

Read tutorials about ways to upgrade.

Once you have upgraded, don't block them. I and many other here never get issues with updates as we do not fight the system

Best way to upgrade is to download latest iso, mount it as a drive and run setup.exe.

However, although it should work, you are asking a lot for it to go smoothly as you are on a really old version.

If the upgrade falls over, a clean install is probably best.

If you upgrade sucessfully, then run following from an admin command prompt:

Code:

sfc /scannow

It takes up to 10 minutes but checks if anything is corrupted and attempts to fix it (usually works as well).

Also, it is not a bad idea to generally tidy things up as well

Make sure you have a Reflect backup before you attempt upgrade!

If the upgrade falls over, a clean install is probably best.

Super. Thanks for your fair comments. I realize that my Windows 10 Pro was far too old not to cause significant problems.
I managed to install Windows Pro v. 2004 build 19041.572 of 2020.
Now Hyper-V kicks in pretty well, wth all the features described in the tutorial. Unlike before, now there is a long list of Actions in the right panel, but, again, I see no server connection there. Tomorrow, I'll try to install a virtual Windows 10 Pro with Hyper-V.
Reading the tutorial, it looks pretty straight forward. Also I'll see if I can recover with Hyper-V that Drive Image of my wife's computer. I had managed to do it with VBox , but the Vbox was very jittery, slow and froze up all the time. May be I didn't give it enough RAM.
I'll ask the Forum for assistanve if I need to. Sure thing, I'll I'll read the tutorial and search the web in order to better understand.

THanks

Ittiandro