Corrupted VM because copy-paste

[markomladenovic]

Hallo guys,

I cant start Virtual Machine, and now I know why, but I dont know how to solve...

I copied *.vdi, from one location to another, copy - paste.

After that removed virtual machine from VM box without deleting files. So know when create new win 10 64bit and load Use an existing virtual HDD, i got to Windows repair page.

I cant repair.
I am using 6.1.32 VM box, and vdi has size 27.456.962.560 bytes.

Can anybody give me a hint how to realive image....

Thank you all

[scottgus1]

I copied *.vdi, from one location to another, copy - paste.

There's a Virtualbox Move command for this, in the Virtual Media Manager, that keeps the VM intact without requiring deleting and rebuilding.
It's actually better to move the whole VM, rather than just the vdi drive file. There's also a Virtualbox Move command for this: right-click the VM in the list, Move.

Did you do a file-compare after the copy, to confirm the integrity of the copy?

I copied *.vdi

Is the * just a placeholder for the real name of the .vdi, or did you really command a copy of all .vdi's? What was the name(s) of the vdi(s) you copied? If the name was a series of seemingly random numbers, then that was a snapshot disk, which is not standalone.

After that removed virtual machine from VM box without deleting files.

Not a good idea. You basically took the hard drive out of a computer and threw away the computer. The computer's motherboard ID is probably used in the VM OS's activation. So you'll need to reactivate the OS etc if you can get the OS running again.

I copied...
Can anybody give me a hint how to realive image....

Try the copy again? Also restore the original VM from your backups. The problems with Windows Repair would be better suited for a Microsoft forum.

[markomladenovic]

THX scottgus1,

I understand now what I did, and where are errors.
I didn't check integrity, I just copied because lack off space.

*.vdi means win10 64bit.vdi

Not a good idea. You basically took the hard drive out of a computer and threw away the computer. The computer's motherboard ID is probably used in the VM OS's activation. So you'll need to reactivate the OS etc if you can get the OS running again

I can create virtual machine again, and load *.vdi and start, but all I got is this image:

[markomladenovic]

i cant upload photos, because rules.

[scottgus1]

i cant upload photos web links, because rules.

FTFY.

Pictures can be posted using the forum's Upload Attachment tab on the first day first post.

[markomladenovic]

Hallo guys,

can you help me with solution how to solve crashed Windows 10 virtual machine, because faulty coping procedure of virtual machine?

I made wrong decision to copy paste image file vdi, and now I cant start Windows in Virtual machine.

Every time machine starts, and goes to Automatic repair, without success to repair.

Is there possibility to repair during booting Windows.
VMBox 6.1.32
Windows 10 64bit Home

[mpack]

Please do not open multiple topics to discuss one issue. I have merged your new topic with your existing one.

I suggest that you copy the source VM again as Scott already suggested. This time make sure to copy the entire VM folder, and also ensure that any intermediate removable drive is formatted with a filesystem that allows large files, i.e. format it with NTFS or exFAT.

Once the VM folder is copied to the destination PC, double click the .vbox file (the machine settings file) to register the VM. You may need to disable the Windows option "Hide extensions of known file types" in order to see the ".vbox" extension.

If you no longer have the original VM folder contents then you will need to create a new VM with settings as close as possible to the old VM, however the guest OS will still have lost activation.

[markomladenovic]

Hallo guys, i found all files, but same result, machine doesnt boot to Windows 10.

Can anybody take a look at log file?

There are first log file and todays.

last one https://we.tl/t-GZbOoU3Fhd

first one https://we.tl/t-LJ60crrXkO

if you see what is the problem, please describe me how to solve.

[scottgus1]

Please zip and post the log files using Upload Attachment, same as you did the screenshots.

Also, if the original VM still boots, please provide a log from that VM, too. Label which is which.

[markomladenovic]

Thanks scottgus1

These are all log files from crashed VM.
First one in with date 05042022 time 1116, name VBox.log3_05042022_1116
Last one, from today Vbox.log.rar

Rest are intermediate time.

When I start machine, it start to boot, with windows circle turning and after that it restart and start with automatic repair page.

I did total repair with "Save user data", but all programs are deleted.

Machine can't be started in Windows safe mode, also.

[markomladenovic]

To be clear, I repaired copy of original vdi file.

[scottgus1]

The log does not show any Virtualbox 'hardware' issues. But the VM could run better on two processors, not just the one it has now. Windows 10 adores two processors, and the host has room.

Does the original VM still boot?

[markomladenovic]

I changed to 4 processors.

When I run the VM, I got those two screens

[scottgus1]

I changed to 4 processors.

the VM could run better on two processors

4 != 2. Your host does not have room for a 4-processor VM.


I think this is the third time I've asked this question:

Does the original VM still boot?

[markomladenovic]

I dont have original VM, because i removed it from VMBox manager with command Remove (and after that I choose Remove only, without deleting files).
After that I copied vdi file from VM folder C:\Users\m.mladenovic\VirtualBox VMs\win 10 64bit to server (only VDI file).
Few days after I copied vdi file to external SSD, created new machine (same computer - same memory, disk space, number of processors), with a different name.
When I started VM, it try to boot, but it cannot.

If I remember originaly it was 6.30 VMBox, now is 6.31. Can that be a problem?