Discuss the 4.3.14 release

[socratis]

P.S.: Shall I make an entry to the bug tracker, too?

I would hold on to that until we have one or two more testers chiming in. The developers have a lot on their plate with the 4.3.14 release already. I will try it tomorrow with my Greek keyboard layout and post back (too late in the evening to try it now).

[DrTeeth]

I have had MAJOR problems with VirtualBox after installing 4.3.14 over 4.3.12 on a Win 7 x64 machine and a Win 8.1 x64 machine.

Neither will load and the error messages mention that various DLLs (that are all 64 bit). The DLL errors are different for each machine.

Same error box as NilexBM on both machines.

No probs with 4.3.12.

[socratis]

@DrTeeth
Your problem sounds really unique! I haven't heard of anyone having issues with 4.3.14 on Windows!


(hint: 4.3.14 conflicts with anti-virus packages)

SEARCH PEOPLE!

[DrTeeth]

@DrTeeth
Your problem sounds really unique! I haven't heard of anyone having issues with 4.3.14 on Windows!

SEARCH PEOPLE!

Excuse me, but this seems to be a different issue to the anti-virus one, which I have read completely. Mods are even locking threads started by people who have this particular problem with NO antivirus software installed at all! They clearly state they have no AV software installed and a mod locks the thread and posts a link to the AV conflict thread <face-palm>.

I do not get any 'supR3HardenedWinVerifyProcess' errors.

[socratis]

No, it's exactly the same issue, unfortunately. It's a DLL injection issue. From a moderator that has (wisely) locked some threads:

the actual problem is with any program that injects DLLs into the VirtualBox address space. VirtualBox thinks this is spyware.

Emphasis mine.

[JayEm]

The issue I have is that when typing in guest VMs, I am no longer able to enter characters which on a german keyboard are composed with AltGR, e.g. "@", or "|". It does not matter whether I upgrade the guest additions to 4.3.14, or leave them at 4.3.12. This is especially a problem when passwords contain such characters; I had to ssh in and change PW to something different. I'm afraid that when there is no quick workaround I have to downgrade to 4.3.12.

No problems here, working as expected.

[socratis]

The issue I have is that when typing in guest VMs, I am no longer able to enter characters which on a german keyboard are composed with AltGR, e.g. "@", or "|". It does not matter whether I upgrade the guest additions to 4.3.14, or leave them at 4.3.12. This is especially a problem when passwords contain such characters; I had to ssh in and change PW to something different. I'm afraid that when there is no quick workaround I have to downgrade to 4.3.12.

