the next version of VirtualBox 5.0.16 will correct the following error message
vbox_e_file_error
(0x80bb00040)
next versions of VirtualBox
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: next versions of VirtualBox
Will it? I didn't know the developers passed such information on until the changelog was posted with the download. As of Feb. 3 2016, 12:51 PM Eastern time, the latest public version is 5.0.14. Where did you get your info, Blog?
-
Martin
- Volunteer
- Posts: 2562
- Joined: 30. May 2007, 18:05
- Primary OS: Fedora other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: XP, Win7, Win10, Linux, OS/2
Re: next versions of VirtualBox
Looks more like a question from someone without better english knowledge.
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: next versions of VirtualBox
I would need to better understand the context of the error. To me it reads as a host file error, which a new version of VirtualBox will not fix.
This error has been reported in the past in the context of trying to unpack a corrupted or truncated OVA.
This error has been reported in the past in the context of trying to unpack a corrupted or truncated OVA.
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: next versions of VirtualBox
@blogdoguib: Today you started creating numerous cross posts of this issue, which I just deleted, as cross posting is against the forum rules. Please do not keep doing that.
In future please provide a VM log file when asking questions, and provide a proper description of the problem and its context. I appreciate that English may not be your first language, in which case you might find it easier to use your native language and let us rely on Translate tools.
To provide a VM log file: Make sure the VM is shut down (not suspended), then right click it in the manager list. Select "Show Log" and save "VBox.log" (ONLY) to a zip file. Attach the zip to your message.
In future please provide a VM log file when asking questions, and provide a proper description of the problem and its context. I appreciate that English may not be your first language, in which case you might find it easier to use your native language and let us rely on Translate tools.
To provide a VM log file: Make sure the VM is shut down (not suspended), then right click it in the manager list. Select "Show Log" and save "VBox.log" (ONLY) to a zip file. Attach the zip to your message.