4.3.14 conflicts with anti-virus packages.

[goliate82]

I also have same problem wih window 7 home edition .
I installed virtualBox 4.3.14 r95030 ..
I cannot start vm with "Error relaunching VirtualBox VM process: 5 Command line: '81954AF5-31EB-A142-B7AF187A1C41-
suplib-2ndchild --comment Ubuntu --startvm 755039eb-88e1-40b7-b227-050b64ec6e6b -- no-startvm-errormsgbox' (rc=-104)"

[mpack]

Thanks, but I think we now have all the posts about 4.3.14 which we need. Before posting again, please try the 4.3.15 test build mentioned in the first post of this discussion.

[LesD]

Just downloaded 4.3.15 from the link provided in the 1st post and it solved my problem.

Thank you

PS: After the install of 4.3.15 the association between .ova files and virtualbox was lost so double clicking on an ova file did not automatically run the import.

[raananb]

Downloaded and installed 4.3.15 - same problem as 4.3.14

Started a 4.3.15 topic

[mpack]

Started a 4.3.15 topic

... which I just deleted.

4.3.15 only exists because of this thread, and is still only experimental (hence the odd number), so lets just keep the focus here thanks. Time enough for a new discussion topic when there's a new official release version.

[fditolla]

With the latest patch (VirtualBox-4.3.15-95286-Win.exe) here all the VMs run fine again.
host: Windows 7.64 + avast and nvidia driver
VMs: Debian, Ubuntu. CentOS, SuSE, Kali.

[Iceman_B]

I ran into the following as well:

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

I tried the test release and no problems.
Currently running 4.3.15 r95286

[somnang]

I downloaded VirtualBox-4.3.15-95286-Win.exe today. After installation, VM gave this error:

Failed to open a session for the virtual machine Win7.

The virtual machine 'Win7' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'D:\temp\VirtualBox\Win7\Logs\VBoxStartup.log'.

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

And here's the log:

Code: Select all   Expand viewCollapse view

