The problem is most probably a corrupted VHD file. How and where did you get a hold of the VHD?
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Perryg wrote:That is one of the downsides of using VHD instead of the default VDI. VHD is too fragile.
Restore from a backup.
I can not restore windows again because i don't know how ?
anyway i have many important files on hard , Is it possible to save this data, is there a way to restore this data ?????????????
I'm not sure we know what the problem is yet. The path tells me this "VHD" isn't part of a VM, so what is it, and where did it come from? If it's been transported, do a checksum test for corruption.
The error says the file isn't a VHD, despite the extension. I'd like to see the evidence to the contrary, and evidence that this was ever part of a working VirtualBox VM. It's possible the message could also mean the VHD is only part of an incomplete difference chain, i.e. a "borrowed" Win7 XP mode VM.