Reputation: 163
I'm trying to make a Win 7 64 bit guest machine. When it's time to load the ISO, I try to load it and I get the following error
The VM session was aborted.
Result Code: E_FAIL (0x80004005)
Component: SessionMachine
Interface: ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}
What's a fix for this? Thank you.
Upvotes: 12
Views: 44226
Reputation: 1
This worked!
Allow Oracle VirtualBox to access the folder where you store your VMs. That seemed to work for me. I've spent hours trying many different things like disabling Hyper-V but this seemed to be it. Hope it works for you.
Upvotes: 0
Reputation: 14354
This happened to me in the weirdest of circumstances, it just stopped working out of nowhere on Windows. To check if you have the same problem as me go to "Settings" and then "Shared Folders", try to create new shared folders and deleting them. When you click OK if you get an an error message saying you don't have permission or can't access, then it's user permission issue, go to where the virtual machine is on your file system and make "read", "modify" and "write", hell just select "all" on that folder, or probably better yet the entire Folder containing the application.
Upvotes: 0
Reputation: 51
Upvotes: 0
Reputation: 138
Menu -> Machine -> Discard Saved State...
This worked.
Upvotes: 1
Reputation: 5360
Backed up the last saved snapshot from C:\Users\\VirtualBox VMs\Ubuntu\Snapshots
Go to Machine> Ignore last saved state.
Restart VM.
This worked.
This issue most likely happened for me because my Windows 10 randomly restarted a couple of time, with BSOD.
Error code
Result Code: E_FAIL (0x80004005)
Component: SessionMachine
Interface: ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}
Upvotes: 2
Reputation: 21
Maybe it will help. I turned off sound card , and at virtual machine I had "audio" controller turned on. When I turned off audio controler virtual machine start normaly.
BR Simon
Upvotes: 2
Reputation: 196
I have the same issue, and hopefully there will be a bug-fix for it soon.
In the meantime, I have managed to start the install process (in my case for Linux mint 17.2 rather than windows) by attaching the .iso image in the VirtualBox IDE Storage Settings page rather than the "mount" dialog that causes the error.
Open the settings for your VM in the VirtualBox UI, go to Storage, click on the "empty" entry in the list of IDE Controllers, and select the disk icon over to the right of the screen. Finally, select to "Choose Virtual Optical Disk File", and select your .iso of choice. Then start the VM and it should boot just fine.
I hope it helps for your case too!
Upvotes: 17