Virtualbox error rc 0x80bb0001

virtualbox.org

End user forums for VirtualBox

• Board index‹General‹VirtualBox on Windows Hosts
• Change font size
• Print view

• FAQ
• Login

[SOLVED] 0x80bb0001 and 0x80bb000c freeze Virtualbox and forces PC reboot

[SOLVED] 0x80bb0001 and 0x80bb000c freeze Virtualbox and forces PC reboot

by DeGarcen » 17. May 2020, 22:08

Re: 0x80bb0001 and 0x80bb000c freeze Virtualbox and forces PC reboot

by DeGarcen » 17. May 2020, 22:14

Re: 0x80bb0001 and 0x80bb000c freeze Virtualbox and forces PC reboot

by DeGarcen » 17. May 2020, 22:34

Restarting the service does not prevent from having to reboot the computer. Not only that, but trying to launch again after that just duplicates the process several times:
Code: Select all Expand viewCollapse view pwsh.exe -c Restart-Service VBoxSDS
Code: Select all Expand viewCollapse view pwsh.exe -c Get-Process -name Virtualbox

NPM(K) PM(M) WS(M) CPU(s) Id SI ProcessName
—— —— —— —— — — ————
20 52.91 86.52 0.88 5296 1 VirtualBox
21 52.92 86.32 0.81 11040 1 VirtualBox
20 52.13 85.64 1.00 17908 1 VirtualBox
20 51.86 85.48 0.97 19836 1 VirtualBox
20 52.18 85.88 1.00 25840 1 VirtualBox

Re: 0x80bb0001 and 0x80bb000c freeze Virtualbox and forces PC reboot

by scottgus1 » 17. May 2020, 23:09

If you revert to the older version you were running, can you use the main Virtualbox window as normal?

Also, assuming that you’re running a Windows host from the forum posted in, try this:

Disable any autostart guests. Restart the host so no Virtualbox processes are running.
Go to C:\Users\ and move the .Virtualbox folder (note the period starting the folder name) to the desktop.
Start Virtualbox. The guest list will be empty, and all File menu Preferences modifications will be reset. (All the guests are still available, just need to be re-registered.)
In the main Virtualbox window, use the Machine menu Add command. Go to each guest’s folder EXCEPT for «manjaro-kde» and register the .vbox file. See if the main Virtualbox window remains stable.
Now, lastly, register «manjaro-kde». See if the window is still stable or crashes when you select «manjaro-kde» in the guest list.

If the main Virtualbox window stays stable with «manjaro-kde» selectable, then it was just a glitch. Use the old .Virtualbox folder’s Virtualbox.xml file for comparison and manually reset the File menu Preferences, possibly Host-Only and NATNetworks.

If the main window goes squiffly when «manjaro-kde» is registered, then zip that guest’s .vbox file and another working guest’s .vbox file, and post the zip file, using the forum’s Upload Attachment tab.

Re: 0x80bb0001 and 0x80bb000c freeze Virtualbox and forces PC reboot

by DeGarcen » 18. May 2020, 00:39

Источник

virtualbox.org

End user forums for VirtualBox

• Board index‹Guest systems‹Windows Guests
• Change font size
• Print view

• FAQ
• Login

VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)

VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)

by Asper » 7. Oct 2011, 09:33

I work with a Windows XP host with a Windows XP guest, the release of VirtualBox and of GuestAdditions are aligned.
After that I have updated at version 4.1.4, I experience this issue: every time I start VitualBox the guest machine is inaccessible.
The VirtualBox interface shows the inaccessible machine and it gives the following error:
Code: Select allExpand viewCollapse view Could not find an open hard disk with UUID <7e9b1544-60b6-4c4c-afb3-66571dafc088>.
Codice ‘uscita: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
Componente: VirtualBox
Interfaccia: IVirtualBox
To remove the issue, I have found the following procedure:

1- I delete the inaccessible machine;
2- I create a new machine with the same hard disk, the procedure is successful;
3- I remove the just created machine;
4- I add the machine that was previously inaccessible and the procedure is successful;
5- I can use the machine and the Windows XP guest works correctly; on guest exit, I perform a successful Windows shutdown.

The next time I start VirtualBox, the guest machine is again inaccessible!

What can I do to remove the issue permanently?

Re: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)

by mpack » 7. Oct 2011, 16:17

Please post (as an attachment) the .vbox file for that virtual machine. I believe «.vbox» is not an allowed attachment type, so for that reason and to save space, please make it into a .zip first.

It will do no harm if you also include your «VirtualBox.xml» file in the same zip, although if the VM in question was created in VirtualBox v4.0 or later then VirtualBox.xml should not be relevant.

Re: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)

by Asper » 7. Oct 2011, 16:49

Hi mpack,
please find attached the file *.vbox and the file VirtualBox.xml.

Re: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)

by mpack » 7. Oct 2011, 17:04

