VDI can be backedup on another external disk to use it later

[a cooperator]

Hi,
Host OS is Window 7 Home premium 64 as well as guest OS.
I really have tried only copying a copy of a VM's virtual hard disk(VDI) on which Windows 7 installed along with its updates and some programs. Then I saved the VDI file on an external hard drive.
I don't copy 'log' and 'windows 7 -m.vbox-prev' and 'the name of VM'

However, when I have created a new VM and then attached this existing VDI backed up previously on an external hard drive, I found this error "VBox stopped working ' when Windows 7 was loading.





Sometimes I faced this belue screen error while VM was loading



When loading VM with using the original VDI file located on local hard drive, I didn't find any error.

Is this error shown because VM was running from a VDI located on an external hard drive or because I only backed up VDI file without backing up the other files of the VM whose VDI file was backed up?

[a cooperator]

As additional information, I would sya that when I created the first VM, I have let VDI attached to it via IDE controller.

However, when I created a new VM, I have attached this backedup VDI to the VM via SATA controller. Thus, I I was facing that error due to attaching VDI to VM via SATA controller, however, VDI should have been attached to the VM via IDE contrloller because it was attached to the previous VM via IDE controller. Am I right?



Thus, when I've let VDI attached to the new VM via IDE controller, the VM loaded very well.



And then When Windows got started, I found Windows got some updated 'ATA' devices.

Finally, when I returned to attach the same hard disk(VDI) to the same VM via SATA controller, then while VM was loading, I found 'chkdsk' was checking the OS partition to consistency. Then when Windows got started.
I found this:



In conclusion:
First: I have created VM with VDI attached to it via IDE controller
Second: I have copied that VDI into another external hard disk.
Third: I have tried creating another new VM and attached copied VDI to it via SATA controller, but I faced an error not starting Windows.
Fourth: I have returned to attach the same VDI to the same VM via IDE, then the Windows loaded well. Howeve, when it got started, I found that Windows detected some new devices(ATA, etc) and defined them.
Sixth: I have turn off the VM, and then I have remove the VDI from IDE, and then attach it to the same VM via SATA controller.
Finally: The VM loaded, but in the beginning, CHKDSK was checking OS partition, and then Windows got started, then VBOX HARDDISK ATA DEVICE installed.

[mpack]

Your tendency seems to be to start off down a blind alley then show us 50 pictures of the alley. Not very useful. It would be better for you to say in simple terms what you're trying to achieve, then say what the problem is.

If you simply want to make a backup, back up the whole VM folder as a unit. Don't just back up the VDI. Read Howto: Move a VM.