Snapshot error for new virtual guests after 4.2.10 install

[CsabaPen]

Hi All,

I have updated 4.2.8 to 4.2.10. All old virtual guest are working fine. I can create new snapshot for them. No problem.

But all new guest does not works properly. I cannot move them into or out from groups. Cannot delete them properly from the Console. I have to delete manually the files from the harddisk.

They do not work with snapshots. New VBox guest works fine until I add a snapshot to it. After that:
Failed to open a session for the virtual machine wxp.

No error info.

Result Code: E_FAIL (0x80004005)
Component: ProgressProxy
Interface: IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913}

In the Virtual Media Manager on the disk which belong to the new guest I have an explanation mark. It says:
Parent UUID {all 0s} of the medium C:\Users\oracle\.VirtualBox\Machines\xxxxxx\snapshots\{xxxxxxxxxxxxxxxxxx}.vdi does not match UUID {xxxxxxxxxxxxxx} of its parent medium stored in the media registry ('C:\users\oracle/.VirtualBox\VirtualBox.xml')

[CsabaPen]

Hi All!

Update:

I have found out that the snapshots works if the multi-attached (shared)or hte base disk and the snapshots are on the same drive. It seems that if they are on different drive letter virtual guest does not work.

I never had this problem with VBOX.

I have 15 old virtual pc and server and all stored on the d: drive and the snapshotes are stored in %userprofile%\virtualbox folder on C: drive. They work fine but all new virtual guest that I have created since 4.2.10 update fails if the snapshot and the base vhd are on different drive.

Anybody knows why they cannot run from different drive?

[mpack]

It sounds like you are mixing v4.x and v3.x VirtualBox VMs, and hence have not noticed that the media registry works differently in the two versions. VirtualBox tries hard to be backwards compatible, but using snapshots and distributing them over multiple drives... well I would expect trouble.

IMHO you should bring all the VMs up to v4 standard, then the problems should be reduced. Cloning the VM is the easiest way to do this, though it's also the slowest. An expert would simply edit the xml files.