Well, I don’t know what happened, but the hard disk referenced by this VM does not exist in any media registry — it isn’t in the .vbox file, and it isn’t in VirtualBox.xml either.

I have modified your .vbox to remove the bad reference. I could not convert it to a good reference because I don’t know what VDI file name to use. Please unpack the attachment and use the contents to replace your existing .vbox file. Neither the VirtualBox UI nor any VMs can be running at the time .

Before you can run the VM you must edit the Storage settings: in the left panel, beside your IDE controller, are two little icons for adding attachments. The second little icon is «Add hard disk». Use the latter to add your hard disk to the VM.

That should fix your problem.

Re: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)

by Asper » 11. Oct 2011, 11:16

Hi mpack,
I have tested your suggestion and It works fine. Thank you very much!

The defected virtual machine was created with the new clone tool available on the graphic user interface. Could be something wrong in the clone tool that has created the reported issue?

Re: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)

by mpack » 11. Oct 2011, 12:20

Anything is possible, but I have used that new clone tool several times myself (and many others on this site have mentioned using it as well), with no problems at all.

I’d be inclined to look at the source VM which was cloned. For example, I’d be interested to know if it owns its own hard disk, or borrows it from another VM, or anything else unusual about it.

Re: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)

by Asper » 11. Oct 2011, 13:09

Hi mpack.
please find attached the vbox file of the source VM from which the clone was created.

The source VM was created from zero by installing Windows XP, with VirtualBox 4.0.4.

Starting from VirtualBox 4.1.4., I have moved the VMs folder to an other hard disk, from c: to f:, by changing the appropriate setting in the VirtualBox UI and manually moving the VMs folder content.

Re: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)

by mpack » 11. Oct 2011, 13:44

Well, I see nothing odd about the original VM, so your glitch remains a mystery.

I assume that «the appropriate setting in the VirtualBox UI» was the default machine folder: just FYI, that preference setting controls where new VMs will be created, it has no effect on existing VMs. Is it possible that you moved the VDI file before you cloned the old VM? I can imagine that a non-existing VDI file could certainly result in losing it from the clone, but of course I have not tested that theory.

To move a v4 VM (*) the correct procedure is to remove the existing VM from the UI (saying no when it asks if you want to delete the associated host files), then move the VM folder to its new location, then use «Machine | Add» to add the VM back from its new home.

(*) Readers please note that VMs created by VirtualBox v3 (even if you now use v4) can’t be moved this easily.

Re: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)

by Tirrawarra » 15. Nov 2011, 11:13

Hi the same has just happened to me. Ive spent 3-4 hours trying to find a solution an dam wondering if anyone can help.
I am running Ubuntu 10.04LTS as host
Windows XP SP3 as guest and have the following error:

Could not find an open hard disk with UUID <1d8abb98-f84a-4dba-af98-0931fac2c35f>.
Result Code:
VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
Component:
VirtualBox
Interface:
IVirtualBox

everything was working well till I tried to take a snapshot — which never seemed to happen. (i must say I was distracted by the «clone» (sheep) image which Id never seen before. I have weeks of client work in this VM — so any help or guidance would be much appreciated.

Re: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)

by mpack » 15. Nov 2011, 13:47

If you saw a sheep icon then you were making a clone, not taking a snapshot, and cloning would not have damaged the existing VM in any way: it will have resulted in the creation of a new VM which was at least as functional as the old (i.e., not at all, if the old was not working).

I suspect I’m not hearing the whole story, so I’m going to stop there for now.

Re: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)

by Binho » 5. Apr 2012, 13:25

The VBOX file of the original VM has the reference for the VDI file but the file VBOX of the copied VM does not have the reference for the VDI file. See:

Источник

virtualbox.org

End user forums for VirtualBox

• Board index‹General‹VirtualBox on Windows Hosts
• Change font size
• Print view

• FAQ
• Login

[SOLVED] 0x80bb0001 and 0x80bb000c freeze Virtualbox and forces PC reboot

[SOLVED] 0x80bb0001 and 0x80bb000c freeze Virtualbox and forces PC reboot

by DeGarcen » 17. May 2020, 22:08

Re: 0x80bb0001 and 0x80bb000c freeze Virtualbox and forces PC reboot

by DeGarcen » 17. May 2020, 22:14

Re: 0x80bb0001 and 0x80bb000c freeze Virtualbox and forces PC reboot

by DeGarcen » 17. May 2020, 22:34

Restarting the service does not prevent from having to reboot the computer. Not only that, but trying to launch again after that just duplicates the process several times:
Code: Select all Expand viewCollapse view pwsh.exe -c Restart-Service VBoxSDS
Code: Select all Expand viewCollapse view pwsh.exe -c Get-Process -name Virtualbox

