[Solved] Failed to open a session for the virtual machine DESKTOP-WINXP PROFESSIONAL

[Iris Leung]

Your help is appreciated.
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}

With Endless Blessings in the Son of God,
LEUNG, [Ms.]

[socratis]

Is there a VBox.log that goes with that or it doesn't get created at all? Right-click on the VM in the VirtualBox Manager and select "Show Log". Save only the first "VBox.log", ZIP it and attach it to your response (see the "Upload attachment" tab below the reply form).

With Endless Blessings in the Son of God

Which one of all? There are 12 lead characters, and about 25 supporting actors where I come from...

[Iris Leung]

Dear Socratis,
Here's the log, thanks for your help, it's much appreciated.

VirtualBox VM 5.2.7 r120349 win.amd64 (Jan 18 2018 11:34:54) release log
00:00:02.016496 Log opened 2018-01-22T13:08:54.979968100Z
00:00:02.016498 Build Type: release
00:00:02.016501 OS Product: Windows 10
00:00:02.016502 OS Release: 10.0.14393
00:00:02.016502 OS Service Pack: 
00:00:02.057615 DMI Product Name: N752VX
00:00:02.061014 DMI Product Version: 1.0       
00:00:02.061021 Host RAM: 32663MB (31.8GB) total, 27563MB (26.9GB) available
00:00:02.061024 Executable: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
00:00:02.061024 Process ID: 9836
00:00:02.061025 Package type: WINDOWS_64BITS_GENERIC
00:00:02.061545 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:\Users\Iris Leung\VirtualBox VMs\DESKTOP-WINXP PROFESSIONAL\Snapshots\2018-01-22T07-48-41-136506000Z.sav' is invalid (VERR_FILE_NOT_FOUND). Delete the saved state prior to starting the VM}, preserve=false aResultDetail=0
00:00:02.062032 GUI: Aborting startup due to power up issue detected...
00:00:02.062102 GUI: UIMediumEnumerator: Medium-enumeration finished!

With Endless Blessings in the Son of God,
LEUNG, [Ms.]

[socratis]

This is what the log says, I hope that by cropping the unwanted supporting information, the message is clearer:

VM cannot start because the saved state file 'C:\Users\Iris Leung\VirtualBox VMs\DESKTOP-WINXP PROFESSIONAL\Snapshots\2018-01-22T07-48-41-136506000Z.sav' is invalid (VERR_FILE_NOT_FOUND). Delete the saved state prior to starting the VM

PS. Thanks for doing the logical thing and didn't ZIP the VBox.log, it was too small and the gains would be negligible...

[Iris Leung]

Dear Socratis,

Thank you for your suggestion as "Delete the saved state prior to starting the VM", for clarifying of such, may you please do kindly show me the step of doing so?

With Endless Blessings in the Son of God,
LEUNG, [Ms.]

[mpack]

for your suggestion as "Delete the saved state prior to starting the VM", for clarifying of such, may you please do kindly show me the step of doing so?

In the VM manager, right click the VM and choose "Discard saved state" (or the equivalent in local language).

[Iris Leung]

Dear mpack,

It's all solved and fine now. Thank you very much.

With Endless Blessings in the Son of God,
LEUNG, [Ms.]

[mpack]

Thanks for reporting back, I'm glad you got it working.

[sosservice]

dear mpack,

add to vbox.log
please help me.


Atris Technik 2016 VirtualBox sanal makinesi için bir oturum açma başarısız.

The virtual machine 'Atris Technik 2016 VirtualBox' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Yeni klas�r\Atris Technik 2016.1 VirtualBox\Atris+Technik+2016.1+VirtualBox\Atris Technik 2016 VirtualBox\Logs\VBoxHardening.log'.

Sonuç Kodu: E_FAIL (0x80004005)
Bileşen: MachineWrap
Arayüz: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

[mpack]

Your question is unrelated to the subject matter above and hence does not belong in this (Solved) topic. In any case you provided the wrong log: the appropriate log file name was given in the error message.

I suggest that you start your own topic in "Windows Hosts", describe the problem properly, and provide the correct log: i.e. VBoxHardening.log.

Incidentally, you may find it useful to turn off the Windows file manager feature which "Hides extensions of registered file types", since the resulting filename confusion may have contributed towards you being unable to identify the correct log.