I recently reinstalled VirtualBox 4.3.2 after removing it previously and imported the WinXP IE8 and Win Vista IE7 Virtual Machines from modern.ie but when I try and boot either I immediately get the error mentioned in the title. It mentioned on import that I would need a virtual hard disk which I have also set up.
I'm running Win 7, here are the entries in my log file:
VirtualBox VM 4.3.2 r90405 win.amd64 (Nov 1 2013 15:06:10) release log
00:00:01.027311 Log opened 2013-11-26T10:02:34.696663400Z
00:00:01.027312 Build Type: release
00:00:01.027316 OS Product: Windows 7
00:00:01.027317 OS Release: 6.1.7601
00:00:01.027319 OS Service Pack: 1
00:00:01.027331 Host RAM: 8190MB total, 4719MB available
00:00:01.027335 Executable: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
00:00:01.027335 Process ID: 4756
00:00:01.027336 Package type: WINDOWS_64BITS_GENERIC
00:00:01.035751 Installed Extension Packs:
00:00:01.035801 None installed!
00:00:01.054349 pdmR3LoadR0U: pszName="VMMR0.r0" rc=VERR_LDR_IMPORTED_SYMBOL_NOT_FOUND szErr="SUPR3LoadModule: supLoadModule returned VERR_LDR_IMPORTED_SYMBOL_NOT_FOUND"
00:00:01.054470 VMSetError: D:\tinderbox\win-4.3\src\VBox\VMM\VMMR3\VM.cpp(594) int __cdecl vmR3CreateU(struct UVM *,unsigned int,int (__cdecl *)(struct UVM *,struct VM *,void *),void *); rc=VERR_LDR_IMPORTED_SYMBOL_NOT_FOUND
00:00:01.054473 VMSetError: Failed to load VMMR0.r0
00:00:01.054745 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={8ab7c520-2442-4b66-8d74-4ff1e195d2b6} aComponent={Console} aText={Failed to load VMMR0.r0 (VERR_LDR_IMPORTED_SYMBOL_NOT_FOUND)}, preserve=false
00:00:01.112567 Power up failed (vrc=VERR_LDR_IMPORTED_SYMBOL_NOT_FOUND, rc=E_FAIL (0X80004005))
I've tried searching and can't find anything that fixes the issue.
Thanks
Error 0X80004005 on fresh install of Virtual Box and VMs
-
noteirak
- Site Moderator
- Posts: 5231
- Joined: 13. Jan 2012, 11:14
- Primary OS: Debian other
- VBox Version: OSE Debian
- Guest OSses: Debian, Win 2k8, Win 7
- Contact:
Re: Error 0X80004005 on fresh install of Virtual Box and VMs
Did you use a previous version than 4.3.2 ? If yes, did it work before 4.3.2?
Are able to create a new VM and run it? Is the error limited to only this imported VM?
Are able to create a new VM and run it? Is the error limited to only this imported VM?
Hyperbox - Virtual Infrastructure Manager - https://apps.kamax.lu/hyperbox/
Manage your VirtualBox infrastructure the free way!
Manage your VirtualBox infrastructure the free way!
Re: Error 0X80004005 on fresh install of Virtual Box and VMs
Yes I used a previous version and it worked. An Android VM seemed to completely corrupt VirtualBox. I can't use any VMs. I just tried to set up a Ubuntu one and that gave me the same error.
-
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: Error 0X80004005 on fresh install of Virtual Box and VMs
A VM is just a data file when it isn't running. A data file can't corrupt anything. Also, VirtualBox is a PC simulator - it doesn't much matter to VirtualBox what code is running inside that simulation (e.g. DOS, Android, some kind of "bare metal" app of your own devising etc). So the idea that it would be sensitive to a particular guest OS - particularly an unsupported guest OS (*) - to the extent that host modules are corrupted or (un)installed... is just not credible.jm_taylor wrote:An Android VM seemed to completely corrupt VirtualBox.
And btw, I have an Android VM running under v4.3.2 right here. I tested it just a moment ago to be sure.
(*) Supported guest OS's can have Guest Additions installed to allow interaction with the host, which therefore could conceivably affect the host in some way. That isn't an option for an unsupported guest.
Re: Error 0X80004005 on fresh install of Virtual Box and VMs
Ok fair enough. I'm not really overly familiar with how VMs work. All I know is that they were working, then I installed an Android VM which ran on top of VBox in someway and after that I couldn't even startup VBox, it just crashed everytime.
I'm not bothered about that though, I'd just like to get my fresh install working.
I'm not bothered about that though, I'd just like to get my fresh install working.
-
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: Error 0X80004005 on fresh install of Virtual Box and VMs
Just make sure VBox is uninstalled properly via the control panel. Make sure that the folders "<userdoc>\.VirtualBox", "<userdoc>\VirtualBox VMs" and "<Program Files\Oracle\VirtualBox" no longer exist. Reboot host to ensure any drivers are unloaded.
Then reinstall, making sure you have admin rights and don't omit anything.
Then reinstall, making sure you have admin rights and don't omit anything.