NPM(K) PM(M) WS(M) CPU(s) Id SI ProcessName
—— —— —— —— — — ————
20 52.91 86.52 0.88 5296 1 VirtualBox
21 52.92 86.32 0.81 11040 1 VirtualBox
20 52.13 85.64 1.00 17908 1 VirtualBox
20 51.86 85.48 0.97 19836 1 VirtualBox
20 52.18 85.88 1.00 25840 1 VirtualBox

Re: 0x80bb0001 and 0x80bb000c freeze Virtualbox and forces PC reboot

by scottgus1 » 17. May 2020, 23:09

If you revert to the older version you were running, can you use the main Virtualbox window as normal?

Also, assuming that you’re running a Windows host from the forum posted in, try this:

Disable any autostart guests. Restart the host so no Virtualbox processes are running.
Go to C:\Users\ and move the .Virtualbox folder (note the period starting the folder name) to the desktop.
Start Virtualbox. The guest list will be empty, and all File menu Preferences modifications will be reset. (All the guests are still available, just need to be re-registered.)
In the main Virtualbox window, use the Machine menu Add command. Go to each guest’s folder EXCEPT for «manjaro-kde» and register the .vbox file. See if the main Virtualbox window remains stable.
Now, lastly, register «manjaro-kde». See if the window is still stable or crashes when you select «manjaro-kde» in the guest list.

If the main Virtualbox window stays stable with «manjaro-kde» selectable, then it was just a glitch. Use the old .Virtualbox folder’s Virtualbox.xml file for comparison and manually reset the File menu Preferences, possibly Host-Only and NATNetworks.

If the main window goes squiffly when «manjaro-kde» is registered, then zip that guest’s .vbox file and another working guest’s .vbox file, and post the zip file, using the forum’s Upload Attachment tab.

Re: 0x80bb0001 and 0x80bb000c freeze Virtualbox and forces PC reboot

by DeGarcen » 18. May 2020, 00:39

Источник

virtualbox.org

End user forums for VirtualBox

• Board index‹General‹VirtualBox on Windows Hosts
• Change font size
• Print view

• FAQ
• Login

[SOLVED] 0x80bb0001 and 0x80bb000c freeze Virtualbox and forces PC reboot

[SOLVED] 0x80bb0001 and 0x80bb000c freeze Virtualbox and forces PC reboot

by DeGarcen » 17. May 2020, 22:08

Re: 0x80bb0001 and 0x80bb000c freeze Virtualbox and forces PC reboot

by DeGarcen » 17. May 2020, 22:14

Re: 0x80bb0001 and 0x80bb000c freeze Virtualbox and forces PC reboot

by DeGarcen » 17. May 2020, 22:34

Restarting the service does not prevent from having to reboot the computer. Not only that, but trying to launch again after that just duplicates the process several times:
Code: Select all Expand viewCollapse view pwsh.exe -c Restart-Service VBoxSDS
Code: Select all Expand viewCollapse view pwsh.exe -c Get-Process -name Virtualbox

NPM(K) PM(M) WS(M) CPU(s) Id SI ProcessName
—— —— —— —— — — ————
20 52.91 86.52 0.88 5296 1 VirtualBox
21 52.92 86.32 0.81 11040 1 VirtualBox
20 52.13 85.64 1.00 17908 1 VirtualBox
20 51.86 85.48 0.97 19836 1 VirtualBox
20 52.18 85.88 1.00 25840 1 VirtualBox

Re: 0x80bb0001 and 0x80bb000c freeze Virtualbox and forces PC reboot

by scottgus1 » 17. May 2020, 23:09

If you revert to the older version you were running, can you use the main Virtualbox window as normal?

Also, assuming that you’re running a Windows host from the forum posted in, try this:

Disable any autostart guests. Restart the host so no Virtualbox processes are running.
Go to C:\Users\ and move the .Virtualbox folder (note the period starting the folder name) to the desktop.
Start Virtualbox. The guest list will be empty, and all File menu Preferences modifications will be reset. (All the guests are still available, just need to be re-registered.)
In the main Virtualbox window, use the Machine menu Add command. Go to each guest’s folder EXCEPT for «manjaro-kde» and register the .vbox file. See if the main Virtualbox window remains stable.
Now, lastly, register «manjaro-kde». See if the window is still stable or crashes when you select «manjaro-kde» in the guest list.

If the main Virtualbox window stays stable with «manjaro-kde» selectable, then it was just a glitch. Use the old .Virtualbox folder’s Virtualbox.xml file for comparison and manually reset the File menu Preferences, possibly Host-Only and NATNetworks.

If the main window goes squiffly when «manjaro-kde» is registered, then zip that guest’s .vbox file and another working guest’s .vbox file, and post the zip file, using the forum’s Upload Attachment tab.

Re: 0x80bb0001 and 0x80bb000c freeze Virtualbox and forces PC reboot

by DeGarcen » 18. May 2020, 00:39

Источник