Cantstart windows

[dcneuro]

When I try to start windows, I get this error. When I give the Crl-alt-del command, it ttys to restart and ends up at the same error.

Any suggestions?

[socratis]

This seems like a guest OS corrupted image (=bad, really bad). NTLDR (NT Loader) is a vital piece of the boot-up process and if it's not there or if it corrupted, things are not gonna move on. I've never seen a recovery from a missing NTLDR, but others might disagree. Do you have vital files that you need to access?

[dcneuro]

No, I just didn't feel like reinstalling all of my software. I did an export process, then I added a new VM. When it asked where I told it to use the 40 gb already allocated to the first one. When I went in to the second one, all of my stuff appears to be intact, with the exception of some settings.

[dcneuro]

Can I just delete the old one?

[mpack]

I see your old VM used a snapshot - the corruption was likely in the snapshot only. By building a new VDI around the base disk you've lost everything that was saved since the snapshot was created. Whether you're ok with that is up to you.

If your second VM is accessing the base disk of the older VM then no, you can't just delete the old VM. What you should do instead is use File|Virtual Media Manager to copy the old base disk, move the disk copy into the new VMs folder, then tell the new VM to use that VDI instead. Once the new VM is fully independant then you can delete the old one.

p.s. the exported version of your old VM will be useless as it will have merged the snapshot for export purposes. Cloning the VM would do the same.

[dcneuro]

Another question. When I did the export, where does the file export to? I presume this export file is all of my data and settings? What are the three letter extension for the file? If I import this file into the new VM I created, will it restore my old settings?

[mpack]

As I said, the exported VM will be useless since it will incorporate the same corruption that led to the first reported error. The only reason you've gotten past that corruption is because you implicitly reverted to pre-snapshot data whereas an export will include that data.

An exported VM has an OVF extension, and will be saved in the folder you chose at the time you exported it. Important supplementary files will be in the same folder.

[dcneuro]

Well, I successfully made the copy. How do I add it to the other vm and make it active?

[mpack]

Move the copy into the new VM folder, then use the Storage panel of the VM settings to detach the currently mounted VDI file and attach the preferred VDI to the hdd controller.

[dcneuro]

I continue to have problems tin this. Now I get these errors:

[dcneuro]

I have several more error screenshots, however, the site will not permit me to past them.

[dcneuro]

Here is another...

[dcneuro]

and 1 more. The first one is too large apparently

[mpack]

Those seem to be warnings, not errors. You should be able to use File|Virtual Media Manager to unmount the ISO from all VMs. Note the "Optical Disks" tab.