4.3.14 conflicts with anti-virus packages.

[jefke]

I'm just hoping that we could get some information on how the problem is solved, when it will probably eventually be solved.
For me personally, it would influence my decision on whether or not to further use virtualbox as my virtual machine solution of choice or not.

I refer also to my previous post: will it be whitelisting of known AV packages, will it be (as it seems the case, if I'm not misinterpreting it) removing AV injections, basically blocking AV solutions' monitoring of VB processes, ...

Thanks in advance for any light you could shed on this!

[Jorabo]

Same problems with Windows8.1 and F-Secure Antivirus.....

[cwahlgren]

Hi,

Latest test build VirtualBox-4.3.15-95226-Win.exe now works for me. Previous 4.3.15 build didn't work, as I've reported earlier.
I have Windows 7 Enterprise, Symantec Endpoint Protection.

[sunboy]

VirtualBox-4.3.15-95226-Win.exe works here (VMs can be started) with
Trendmicro Office Scan and Zemana Antilogger free
W7pro 64 bit


But i have the impression starting lasts some seconds longer?

[MikeDiack]

Some good news:

I can also confirm the newest build VirtualBox-4.3.15-95226-Win.exe works for me on Windows 7 SP1 x64 with Symantec Endpoint 12.1.4001.4126.

Well done guys!

Two smaller comments:

1) The "new" test build on page 1 of this thread still points to the earlier 4.3.15 build, not the second test build.
2) I'd agree with someone else - the VMs now take longer to start - is this due to debugging/logging code, or part of the fix/workaround for the injection issues?

Will report on use with Comodo Internet Security 7.0 on Win 7 SP1 x86 shortly....

Mike

[mpack]

I'd like to remind you that all versions (updates) released together with 4.3.14 (such as 4.2.26) are also affected by this "supR3HardenedWinReSpawn" (et al) problem.

Good point, thank you. I actually hadn't realized that this feature had been added to "stable" branches - I don't use those versions and I see nothing mentioned in the changelog.

[LotharL]

Sadly still not working here, only new error message:

Für die virtuelle Maschine Debian Test konnte keine neue Sitzung eröffnet werden.
The virtual machine 'Debian Test' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005).
More details may be available in 'C:\Users\Admin\VirtualBox VMs\Debian Test\Logs\VBoxStartup.log'.
Fehlercode:E_FAIL (0x80004005)
Komponente:Machine
Interface:IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

VBoxStartup.log

2148.21f8: Log file opened: 4.3.15r95226 g_hStartupLog=0000000000000054 g_uNtVerCombined=0x611db110
2148.21f8: Calling main()
2148.21f8: SUPR3HardenedMain: pszProgName=VirtualBox fFlags=0x0
2148.21f8: SUPR3HardenedMain: Respawn #1
2148.21f8: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume2\Program Files\Oracle\VirtualBox\VirtualBox.exe)
2148.21f8: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume2\Program Files\Oracle\VirtualBox\VirtualBox.dll)
2148.21f8: supR3HardenedWinDoReSpawn(1): New child 21fc.2298 [kernel32].
2148.21f8: supR3HardenedWinPurifyChild: PebBaseAddress=000007fffffde000 cbPeb=0x380
2148.21f8: supR3HardNtPuChFindNtdll: uNtDllParentAddr=0000000077830000 uNtDllChildAddr=0000000077830000
2148.21f8: supR3HardNtPuChTriggerInitialImageEvents: pvLdrInitThunk=000000007785c340 pvNtTerminateThread=00000000778817e0
2148.21f8: supR3HardNtPuChSanitizeMemory: Freeing exec mem at 0000000000060000 (0000000000060000 LB 0x2000)
2148.21f8: supR3HardNtPuChSanitizeImage: 0000000077830000 '\Device\HarddiskVolume2\Windows\System32\ntdll.dll'
2148.21f8: supR3HardNtPuChSanitizeMemory: Freeing exec mem at 00000000779e0000 (00000000779e0000 LB 0x3000)
2148.21f8: supR3HardNtPuChSanitizeImage: 000000013f500000 '\Device\HarddiskVolume2\Program Files\Oracle\VirtualBox\VirtualBox.exe'
2148.21f8: supR3HardNtPuChSanitizeImage: 000007feffb50000 '\Device\HarddiskVolume2\Windows\System32\apisetschema.dll'
2148.21f8: supR3HardenedWinDoReSpawn(1): Quitting: ExitCode=0xc0000005 rcNt=0x0

