virtualbox.org

One of the earlier .17 (I think) builds solved the startup issues I was experiencing, however I still see errors when shutting down VMs.

I have a Debian Sid VM (with systemd and gnome). Shutting this down (from within the guest OS) just now, I've received a virtualbox.exe application error stating "The instruction at 0x6ce6b51c referenced memory at 0x11eed410. The memory could not be read.".

Similarly, with a tails, during shutdown, in the middle of it wiping memory, I get the same error, though different memory locations obviously.

Could you please look into this.

I'm getting an error during install of Win7 guest in Win7 host. The error is:


Host: Win7 sp1 32bit
Antivirus: Bitdefender
Firewall: ZoneAlarm

I'm getting following error on trying startup a VM:
System:
OS: Windows 7 Home Premium x64
Memory: 6GB DDR3 RAM
Processor: AMD Sempron 140 Processor 2.70GH
GPU: NVIDIA GeForce G210
Mainboard: ASRock N68C-S UCC
AV: avast! Free Antivirus & Malewarebytes Anti-Maleware (error also appear when both are disabled)

4.3.18 finally works for me! I couldn't get Virtualbox 4.3.14 and all test builds up to now to run.

Host: Windows XP
HIPS/Firewall: Comodo version 5

Thanks!

A quick question to bird and co.

Am I right in thinking you'll soon be issuing 4.3.19 test builds as you did for the final 4.3.16 and 4.3.18 builds, to get our feedback?

If so, is this the thread we should be checking, for their arrival (as was the case for the .15 and .17 builds)?

Mike

Concerning the error with Symantec Endpoint Protection 12.1.5337.5000 I can confirm the same error with both 4.3.16 r95972 and 4.3.18. r96516. I noted the logs show the first error at sysplant.sys. Google suggests this is used by SEP for Application and Device Control and isnt needed if these are not used. Turning off Application and Device Control makes no difference. Renaming sysplant.sys and then restarting the computer fixes the problem in that virtualbox will now run correctly. It does leave SEP complaining that it needs a restart!

I can also confirm that 96342 doesnt have this problem, so I will stick to this for the time being...

<whole bunch of chatter deleted>

People, this is not the "Windows 10 discussion" topic. See the first post of this discussion for what is required here.

Hi,

I still can't start any VM with 4.3.18 on Windows 7 64-bit, with Avast installed.



Thanks.

MikeDiack wrote:A quick question to bird and co.

Am I right in thinking you'll soon be issuing 4.3.19 test builds as you did for the final 4.3.16 and 4.3.18 builds, to get our feedback?

If so, is this the thread we should be checking, for their arrival (as was the case for the .15 and .17 builds)?

Mike

Many, but not all appear here: https://www.virtualbox.org/wiki/Testbuilds

Same.

Error:
Failed to open a session for the virtual machine WinTest.

The virtual machine 'WinTest' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'C:\Users\M\VirtualBox VMs\WinTest\Logs\VBoxStartup.log'.

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

Symantec Endpoint Protection 12.1.5(12.1 RU5 121.1.5337.5000)

VM startup error

BrianG61UK wrote:Many, but not all appear here: https://www.virtualbox.org/wiki/Testbuilds

The windows test build link is broken.

The link currently is for r96342 (VirtualBox-4.3.17-96342-Win.exe), a 4.3.17 test build which has been deprecated, since 4.3.18 has been released.
I think we're still waiting for our first 4.3.19 Windows test build.

This error windows 7 x64!

Tried upgrading from 4.3.17-r96235 to 4.3.18-96516. I got startup errors ("...see VBoxStartup.log") when I tried to launch my VMs (Ubuntu if it matters) and the VM wouldn't start.

System: Win 7, 32 bit, 4 GB RAM
McAfee Enterprise

Immediately fell back to the previous version and my VMs started working again.