Windows 4.3.20 specifically for errors due to security

[danielnashnz]

I'm having problems running any VM in Virtualbox versions later than VirtualBox-4.3.16-95972-Win on:

• Win7 Pro 64
  Comodo CIS 8.0.0.4344 (just Firewall with HIPS, but not Antivirus)
  Avira Free Antivirus 14.0.7.468

- always the error in sceenshot/attachment.
I also tried VirtualBox-4.3.21-97569-Win as well, but still no joy.

screenshot.png (32.83 KiB) Viewed 8667 times

VBoxStartup.zip

(3.13 KiB) Downloaded 44 times

[mpack]

We seem to be getting a rash of uninformative "I have the same problem" posts. Please see the first post of this topic for a list of things you must include (and not include) when posting in this topic. Otherwise your post just gets deleted.

[Moebiusgold]

I installed 4.3.20 3 days ago with administrator rights. I hope that I am posting this in the correct place as I don't have any idea what the problem is. I cannot get any VM to start. I have tried many different guest OS but they all fail the same way, with VERR_LDR_MISMATCH_NATIVE error before even getting to build the OS. I have uninstalled, re-installed, and repaired 4.3.20 but the results are always the same. I turned off Driver verification in the BIOS, no difference. I am not running EMET. I do not have the folder in C:\Users\me\AppData\Local from installing w/o admin rights. I am running Win 8.1 64 bit non pro with virtualization enabled in the bios. This is my first time with Virtualbox and I am a complete novice when it comes to anything like this.
Any hint to what I am doing wrong would be greatly appreciated.

Ubuntu 14.10-2015-01-26-08-50-57.log

Here is the log of an Ubuntu guest

(1.84 KiB) Downloaded 39 times

Thanks

[mpack]

@Moebius: you do not have a security related issue. You issue seems to be a standard one of the VirtualBox application incorrectly installed (e.g. installing for the "Admin" account instead of installing for the correct user but using "Run as administrator"). If you need to discuss this further then create a new topic for the discussion, assuming that a Google search for VERR_LDR_MISMATCH_NATIVE doesn't answer all your questions.

[J-drew]

I'm also not sure my problem is security related. But here's the info.

Host OS = Windows 7 64 bit SP1. MS KB3024777 has been run to remove MS KB3004394. Rebooted the machine and re-installed VirtualBox.
Virtual Box Version = 4.3.20 Build 96997
AV etc. = MS Security essentials ONLY to the best of my knowledge. Windows standard firewall.

I've installed VirtualBox under a normal user's login (mine) but with a superuser's (windows admin) credentials (also mine).

When I try to start a VM, any VM, I get an error that looks like this:
---
Error relaunching VirtualBox VM process: 5
Command line: '60eaff78-4bdd-042d-2e76-669728efd737-suplib-3rdchild -- command "test 2" --startvm 159e46b6-5167-47da-8dd6-924d5a5ff0c5 --no-startvm-errormsgbox "--sup-startup-log=C:\Users\jlk\VirtualBox VMs-test 2\logs\VBoxStartup.log"' (rc=-104)
--
Failed to open a session for the virtual machine test 2.

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

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

See log file attached.

[J-drew]

It seems that 4.3.21 (97849) has solved my problem - at least initially.

[rnewman]

Hello,
No go with the latest build.

OS - Win7 Professional 64bit - SP1
Trendmicro Office Scan - 11.0.1454
Virtualbox - 4.3.21-97849

Screen shot and startup log attached.

-Richard

[tkawai]

hello,

Virtualbox 4.3.21 build 97849
error on follows

HOST: Windows7 SP1 64bit
SEP 12.1.5337.5000(12.1.5 RU5)
Virtualbox 4.3.21 build 97849

GUEST: Windows 8.1 Pro 64bit

[Tulsagrammer]

I've got the same problem many others have identified: VirtualBox guests won't start with Symantec Endpoint Protection 12.x installed. Once I uninstalled SEPM, VirtualBox guests were able to start normally. Summary of my environment:

• Windows 7, 64-bit Version 6.1.7601 Service Pack 1 Build 7601
• SEPM Version 12.1.5 (12.1 RU5) build 5337 (12.1.5337.5000)
• VirtualBox 4.3.21 r97849

The attached zip file contains this additional information about my most recent failed attempt to start a guest:

• An msinfo32 ".NFO" file with details about my system configuration.
• A screen capture showing the error messages displayed by VBox.
• VBox startup log.

The tail end of the startup log shows the following errors:

Code: Select all

1ae8.1af8: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume2\Windows\System32\kernel32.dll [lacks WinVerifyTrust]
1bcc.1390: Error (rc=258):
1bcc.1390: Timed out after 60001 ms waiting for child request #1 (CloseEvents).
1bcc.1390: Error 258 in supR3HardNtChildWaitFor! (enmWhat=5)
1bcc.1390: Timed out after 60001 ms waiting for child request #1 (CloseEvents).

[Tulsagrammer]

As a follow-up to my previous post, I've downloaded and installed VirtualBox 4.3.21 r97927. Guests still fail to start.

Also, my testing has also included adding Application Control exclusions as suggested by Symantec's page:
http://www.symantec.com/business/suppor ... TECH225620.
Those exclusions are ineffective.

[Tulsagrammer]

I have two older versions of VBox available, 4.3.10-93012 and 4.3.12-93733. Based on what others have reported here in this thread, it seems possible that either version might work with SEPM 12.1. But would I have any problems using a back version of VBox to run VMs that have been processed by 4.3.20 (and which have the 4.3.20 tools installed)?

[loukingjr]

You should have no problem rolling back to VB 4.3.12.

[Jacob Klein]

Hmm.. Once I had taken snapshots of 4.3.18 or later, I could not use those snapshots on 4.3.12, which is why I had to take the VMs off of my Windows 10 Host, and put them onto some other host that could run 4.3.18 or later.

So... reverting to an older VirtualBox, using a VM that had been saved with a later version, may not necessarily work all the time, from my experience.

[here647]

Test build 4.3.21r97927 Still FAILS:

Failed to create the VirtualBox COM object.

The application will now terminate.



Callee RC: E_INVALIDARG (0x80070057)


Failed to open a session for the virtual machine slk.

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

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

[rnewman]

Hello,
No go with the latest build.

OS - Win7 Professional 64bit - SP1
Trendmicro Office Scan - 11.0.1454
Virtualbox - 4.3.21-97927

Screen shot and startup log attached.

-Richard