My System:
Win 7 Sp1/64, VirtualBox-4.3.15-95226-Win, Avast 2014.9.0.2021, Comodo 7.0.317799.4142

[Anunes]

VB 4.3.15_95226 Critical Error /Acess Denied
Avast Blocked VB at startup asking for a Exception.
I do not understand all around this. No other Software I have installed is causing such problems. No other App is interfering with AV.

[pillainp]

Well, it certainly looks like I am done with VirtualBox, for the near future at least.

Fedora 19 VirtualBox 4.3.15.95226

Fedora19_431595226.jpg (42.98 KiB) Viewed 5592 times

[Ady]

I'd like to remind you that all versions (updates) released together with 4.3.14 (such as 4.2.26) are also affected by this "supR3HardenedWinReSpawn" (et al) problem.

Good point, thank you. I actually hadn't realized that this feature had been added to "stable" branches - I don't use those versions and I see nothing mentioned in the changelog.

(italics format is mine)

Indeed, it's not in the changelog. FWIW...

In this same forum topic, a post from "michaln" ( https://forums.virtualbox.org/viewtopic.php?f=6&t=62615&start=195#p293938 ) links to:
"Oracle Critical Patch Update Advisory - July 2014"
http://www.oracle.com/technetwork/topics/security/cpujul2014-1972956.html

Affected Products and Components

...

Oracle VM VirtualBox, versions prior to 3.2.24, 4.0.26, 4.1.34, 4.2.26, 4.3.14

I am using 4.2.x so I confirm that 4.2.26 indeed suffers from the same "supR3HardenedWinReSpawn" (et al) problem.

[rbaraldi]

Unfortunally I deleted the imported image , them VB new version, installed the old version of VB and reimported and still got an error in Windows 8.1 host

[The Seeker]

VirtualBox-4.3.15 works for me. I can start all my VM´s

VB-Version: VirtualBox-4.3.15-95226-Win.exe
Security Tools: MS EMET 4.1.5064.16886 & Symantec Endpoint Protection 12.1.4013.4013
OS: Windows 7 Enterprise SP1 x64

[kutkloon7]

The test build (VirtualBox-4.3.15-95226-Win.exe) works here as well. When I tried it immediately after the installation I got some of the same errors, but now it seems to work fine, with the exception of: hardware acceleration does not seem to work in the linux mint guest, and I can't mount any shared folders, "No such file or directory" (the path of the shared folder does show up in the log though, 'C:\Users\Ruben\Desktop\OS\kernel'). I know, it's a test-build, but I figured any moderators might want to know.

using windows 64-bit 8.1, avast! free antivirus version 2014.9.0.2021
I installed guest additions

[pillainp]

No hope here at all.

Nothing works --- Linux, Windows 8.1, Windows 7 --- all VM's can be created but refuse to start with the same 0x80004005 error despite multiple clean installs of VirtualBox.

[Anunes]

The test build (VirtualBox-4.3.15-95226-Win.exe) works here as well. When I tried it immediately after the installation I got some of the same errors, but now it seems to work fine, with the exception of: hardware acceleration does not seem to work in the linux mint guest, and I can't mount any shared folders, "No such file or directory" (the path of the shared folder does show up in the log though, 'C:\Users\Ruben\Desktop\OS\kernel'). I know, it's a test-build, but I figured any moderators might want to know.

using windows 64-bit 8.1, avast! free antivirus version 2014.9.0.2021
I installed guest additions

How can it be? I also have 8.1 - 64bit and same Avast version, but Avast prevents VB from startup.
What is your GPU configuration? I have a Dual system , Intel HD4600 and NVidia 740