Discussion of Problems due to Hardened Security

[mpack]

@MDCI - Please see the first post in this topic for details of what information is required here, i.e. we need the VBoxStartup.log (zipped).

[MDCI]

@MDCI - Please see the first post in this topic for details of what information is required here, i.e. we need the VBoxStartup.log (zipped).

In c:\Users\<user>\.VirtualBox\ not exist VBoxStartup.log
P.S. I reinstall version 4.3.12

[mpack]

For future reference, VM log files are stored in the <vmname>/Logs subfolder. There is nothing of importance in the ".VirtualBox" folder.

[dhannysndiri]

help me Failed to open a session for the virtual machine dhanny.

The virtual machine 'dhanny' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\USER\VirtualBox VMs\dhanny\Logs\VBoxStartup.log'.

Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

[cdg]

I have a similar problem. VirtualBox 4.3.28 running on Windows 10, 32-bit, Build 10162. Attempting to start the virtual machine results in:

Failed to open a session for the virtual machine Windoze XP.

The virtual machine 'Windoze XP' has terminated unexpectedly during startup with exit code 1 (0x1).
More details may be available in 'C:\Users\Carl\VirtualBox VMs\Windoze XP\Logs\VBoxStartup.log'.

Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

This did NOT occur with Build 10130. This does NOT occur with the 64-bit version. This did NOT occur with Windows7 until 7/09/2015. Obviously a Windows 10 problem, but perhaps there is a Vbox work-a-round besides reverting to Vbox 4.3.12 (which does alleviate the problem).

[dhannysndiri]

I hope they answer as many problems here ...

[chun]

Hi to all!

Im having this problem:

The virtual machine 'CS50 Appliance 2014' has terminated unexpextedly during starup with exit code 1(0x1).

ERROR
Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

123.png (10.49 KiB) Viewed 7662 times

*Virtualbox
v 4.3.28 r 100309

124.png (22.48 KiB) Viewed 7662 times

-------------------------------------------------------------------------
I'm using:
*Windows 7 Ultimate
*eMachine
*Pentium(R) Dual-Core CPU T4400 2.20 GHz
*32 bit
*Microsoft Windows
Version 6.1 (Build 760: Service Pack 1)
-------------------------------------------------
--Anti Malwares---
*Avira Free Antivirus
Product version 15.0.11.574
Search engine 8.03.32.14
Virus definition file 8.11.245.42
Control Center 15.00.11.574
Config Center 15.00.11.574
Luke Filewalker 15.00.11.574
Real-Time Protection 15.00.11.572
Filter 15.00.11.550
Web Protection 15.00.11.572
Scheduler 15.00.11.572
Updater 15.00.11.572
Rootkits Protection 15.00.11.550
Local Decider 15.00.11.572

*HitmanPro.Alert
Version 3.0.42 build 190
*hitmanPro 3.7.9 build 242

*Malwarebytes Anti-Malware (free)
v2.1.61022
------------------------------------------

[MDCI]

Send VBoxStartup
P.S. I would like to see the fixes

[mpack]

@mdci: Please see previous discussion of uxtheme.dll.

[Rufus T. Firefly]

My problem with VIrtualBox 4.3.28 persists:

Host is Windows XP [Version 5.1.2600] with SP3.

VirtualBox.exe cannot even be started. Using SysInternals' FileMon revealed that no application log file is written.

AntiVirus: none (machine isn't connected to anything; has never been and will never be)
Firewall: only the one that is integrated into XP.

Anyone solved this one?

[rnewman]

Hello,
No go with the latest build...

OS - Win7 Professional 64bit - SP1
Trendmicro Office Scan - 11.0.1454
Virtualbox - 4.3.29-101478

Screen shot and startup log attached.

I am happy to assist with debugging. Are there any switches or process that would provide additional diagnostic information?

I have also tried 5.0.0-101495 rc3. Same results. Screen shot and startup log are attached.

Thanks,
Richard

[WildBill64]

I am running Windows 8.1 with all updates installed.

I receive the following error message when I try to start either of my virtual machine:

Failed to open a session for the virtual machine Linux Mint.
The virtual machine 'Linux Mint' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'C:\Users\william.coats\VirtualBox VMs\Linux Mint\Logs\VBoxStartup.log'.
Result Code:
E_FAIL (0x80004005)
Component:
Machine
Interface:
IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

I have attached the log files from both of my virtual machines.

I have System Center Endpoint Protection for my antivirus.
Antimalware Client Version: 4.3.220.0
Engine Version: 1.1.11804.0
Antivirus definition: 1.201.1266.0
Antispyware definition: 1.201.1266.0
Network Inspection System Engine Version: 2.1.11804.0
Network Inspection System Definition Version: 115.3.0.0
Policy Name: Default Client Antimalware Policy
Desktop Endpoint Protection Antimalware Policy
Endpoint Protection Tech Services Team
Policy Applied: 7/8/2015 at 10:02

[cdg]

The same problem, with a slightly different error message, occurs with Vbox 5.0.0

Host: Windows 10, Build 10162, 32-bit version, no AV other than Windoze Defender
Guest: Windows XP SP3
===================
Failed to open a session for the virtual machine Windoze XP.

The virtual machine 'Windoze XP' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\Carl\VirtualBox VMs\Windoze XP\Logs\VBoxStartup.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}
===================

[ErikDaRed]

I'm still seeing the same lacksWinVerifyTrust issue on 5.0.0r101573.

[LucaCosta]

install older version