Failed to open a session. VERR_NOT_SUPPORTED. E_FAIL

Discussions related to using VirtualBox on Windows hosts.
Post Reply
richard19000
Posts: 2
Joined: 7. Jan 2016, 18:18

Failed to open a session. VERR_NOT_SUPPORTED. E_FAIL

Post by richard19000 »

I have installed Virtual box on a Windows Server 2008 R2 64 bit machine. Have ensured Virtualisation is enabled etc.
When creating a new VM it creates fine but then when I try and start the machine I am presented with a warning message as follows:-

Failed to open a session for the virtual machine {machinename}
Details
Not Supported. (VERR_NOT_SUPPORTED)
Result Code: E_FAIL (0x8004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

I have done exactly the same task on a Windows 7 machine I have and it worked fine so it must be something to do with the Hardware on the 2008 server. After spending many an hour googling around I cannot find what the issue is and am completely pulling my hair out now...

I would appreciate any help anyone can give.

Thanks, Richard
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: Failed to open a session. VERR_NOT_SUPPORTED. E_FAIL

Post by mpack »

Please post the VM log file of an error session. With the VM fully shut down, right click and "Show Log" in the GUI, save "VBox.log" (ONLY) to a zip, and attach the zip here.
richard19000
Posts: 2
Joined: 7. Jan 2016, 18:18

Re: Failed to open a session. VERR_NOT_SUPPORTED. E_FAIL

Post by richard19000 »

Hi mpack
Please find log file attached as requested.

Many thanks
Richard
Attachments
Vbox Log File.zip
(7.32 KiB) Downloaded 10 times
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: Failed to open a session. VERR_NOT_SUPPORTED. E_FAIL

Post by mpack »

I see that you've built a VM around a pre-existing VHD which you have located in the root folder (not a good idea), called "C:\WIndows 7.vhd". I am suspicious of this VHD, I suspect that it is the source of the "not supported" message, i.e. there must be something wrong with it.

Try cloning the VHD to VDI using CloneVDI, see what it has to say about your VHD. If it succeeds (and it probably won't) then please locate the VDI inside the VM folder, discard the VHD from the media register (File|Virtual Media Manager, release and then remove) and instead mount the VDI using the VM storage panel.
Post Reply