Page 1 of 1
Failed to open a session for the virtual machine
Posted: 26. Apr 2022, 14:21
by TomNG
Failed to open a session for the virtual machine 513CG_01.
The virtual machine '513CG_01' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'E:\VirtualBox VMs\513CG_01\Logs\VBoxHardening.log'.
Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
Could please help to fix?? for the VBox.lag is attached link as follows:
https://drive.google.com/file/d/1eou_c1 ... sp=sharing
Re: Failed to open a session for the virtual machine
Posted: 26. Apr 2022, 14:22
by mpack
Please zip log files and attach them here, using "Upload attachment" when composing the post.
Also you'll notice that the error message mentions the VBoxHardening.log file. Please include that in the zip.
Re: Failed to open a session for the virtual machine
Posted: 26. Apr 2022, 14:36
by TomNG
mpack wrote:Please zip log files and attach them here, using "Upload attachment" when composing the post.
Also you'll notice that the error message mentions the VBoxHardening.log file. Please include that in the zip.
The file is too big, maximum allowed size is 256 KiB. I try to upload to drive for your download.
https://drive.google.com/file/d/1UVM3pm ... sp=sharing
Re: Failed to open a session for the virtual machine
Posted: 26. Apr 2022, 15:07
by mpack
Log files are not too big when zipped. I have never seen one exceed 256KB.
Re: Failed to open a session for the virtual machine
Posted: 26. Apr 2022, 15:13
by TomNG
mpack wrote:Log files are not too big when zipped. I have never seen one exceed 256KB.
Can you download the above link??
Re: Failed to open a session for the virtual machine
Posted: 26. Apr 2022, 15:15
by TomNG
This is VBoxHardening log
Re: Failed to open a session for the virtual machine
Posted: 26. Apr 2022, 15:19
by mpack
You have Avast antivirus installed. Make sure that hardware virtualization is disabled in the AV settings.
Note also that Windows 7 is no longer a supported host, though for the moment it still seems to work.
Re: Failed to open a session for the virtual machine
Posted: 26. Apr 2022, 15:23
by TomNG
mpack wrote:You have Avast antivirus installed. Make sure that hardware virtualization is disabled in the AV settings.
Note also that Windows 7 is no longer a supported host, though for the moment it still seems to work.
AV hardware virtualization is disabled but VM dose not open.
Re: Failed to open a session for the virtual machine
Posted: 26. Apr 2022, 15:26
by TomNG
mpack wrote:You have Avast antivirus installed. Make sure that hardware virtualization is disabled in the AV settings.
Note also that Windows 7 is no longer a supported host, though for the moment it still seems to work.
Are you mean that window7 7 host will not supported but the VM still can run windows 7? Am i right?
Re: Failed to open a session for the virtual machine
Posted: 26. Apr 2022, 15:53
by TomNG
mpack wrote:You have Avast antivirus installed. Make sure that hardware virtualization is disabled in the AV settings.
Note also that Windows 7 is no longer a supported host, though for the moment it still seems to work.
Avast antivirus is disabled. Then, the VM can open the windows now. thank you for your support
Re: Failed to open a session for the virtual machine
Posted: 26. Apr 2022, 22:00
by Malon
Failed to open a session for the virtual machine kali linux.
The virtual machine 'kali linux' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\DON\VirtualBox VMs\kali linux\Logs\VBoxHardening.log'.
Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
Could please help to fix??attached bellow is the VBoxHardening log file
Re: Failed to open a session for the virtual machine
Posted: 27. Apr 2022, 08:49
by mpack
Please start your own topic, it is not polite to hijack someone else's topic with an irrelevant post (you have neither a Win7 host nor Avast antivirus).
In your own topic, attach a zip containing both VBox.log and VBoxHardening.log.