I am using Virtualbox 5.1.12 on Ubuntu 16.04 LTS 64 bit host.
The Guest-VM is a small Windows 7 prof System with for online banking only.
The installation is rather new, but was correctly working.
While booting the system today, it was freezing during the startup procedure showing the Ubuntu screen, and it forced me to power off the system.
Rebooting and opening VB was successful, but the Windows VM could not be started.
The error message says: one ore more virtual images cannot be accessed
I tried the snapshots, I tried to clone the VM, I also tried to rename VMs xx.vbox-prev into xx.vbox without any success.
I have no backup, because it is my test system, where I update the production system on another Hardware.
Nevertheless I would like to recover the VM, in order to save the tedious time to aktivate Windows and install the more than 300 Win7 updates.
I hope anyone has an helpful idea.
kind regards
Error: Virtual Images not Accesible
Error: Virtual Images not Accesible
- Attachments
-
- Bildschirmfoto vom 2017-01-02 17-36-06.png (68.38 KiB) Viewed 1021 times
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Error: Virtual Images not Accesible
That's not what the picture says. The error is "File not found". Did you delete any files/snapshots manually (outside of VirtualBox)?itfossil wrote:The error message says: one ore more virtual images cannot be accessed
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.
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.
Re: Error: Virtual Images not Accesible
Thanks for your quick reaction!
No, I did not delete any file. I only renamed as described .vbox-prev into .vbox.
I suppose, that the files, stored in snapshots are corrupted.
I would like to know, how to repair them, but I have no idea how to do it.
in the directory snapshots, no files are displayed.
I tried with Live-CDs ct's desinfect and Notwin-64 but no access.
Best regards
itfossil
No, I did not delete any file. I only renamed as described .vbox-prev into .vbox.
I suppose, that the files, stored in snapshots are corrupted.
I would like to know, how to repair them, but I have no idea how to do it.
in the directory snapshots, no files are displayed.
I tried with Live-CDs ct's desinfect and Notwin-64 but no access.
Best regards
itfossil
- Attachments
-
- Bildschirmfoto vom 2017-01-02 17-32-46.png (124.71 KiB) Viewed 1010 times
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Error: Virtual Images not Accesible
From a terminal type the command:
VBoxBugReport "Win7-mini"
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.
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.