d68.fac: Log file opened: 4.3.15r95286 g_hStartupLog=000000000000001c g_uNtVerCombined=0x611db110
d68.fac: Calling main()
d68.fac: SUPR3HardenedMain: pszProgName=VirtualBox fFlags=0x0
d68.fac: SUPR3HardenedMain: Respawn #1
d68.fac: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Program Files\Oracle\VirtualBox\VirtualBox.exe)
d68.fac: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Program Files\Oracle\VirtualBox\VirtualBox.dll)
d68.fac: supR3HardenedWinDoReSpawn(1): New child a98.e24 [kernel32].
d68.fac: supR3HardenedWinPurifyChild: PebBaseAddress=000007fffffd6000 cbPeb=0x380
d68.fac: supR3HardNtPuChFindNtdll: uNtDllParentAddr=0000000077720000 uNtDllChildAddr=0000000077720000
d68.fac: supR3HardNtPuChTriggerInitialImageEvents: pvLdrInitThunk=000000007774c340 pvNtTerminateThread=00000000777717e0
d68.fac: supHardNtVpScanVirtualMemory: enmKind=CHILD_PURIFICATION
d68.fac:  *0000000000000000-fffffffffffeffff 0x0001/0x0000 0x0000000
d68.fac:  *0000000000010000-fffffffffffeffff 0x0004/0x0004 0x0020000
d68.fac:  *0000000000030000-000000000002efff 0x0040/0x0040 0x0020000 !!
d68.fac: supHardNtVpScanVirtualMemory: Freeing exec mem at 0000000000030000 (0000000000030000 LB 0x1000)
d68.fac:   0000000000031000-0000000000021fff 0x0001/0x0000 0x0000000
d68.fac:  *0000000000040000-000000000003bfff 0x0002/0x0002 0x0040000
d68.fac:   0000000000044000-0000000000037fff 0x0001/0x0000 0x0000000
d68.fac:  *0000000000050000-000000000004efff 0x0004/0x0004 0x0020000
d68.fac:   0000000000051000-0000000000031fff 0x0001/0x0000 0x0000000
d68.fac:  *0000000000070000-fffffffffff73fff 0x0000/0x0004 0x0020000
d68.fac:   000000000016c000-0000000000168fff 0x0104/0x0004 0x0020000
d68.fac:   000000000016f000-000000000016dfff 0x0004/0x0004 0x0020000
d68.fac:   0000000000170000-ffffffff88bbffff 0x0001/0x0000 0x0000000
d68.fac:  *0000000077720000-000000007771efff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
d68.fac:   0000000077721000-000000007761efff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
d68.fac:   0000000077823000-00000000777f3fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
d68.fac:   0000000077852000-0000000077849fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
d68.fac:   000000007785a000-0000000077858fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
d68.fac:   000000007785b000-0000000077857fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
d68.fac:   000000007785e000-00000000777f2fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
d68.fac:   00000000778c9000-00000000778a1fff 0x0001/0x0000 0x0000000
d68.fac:  *00000000778f0000-00000000778eefff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\sysferThunk.dll
d68.fac: Error (rc=-5633):
d68.fac: Unknown image file \Device\HarddiskVolume1\Windows\System32\sysferThunk.dll at 00000000778f0000.
d68.fac:   00000000778f1000-00000000778effff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\sysferThunk.dll
d68.fac: Error (rc=-5633):
d68.fac: Unknown image file \Device\HarddiskVolume1\Windows\System32\sysferThunk.dll at 00000000778f1000.
d68.fac:   00000000778f2000-00000000778effff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\sysferThunk.dll
d68.fac: Error (rc=-5633):
d68.fac: Unknown image file \Device\HarddiskVolume1\Windows\System32\sysferThunk.dll at 00000000778f2000.
d68.fac:   00000000778f4000-00000000778f2fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\sysferThunk.dll
d68.fac: Error (rc=-5633):
d68.fac: Unknown image file \Device\HarddiskVolume1\Windows\System32\sysferThunk.dll at 00000000778f4000.
d68.fac:   00000000778f5000-00000000778f1fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\sysferThunk.dll
d68.fac: Error (rc=-5633):
d68.fac: Unknown image file \Device\HarddiskVolume1\Windows\System32\sysferThunk.dll at 00000000778f5000.
d68.fac:   00000000778f8000-000000007020ffff 0x0001/0x0000 0x0000000
d68.fac:  *000000007efe0000-000000007dfdffff 0x0000/0x0002 0x0020000
d68.fac:  *000000007ffe0000-000000007ffdefff 0x0002/0x0002 0x0020000
d68.fac:   000000007ffe1000-000000007ffd1fff 0x0000/0x0002 0x0020000
d68.fac:   000000007fff0000-ffffffffc034ffff 0x0001/0x0000 0x0000000
d68.fac:  *000000013fc90000-000000013fc8efff 0x0040/0x0080 0x1000000  \Device\HarddiskVolume1\Program Files\Oracle\VirtualBox\VirtualBox.exe
d68.fac:   000000013fc91000-000000013fc20fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume1\Program Files\Oracle\VirtualBox\VirtualBox.exe
d68.fac:   000000013fd01000-000000013fcd7fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Program Files\Oracle\VirtualBox\VirtualBox.exe
d68.fac:   000000013fd2a000-000000013fd21fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume1\Program Files\Oracle\VirtualBox\VirtualBox.exe
d68.fac:   000000013fd32000-000000013fcfafff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Program Files\Oracle\VirtualBox\VirtualBox.exe
d68.fac:   000000013fd69000-000000013fd61fff 0x0001/0x0000 0x0000000
d68.fac:  *000000013fd70000-000000013fd6efff 0x0040/0x0040 0x0020000 !!
d68.fac: supHardNtVpScanVirtualMemory: Freeing exec mem at 000000013fd70000 (000000013fd70000 LB 0x1000)
d68.fac:   000000013fd71000-fffff803800a1fff 0x0001/0x0000 0x0000000
d68.fac:  *000007feffa40000-000007feffa3efff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\apisetschema.dll
d68.fac:   000007feffa41000-000007fdff4d1fff 0x0001/0x0000 0x0000000
d68.fac:  *000007fffffb0000-000007fffff8cfff 0x0002/0x0002 0x0040000
d68.fac:   000007fffffd3000-000007fffffcffff 0x0001/0x0000 0x0000000
d68.fac:  *000007fffffd6000-000007fffffd4fff 0x0004/0x0004 0x0020000
d68.fac:   000007fffffd7000-000007fffffcffff 0x0001/0x0000 0x0000000
d68.fac:  *000007fffffde000-000007fffffdbfff 0x0004/0x0004 0x0020000
d68.fac:  *000007fffffe0000-000007fffffcffff 0x0001/0x0002 0x0020000
d68.fac: Fatal error:
d68.fac: Unknown image file \Device\HarddiskVolume1\Windows\System32\sysferThunk.dll at 00000000778f0000.
[rc=-5633] Unknown image file \Device\HarddiskVolume1\Windows\System32\sysferThunk.dll at 00000000778f1000.
[rc=-5633] Unknown image file \Device\HarddiskVolume1\Windows\System32\sysferThunk.dll at 00000000778f2000.
[rc=-5633] Unknown image file \Device\HarddiskVolume1\Windows\System32\sysferThunk.dll at 00000000778f4000.
[rc=-5633] Unknown image file \Device\HarddiskVolume1\Windows\System32\sysferThunk.dll at 00000000778f5000.


