VDI file cannot be transferred from external to internal hard disk
Posted: 20. Aug 2018, 22:57
Dear Community,
I have a problem I just can't get solved. Last week I created my first virtual machine. And I probably made a mistake: I saved the machine (vbox) to my internal HD and the corresponding hard disk (vdi) to an external HD. This weekend I was able to install a new, larger HD in my MacBook and wanted to save the VDI file on my computer to make the guest system run better.
But I can't transfer the VDI file to the internal HD without getting an error message when starting Windows.
This is what I did (Terminology: "external VDI" = VDI file on external hard drive; "internal VDI" = VDI file on internal hard drive)
I'm running out of ideas - I've done everything that came to my mind. Can anyone help?
I already have my Windows license (OEM) on the virtual machine and therefore cannot reinstall...
Kind regards
Steffen
----
I tried it with VirtualBox 5.2.17 and 5.2.18.
I'm using Windows 10 on a Mac with High Sierra.
Attached my log file.
I have a problem I just can't get solved. Last week I created my first virtual machine. And I probably made a mistake: I saved the machine (vbox) to my internal HD and the corresponding hard disk (vdi) to an external HD. This weekend I was able to install a new, larger HD in my MacBook and wanted to save the VDI file on my computer to make the guest system run better.
But I can't transfer the VDI file to the internal HD without getting an error message when starting Windows.
This is what I did (Terminology: "external VDI" = VDI file on external hard drive; "internal VDI" = VDI file on internal hard drive)
- I copied the VDI file to internal HD; I removed the external VDI from the machine, released it in the global tools and deleted it; I added the new internal VDI to the machine. RESULT: The machine starts, but stops immediately at the following message: "Preparing automatic repair".
- I have reallocated the external VDI to the machine: RESULT: No problems, Windows starts quite regularly.
- I created a new VM and assigned the new internal VDI to it. RESULT: The machine starts, but stops immediately at the following message: "Preparing automatic repair".
- I created a new VMand assigned the old external VDI to it. RESULT: No problems, Windows starts regularly.
- I created a clone of the old external VDI on the internal disk and assigned the new one to the VM. RESULT: The machine starts, but stops immediately at the following message: "Preparing automatic repair".
- I created a new VM and added the old external VDI, which worked. I cloned this machine completely (including the external VDI) to the internal HD. RESULT: The machine starts, but stops immediately at the following message: "Preparing automatic repair".
- In all variants I selected and deselected the SSD option for the VDIs.
- I also experimented with the attitude to paravirtualization - without result.
I'm running out of ideas - I've done everything that came to my mind. Can anyone help?
I already have my Windows license (OEM) on the virtual machine and therefore cannot reinstall...
Kind regards
Steffen
----
I tried it with VirtualBox 5.2.17 and 5.2.18.
I'm using Windows 10 on a Mac with High Sierra.
Attached my log file.