VirtualBox Solved VBOX_E_FILE_ERROR 0x80BB0004

Recently I wanted to share a VirtualBox Appliance with a colleague. So I tried to export the created appliance. Unfortunate this failed with a:

VBoxManage.exe: error: Code VBOX_E_FILE_ERROR (0x80BB0004) – File not accessible or erroneous file contents (extended info not available)

So I thought why not just copy it… Oh wait, first compact it to save some space and time using VBoxManage modifyvdi some.vdi compact:

>VBoxManage modifyvdi Windows7.vdi compact
Progress state: VBOX_E_FILE_ERROR
VBoxManage.exe: error: Code VBOX_E_FILE_ERROR (0x80BB0004) - File not accessible or erroneous file contents (extended info not available)

When I tried to copy or zip the file there were errors accessing it. Somehow the VirtualBox Appliance was still running fine. The files that make up the appliance weren’t locked.


My laptop (the host of the appliance) is is running Windows7 and I decide to run chkdsk and found:

CHKDSK controleert de bestandsgegevens (stap 4 van 5)...
Leesfout met status 0xc0000185 op offset 0x17410c9000 voor 0x10000 bytes.
Leesfout met status 0xc0000185 op offset 0x17410d6000 voor 0x1000 bytes.
Er zijn beschadigde clusters in bestand 37907 met naam \Users\ppvdbeek\VIRTUA~2\Windows7\Windows7.vdi vervangen.

This is Dutch stating that there were bad sectors in the vdi file that had to be corrected. After that, I could run the appliance, compact the disk and export the appliance successful.

On Linux you could use fsck (for “file system check”) in a similar case.

18 thoughts on “VirtualBox Solved VBOX_E_FILE_ERROR 0x80BB0004

  1. Pingback: deltaloungeHow to VirtualBox overview - deltalounge

  2. John

    i have the problem too

    Failed to create a new virtual machine.

    Machine settings file ‘C:\Users\Anson Zhao\VirtualBox VMs\Windows 8\Windows 8.vbox’ already exists.

    Result Code: VBOX_E_FILE_ERROR (0x80BB0004)
    Component: Machine
    Interface: IMachine {5eaa9319-62fc-4b0a-843c-0cb1940f8a91}
    Callee: IVirtualBox {c28be65f-1a8f-43b4-81f1-eb60cb516e66}

  3. PeterPaul Post author

    Two ways to solve this:
    * delete the ‘C:\Users\Anson Zhao\VirtualBox VMs\Windows 8\Windows 8.vbox’ file that is already there from a previous try.
    * Use another name for the virtual machine


  4. David Rader

    This is the first hit I get on google for an export appliance eror: virtualbox export appliance “file not accessible or erroneous file contents”. In my case, the error was not bad sectors but rather the simple fact that my disks within the vm were .qcow, which appears to not be supported by the export process (it would be nice if the error simply said .qcow disks are not supported but it does not).

    My solution was to convert my .qcow images to .vdi images (qemu-img convert -f qcow -O vdi ) and then the export worked without an issue.

    Hope this helps someone else.

  5. Lando

    Hey guys maybe I can get some help.

    I just imported my VM Virtualbox (Linux) file on my flash drive from a desktop which is from where I created the file Using Oracle. I then connected my flash drive into my laptop to try running my file linuxVM32bit and it gave me an error
    Result Code:
    VBOX_E_FILE_ERROR (0x80BB0004)

    Can you help me here please thanks.

  6. Chris

    Problem solved. Thanks David Rader!

    I had a VHD-image that failed on export.

    File not accessible or erroneous file contents.

    Resultaatcode:VBOX_E_FILE_ERROR (0x80BB0004)
    Interface:IAppliance {8398f026-4add-4474-5bc3-2f9f2140b23e}

    Inspired by your story, I converted my VHD to VDI first, added it as new machine, et voilá! The eport succeeded.

  7. Madison

    Im still very confused on what to do.

    Im on a Robotics team and use the FTC AppInventor, but i dont know if that’ll make a difference please help!

    Result Code: VBOX_E_FILE_ERROR (0x80BB0004)
    Component: MachineWrap
    Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

  8. GEGE

    Its funy but this problem dont happen when I open the kali linux in VMware played but its hppen when I opened In virtual box and also the file its in format for Virtual box.

  9. Pingback: Virtualbox Bus Error

  10. hrx

    Hi! Thank you for your solution. I converted vhd disk to vdi and then extracted ova applicance. Go to “File–>Virtual Media manage –> Copy” Select your disk and copy it like vdi. Then in VB under “Storage” select your IDE Primary disk this vdi disk. You can delete vhd disk. Than you can export your appliance :))

  11. JBravo686

    Was also getting VBOX_E_FILE_ERROR (0x80bb0004) in the log file after VM refused to start. In the log file, aText read:

    “VM cannot start because the saved state file ‘C:\Users\me\VirtualBox VMs\Ubuntu 16.04\Ubuntu 16.04\Snapshots\2019-08-29T12-59-21-090119800Z.sav’ is invalid (VERR_FILE_NOT_FOUND).”

    It recommended erasing the saved state file and restarting. That did not work. Erased ALL the saved state files (in the ..\Snapshots folder). That didn’t work either.

    Went into the .vbox file (its XML) and found the variable lastStateChange=”2019-08-29T12:59:40Z” and erased that (since the original error message also stated something about the state being wrong). Also erased stateFile=”Snapshots/2019-08-29T12-59-21-090119800Z.sav” for good measure. Saved the .vbox file, restarted the VM, everything is working.

  12. Mohd Abdul Mujib

    Maybe the original Image is “Fixed” size and you are trying to convert that into “Dynamically Allocated” and thats the reason you get “Parameter Error”.

Leave a Reply

Your email address will not be published. Required fields are marked *