Image:

VB.PNG (85.96 KiB) Viewed 6221 times

I thought it would be a bit too personal to include applications installed on my machine. But I'll give a few names.
NVIDIA drivers
Symantec Endpoint Protection v12.1.671.4971
Adobe Flash
Adobe Reader
Microsoft .NET Framework 4.5.1
Microsoft Keyboard and Mouse
Microsoft Silverlight
Microsoft Visual C++
Virtual CloneDrive
Waterfox
WinRAR

Going to downgrade to 4.3.12, again.

[Vauquelin]

I am in the same situation as Herdz above
Using AVG antivirus and cannot start VM box 4.3.14
Using an HP 2000 notebook family premium with Windows 7
No such registry entry as discussed above

[eyeskillerLB]

Same problem here.

Eset Smart Security - Kali Linux - VB 4.3.14 r95030

But I can't post images, 'cause I am not member for 1 day and I haven't posted 1 post, so If u want image, write mi message.

[LesD]

So why don't you try 4.3.15?

[raananb]

@LesD,

VirtualBox-4.3.15-95286-Win.exe fails too on Windows 8.1 & Avast, Intel i7

[gak]

Same issue on Windows 8.1 with Avast.
Yesterda removed Avast and enabled Windows Defender, then tried install again which worked.
Again same issue today.

Will test this test build (download is quite slow)

[Nifft]

I have the same problem. I've tried VirtualBox-4.3.15-95286-Win.exe to no avail, none of our VMs are working. Getting the same errors as others in the thread.

Any update on a fix for this?

[trizz]

Interesting post in the beta forum. I don't use resident antivirus so I've not tested it :-

Ok, i've researched the problem and found the solution.

It is caused by the following entry in the registry:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers]
"C:\\Program Files\\Oracle\\VirtualBox\\VirtualBox.exe"="DISABLEUSERCALLBACKEXCEPTION"

Delete this entry, and everything works as expected.

The DISABLEUSERCALLBACKEXCEPTION registry key has nothing to do with AV software, it's part of a Windows feature. It is currently unknown why some systems have the key set and others don't.

That key is set if Windows asked the user "If this program is installed correctly" (can't post images yet; just google at "this program is installed correctly" to view an image)
Deleting this key solves the "Failed to verify process integrity" problem.