The vm session was closed before any attempt to power it on как исправить

I installed VirtualBox on Windows. I set it up to boot Ubuntu14. I enabled the virtualization option for the CPU to enabled (before that, the VM would not boot up complaining about i686 CPU). I rebooted the OS. After this, when I try starting the VM, it gives the following error:

The VM session was closed before any attempt to power it on.


Result Code: 
E_FAIL (0x80004005)
Component: 
SessionMachine
Interface: 
ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}

What did I do wrong and how can I fix it? Thanks. I did not post on serverfault since this is not a server but a laptop.

asked Sep 26, 2015 at 18:08

discarding the «saved state» of the virtual machine using the virtual box GUI allowed me to launch the Ubuntu VM.

I just had this same issue, and the fix for me (On Windows) was to run Virtual Box as Administrator.

vboxmanage discardstate <vmId>

you can get with vboxmanage list vms

answered Dec 3, 2018 at 14:54

It was a permissions issue for me because I changed the VM folder to a different drive, either try running as administrator or just change the security permissions of the VM root folder to allow full control by anyone. The latter worked for me!

answered Feb 19, 2020 at 0:44

My solution was to clone the VM into an alternative name, and then remove the older one with all the files.

(I already removed the Snapshoots and VM in every way I thought …)

answered Aug 5, 2021 at 12:36

Solution of «Discard Saved State» is still valid at 2022 Cx

answered Jan 2, 2022 at 22:29

answered Mar 11, 2016 at 10:12

I newly installed VirtualBox and try to register a former created virtual machine.
When start it I got the same error. And the «clear saved state» was not-able-to-click. I tried other virtual machines, all the same.
Then I did this:
1)I enabled the CPU virtualization in bios, which was disabled. (not really related but should give another 64 cpu not supported like error sooner or later).
2)I remove and save storage hard disk. Then another error:

............(Access denied.)..........

3)Reopen virtual box in Administrator. or maybe repeat 2.
it works…

answered Jan 18, 2017 at 2:29

I faced the same problem. I resolved it by renaming the .sav file.
Steps to resolve the problem.

1. Select the VM which is having problem and Right click on VM and select ‘show log’ option

2. Find the file name which is saved the VM state like ‘2018-07-03T17-05-16-834993200Z.sav is invalid’ in the logs.

3. Go the path where the .sav file is located and change the file extension to anyother file format.

4. Restart the VM. It works.

Regards
Sridhar Ganji

answered Jul 9, 2018 at 11:13

I hope this answer isn’t too late, but I was in the same problem and finally I solved with two solutions get from different sources.

You must solve the next issue with:

• Open the registry editor. Start > Run > regedit
• Go to: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetservicesVBoxDrv
• Edit the key called Start. Change its value from 1 to 3
• Close the registry editor and restart your computer. After your computer restarts you should be able to use VirtualBox without any issues.

If not you must open cmd as Administrator and type the next command:

sc start vboxdrv

After that try to start the virtual machine.

Hi,

My VirtualBox wont start!

I get the following error message:

The VM session was closed before any attempt to power it on.

Result Code: E_FAIL (0x80004005)
Component: SessionMachine
Interface: ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}

The log info is:

00:00:02.352024 VirtualBox VM 6.0.2 r128162 win.amd64 (Jan 14 2019 14:48:15) release log
00:00:02.352028 Log opened 2019-02-08T04:24:59.973668200Z
00:00:02.352028 Build Type: release
00:00:02.352032 OS Product: Windows 7
00:00:02.352033 OS Release: 6.1.7601
00:00:02.352033 OS Service Pack: 1
00:00:02.692931 DMI Product Name: OptiPlex 9020
00:00:02.695330 DMI Product Version: 01
00:00:02.695336 Host RAM: 16326MB (15.9GB) total, 14276MB (13.9GB) available
00:00:02.695339 Executable: C:Program FilesOracleVirtualBoxVirtualBoxVM.exe
00:00:02.695339 Process ID: 4788
00:00:02.695340 Package type: WINDOWS_64BITS_GENERIC
00:00:02.695645 ERROR [COM]: aRC=VBOX_E_FILE_ERROR (0x80bb0004) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={VM cannot start because the saved state file 'C:Virtual MachinesBRLS001Snapshots2019-02-08T01-35-39-927980700Z.sav' is invalid (VERR_FILE_NOT_FOUND). Delete the saved state prior to starting the VM}, preserve=false aResultDetail=-102
00:00:02.696078 GUI: Aborting startup due to power up issue detected...
00:00:02.696130 GUI: UIMediumEnumerator: Medium-enumeration finished!

I have only recently installed this version (14 days ago) Version 6.0.2 r128162 (Qt5.6.2)

When we installed this version it ran fine. Today we had an unrelated internet outage and so I restarted the computer and now VirtualBox wont start.

I’m running windows 7 professional.

Any ideas?

BRLC wrote:00:00:02.695645 ERROR [COM]: aRC=VBOX_E_FILE_ERROR (0x80bb0004) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={VM cannot start because the saved state file ‘C:Virtual MachinesBRLS001Snapshots2019-02-08T01-35-39-927980700Z.sav’ is invalid (VERR_FILE_NOT_FOUND). Delete the saved state prior to starting the VM}, preserve=false aResultDetail=-102

Please let me know if you want me to explain the error any further…

Thank you for your reply Socratis.

I’ll search the forum here a bit to find out how to do that. I’m sure someone has had to do it before.

Cheers,

BRLC

Thanks will try that in an hour or so when back at the computer.

Next question is why has it savd that error state? How can I stop it from saving that error state?

Will post the result shortly. Hopefully it works.

Cheers.

BRLC wrote:How can I stop it from saving that error state?

Stop it from saving the error state? I’m sorry, but what are you talking about? Please read the error again a little bit closer:

You saved the VM state into a file, and that file (the saved state) went missing, who knows what you did to your computer. When you tried to restart it from that saved state, the file couldn’t be found and you got that error.

Generally speaking, if a program expects a file to be somewhere, and that file isn’t? You get an error.

Ok cool, that makes sense.

Thanks for your help Socratis.

The server is up and running again and seems to be fine. At least I’ll know what to do next time this happens!

Someone can make this post as solved now.

Cheers,

BRLC

BRLC wrote:Someone can make this post as solved now.

Happy to…

I want to report that I think this problem was for me caused by a virtual machine still running in the background.

Unfortunately I also upgraded JIC, so I can’t be sure.

However I did CTRL-ALT DELETE and shut down a running virtual machine.

I upgraded to VirtualBox-6.1.34a-150636-Win, probably from VirtualBox-6.1.22-144080-Win.

After that the same VM that wouldn’t start before, did.