Opened 4 years ago
Closed 4 years ago
#20267 closed defect (invalid)
Can't Start My Virtual Machine Suddenly
Reported by: | SamSepiol01 | Owned by: | |
---|---|---|---|
Component: | virtual disk | Version: | VirtualBox 6.1.18 |
Keywords: | kali, kalilinux, kali linux | Cc: | |
Guest type: | other | Host type: | Windows |
Description (last modified by )
Hello Everyone, yesterday i wanted to start kali linux in My VirtualBox and then i got this error
The object functionality is limited. Fehlercode: E_ACCESSDENIED (0x80070005) Komponente: MachineWrap Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
I researched on the Web and found some articles like changing something in the VirtualBox Files nothing helped. The last thing i remember was My VirtualBox Froze and then i closed it and turned off my pc. later when i tried to start it over my shortcut it showed the error i pasted above. If i try to start The Machine Manually over the VB Manager it says Document is empty... Somethings i have to say My Pc's Space is Very Low it have's like 5-6 GB left. I Home some1 can help. Greetings, Sam.
Attachments (4)
Change History (11)
by , 4 years ago
Attachment: | virtualboxerror.PNG added |
---|
by , 4 years ago
Attachment: | virtualboxerror2.PNG added |
---|
by , 4 years ago
Attachment: | virtualboxerror3.PNG added |
---|
by , 4 years ago
Attachment: | virtuaalboxerror4.PNG added |
---|
comment:1 by , 4 years ago
Description: | modified (diff) |
---|
follow-up: 3 comment:2 by , 4 years ago
comment:3 by , 4 years ago
Replying to janitor:
Your
Kali Linux.vbox
file seems corrupted (size 0). You can copy theKali Linux.vbox-prev
backup file over to get back to the previous state (you will lose the last change you made to that VM).
ok so what should i do after copying it. shall i delete the current machine?
comment:5 by , 4 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
follow-up: 7 comment:6 by , 4 years ago
Resolution: | invalid |
---|---|
Status: | closed → reopened |
I had the same problem and created a new virtual machine using the same vhd file. It worked ok.
comment:7 by , 4 years ago
Resolution: | → invalid |
---|---|
Status: | reopened → closed |
Replying to Paulino:
I had the same problem and created a new virtual machine using the same vhd file. It worked ok.
That is nice, but that's not a reason to reopen this report.
Your
Kali Linux.vbox
file seems corrupted (size 0). You can copy theKali Linux.vbox-prev
backup file over to get back to the previous state (you will lose the last change you made to that VM).