I said to wait and see if other people are seeing the same behavior. And they have seen it. And filed a bug report (https://www.virtualbox.org/ticket/13216).

[TSKRICH]

New install of 4.3.14 just downloaded, Same problem exist with only Microsoft Security Essentials installed and no other AV.

Windows 7 Home 64 bit system installed

[asandu]

Since I upgraded to .14 .. Can't start my machines because of the vboxnet0 not existing and failing to create ..

d3xt3r01 ~ # VBoxManage hostonlyif create
0%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to create the host-only adapter
VBoxManage: error: Failed to execute 'VBoxNetAdpCtl add' (exit status: -10). Check permissions!
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterface, interface IHostNetworkInterface
VBoxManage: error: Context: "int handleCreate(HandlerArg*, int, int*)" at line 66 of file VBoxManageHostonly.cpp
Jul 20 13:58:28 d3xt3r01 kernel: [227364.585551] PGD 134d35067 PUD 0
Jul 20 13:58:28 d3xt3r01 kernel: [227364.586404] Oops: 0002 [#24] SMP
Jul 20 13:58:28 d3xt3r01 kernel: [227364.587257] Modules linked in: vboxnetflt(O) vboxnetadp(O) vboxdrv(O) xt_comment btusb fuse bnep bluetooth iwlmvm iwlwifi xt_multiport xt_set ipt_MASQUERADE iptable_n
at nf_nat_ipv4 xt_REDIRECT xt_nat ip6table_nat nf_nat_ipv6 nf_nat ip_set_hash_ip ip_set_hash_net ip_set aufs ext2 snd_usb_audio snd_usbmidi_lib snd_rawmidi iTCO_wdt iTCO_vendor_support snd_hda_codec_real
tek x86_pkg_temp_thermal coretemp snd_hda_codec_hdmi lpc_ich e1000e(O) mfd_core nuvoton_cir rc_core snd_hda_intel snd_hda_codec snd_hwdep [last unloaded: vboxdrv]
Jul 20 13:58:28 d3xt3r01 kernel: [227364.590848] CPU: 0 PID: 1446 Comm: VBoxNetAdpCtl Tainted: G D O 3.13.6-aufs #8
Jul 20 13:58:28 d3xt3r01 kernel: [227364.591763] Hardware name: /D54250WYK, BIOS WYLPT10H.86A.0026.2014.0514.1714 05/14/2014
Jul 20 13:58:28 d3xt3r01 kernel: [227364.592688] task: ffff88040cc89f40 ti: ffff880376d86000 task.ti: ffff880376d86000
Jul 20 13:58:28 d3xt3r01 kernel: [227364.593612] RIP: 0010:[<ffffffffa047a387>] [<ffffffffa047a387>] vboxNetAdpOsCreate+0x67/0x110 [vboxnetadp]
Jul 20 13:58:28 d3xt3r01 kernel: [227364.594550] RSP: 0018:ffff880376d87de8 EFLAGS: 00010202
Jul 20 13:58:28 d3xt3r01 kernel: [227364.595489] RAX: 0000000100000001 RBX: ffff88010a24c000 RCX: 0000000000000000
Jul 20 13:58:28 d3xt3r01 kernel: [227364.596413] RDX: 000000000027000a RSI: ffffffffa047af91 RDI: ffff88010a24c000
Jul 20 13:58:28 d3xt3r01 kernel: [227364.597311] RBP: ffff880376d87e08 R08: ffff88041fa15820 R09: ffff88015d1fdb00
Jul 20 13:58:28 d3xt3r01 kernel: [227364.598183] R10: 0000000000000308 R11: 0000000000000000 R12: ffffffffa047af40
Jul 20 13:58:28 d3xt3r01 kernel: [227364.599031] R13: ffffffffa047af88 R14: ffff880376d87e22 R15: 0000000000000000
Jul 20 13:58:28 d3xt3r01 kernel: [227364.599875] FS: 00007fad5f73e700(0000) GS:ffff88041fa00000(0000) knlGS:0000000000000000
Jul 20 13:58:28 d3xt3r01 kernel: [227364.600716] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 20 13:58:28 d3xt3r01 kernel: [227364.601546] CR2: 0000000100000001 CR3: 0000000108de3000 CR4: 00000000001407f0
Jul 20 13:58:28 d3xt3r01 kernel: [227364.602371] Stack:
Jul 20 13:58:28 d3xt3r01 kernel: [227364.603176] ffff880376d87e60 ffffffffa047af40 ffff880376d87e68 00007fff2ffa5b00
Jul 20 13:58:28 d3xt3r01 kernel: [227364.604003] ffff880376d87e48 ffffffffa047a576 0000000000000001 00000027000a0012
Jul 20 13:58:28 d3xt3r01 kernel: [227364.604828] 00007fff2ffa5b00 00007fff2ffa5b00 0000000000000003 ffff8804092bb108
Jul 20 13:58:28 d3xt3r01 kernel: [227364.605653] Call Trace:
Jul 20 13:58:28 d3xt3r01 kernel: [227364.606468] [<ffffffffa047a576>] vboxNetAdpCreate+0xe6/0x190 [vboxnetadp]
Jul 20 13:58:28 d3xt3r01 kernel: [227364.607293] [<ffffffffa047a25b>] vboxNetAdpLinuxGetStats+0x23b/0x300 [vboxnetadp]
Jul 20 13:58:28 d3xt3r01 kernel: [227364.608117] [<ffffffff8115750e>] do_vfs_ioctl+0x7e/0x500
Jul 20 13:58:28 d3xt3r01 kernel: [227364.608932] [<ffffffff811501a1>] ? final_putname+0x21/0x50
Jul 20 13:58:28 d3xt3r01 kernel: [227364.609739] [<ffffffff81150396>] ? putname+0x26/0x40
Jul 20 13:58:28 d3xt3r01 kernel: [227364.610537] [<ffffffff81157a21>] SyS_ioctl+0x91/0xb0
Jul 20 13:58:28 d3xt3r01 kernel: [227364.611326] [<ffffffff816a7e1b>] tracesys+0xdd/0xe2
Jul 20 13:58:28 d3xt3r01 kernel: [227364.612113] Code: a9 47 a0 bf b8 00 00 00 49 0f 45 f5 e8 d3 0f 0a e1 48 85 c0 48 89 c3 74 4b 48 8b 80 d8 02 00 00 48 85 c0 74 6f 41 8b 16 48 89 df <89> 10 41 0f b7 56
04 66 89 50 04 e8 c9 09 0a e1 85 c0 74 2d 41
Jul 20 13:58:28 d3xt3r01 kernel: [227364.614674] RSP <ffff880376d87de8>
Jul 20 13:58:28 d3xt3r01 kernel: [227364.615510] CR2: 0000000100000001
Jul 20 13:58:28 d3xt3r01 kernel: [227364.616349] ---[ end trace 0fea340450d53ef4 ]---


Filled bug #13213

[rpmurray]

VBoxManage: error: Failed to execute 'VBoxNetAdpCtl add' (exit status: -10). Check permissions!

This looks like a likely place to check.

[m6477]

I'm having a similar, but not identical, problem with 4.3.14.
The host PC is Windows 7 Ultimate 64-bit SP1.
When I run VirtualBox.exe if fails with:

VirtualBox.exe has stopped working
A problem caused the program to stop working correctly. Please close the program.
[Close the program]

It's not updating the log files (or any other file in .VirtualBox directory) at all.
I get the same behaviour whether I run the .exe directly or double-click a .vbox file in Windows Explorer.
Previously I had 4.3.12 installed on this PC and it worked OK.
There is no anti-virus software installed.
I normally run as non-Adminstrator. However if I run as Administrator, VirtualBox starts up OK and lets me create a new VM. (There was no users\Administrator\.VirtualBox directory prior to that, because I don't generally run it as Administrator.)
As non-Administrator user I tried renaming my .VirtualBox directory, in case there was something broken in the configuration, but VirtualBox.exe still failed to start.
This PC does not have the DISABLEUSERCALLBACKEXCEPTION registry entry set.

[michael]

Peter, if you are still having this, it would be interesting if you could give the "keylook" tool attached to ticket #12138<1> a try and post the output that it gives when you press AltGr. Another user said that AltGr works for them before but not after a guest reboot - does this apply to you too? It would be great if you could post updates to that user's bug ticket<2> rather than this forum topic.

<1> https://www.virtualbox.org/ticket/12138
<2> https://www.virtualbox.org/ticket/13216

Hi,

I have a new issue with 4.3.14 that I didn't have with 4.3.12 and which I did not see discussed here yet.

Host is Windows 7 Professional 64bit, german locale and keyboard layout. Guests are various Linux 64bit VMs, e.g. CentOS 6.5, Ubuntu 13.10, CentOS 7, OEL 6.5 each with german locale and keyboard layout. All OS, guests and host are patched up to date.

The issue I have is that when typing in guest VMs, I am no longer able to enter characters which on a german keyboard are composed with AltGR, e.g. "@", or "|". It does not matter whether I upgrade the guest additions to 4.3.14, or leave them at 4.3.12. This is especially a problem when passwords contain such characters; I had to ssh in and change PW to something different. I'm afraid that when there is no quick workaround I have to downgrade to 4.3.12.

Thanks and regards
Peter

P.S.: Shall I make an entry to the bug tracker, too?

[jnpapado]

CentOS/RedHat 6 virtual machines fail to start after upgrading to VB 4.2.14 from 4.2.12 on an OpenSUSE 13.1 host. Had to revert back to 4.2.12 to get them working again. CentOS/RedHat 5 seem to work just fine.
Let me know if you need additional info and what.

[kalikosmil]

hi,

Is there any soltution?
I have windows 8.1 with same problem.
And no antivirus.

I downdrade to release 4.3.12, and everything works fine.


Tanks

[desert_xu]

win7 64bit bug

virtualbox创建com对象失败(被召者 RC: REGDB_E_CLASSNOTREG (0x80040154)) ,but 4.3.12 no this error