Discuss the 4.3.14 release

This is for discussing general topics about how to use VirtualBox.
asandu
Posts: 2
Joined: 20. Jul 2014, 21:29

Re: hostonlyif create failing

Post by asandu »

rpmurray wrote:
asandu wrote:VBoxManage: error: Failed to execute 'VBoxNetAdpCtl add' (exit status: -10). Check permissions!
This looks like a likely place to check.

Ok...permissions to what .. I did it as root .. what special permissions do I need on what files .. I don't get it .. the thing is it worked on 4.3.12 just fine , then upgraded to 4.3.14. Also, too bad the check permissions is not more specific .. Also, I don't get why it needs to cause a kernel oops ..
m6477
Posts: 7
Joined: 21. Jul 2014, 11:29

Re: Discuss the 4.3.14 release

Post by m6477 »

m6477 wrote: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.
Just to clarify:
When I ran as "Administrator", I used the account of that name. When I ran as non-administrator I used a different account that is not a member of the Administrators group.
UAC set is set to the highest setting "Always notify". (I believe this generally makes no difference, because if admin privilege is required a non-Admin always gets prompted for admin username/password, and the literal Administrator account never prompts, even when UAC is set to highest.)
The VirtualBox software was installed when I was logged in as Administrator.

Also, every time I've installed VirtualBox I've installed only the basic application - none of the options: USB support, Networking, Python.
EgonF
Posts: 53
Joined: 3. Oct 2010, 12:24
Primary OS: MS Windows other
VBox Version: OSE other
Guest OSses: MX Linux

Re: Discuss the 4.3.14 release

Post by EgonF »

I am using VirtualBox 4.2.6. What have I to do updating to 4.3.14?

I don't find anything in the documentation.
Egon
stefan.becker
Volunteer
Posts: 7639
Joined: 7. Jun 2007, 21:53

Re: Discuss the 4.3.14 release

Post by stefan.becker »

EgonF wrote:I am using VirtualBox 4.2.6. What have I to do updating to 4.3.14?

I don't find anything in the documentation.
Egon
Are you using Clones or Snapshots?
Emmanuel Paulus
Posts: 1
Joined: 22. Jul 2014, 21:52

Re: Discuss the 4.3.14 release

Post by Emmanuel Paulus »

NilexBM wrote: Unistalled VirtualBox completely, and then did a fresh install. Still the same error.
Restarted Windows when the installation program asked me to do so.
I got the same error after a nvidia64.dll corrupt warning.
The 4.3.14 version is instaled under a program files/Oracle/virtualbox/ directory instead .../oracle VM virtualbox/ in 4.3.12
fiest success
- install the 4.3.12 after 4.3.14
- copy the files of 4.3.14 to .../oracle VM virtualbox/.
- uninstall
- install 4.3.14 (gives now the old directory) and it works.
for testing:
- uninstall everything, including register cleanup with ccleaner.
- install default 4.3.14 (..../Oracle/virtualbox/) and now it works also.

I looks like that installing in .../oracle/virtualbox/ instead of .../oracle VM virtualbox/ as upgrade is the reason of the failure
EgonF
Posts: 53
Joined: 3. Oct 2010, 12:24
Primary OS: MS Windows other
VBox Version: OSE other
Guest OSses: MX Linux

Re: Discuss the 4.3.14 release

Post by EgonF »

stefan.becker wrote:
EgonF wrote:I am using VirtualBox 4.2.6. What have I to do updating to 4.3.14?

I don't find anything in the documentation.
Egon
Are you using Clones or Snapshots?

Snapshots

Egon
pschneider1968
Posts: 2
Joined: 19. Jul 2014, 21:03

Re: Discuss the 4.3.14 release

Post by pschneider1968 »

Hi Michael,
michael wrote: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
thanks for looking into this. I have updated ticket 13216.

Regards
Peter
kaesii
Posts: 2
Joined: 23. Jul 2014, 13:09

Re: Discuss the 4.3.14 release

Post by kaesii »

Hi,

VB running on windows 7 \ 8.1 - created a VM "Windows 7", but not possible to start the machine.

Below the Error Code.

thanks.

Markus
Attachments
Unbenannt.JPG
Unbenannt.JPG (77.9 KiB) Viewed 7830 times
weri
Posts: 4
Joined: 23. Jul 2014, 20:22

Re: Discuss the 4.3.14 release

Post by weri »

Same issue here with the new release 4.3.14
We know when is gonna be fixed?
thanks
SpTigerJD1
Posts: 1
Joined: 26. Jul 2014, 18:40
Primary OS: MS Windows 8
VBox Version: PUEL
Guest OSses: DOS, Various Linux
Location: Ohio

Re: Discuss the 4.3.14 release

Post by SpTigerJD1 »

Steve Richards wrote:After installing to Win 8.1 host, every startup of virtualbox.exe pops up this error dialog.

I do have nVidia graphics adapter in machine.

Code: Select all

---------------------------
VirtualBox.exe - Bad Image
---------------------------
C:\Windows\system32\nvinitx.dll is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support. Error status 0xc0000190. 
---------------------------
OK   
---------------------------
I am having same issue with the certsentry.dll file in the same directory and same error status on Win8.1.
EgonF
Posts: 53
Joined: 3. Oct 2010, 12:24
Primary OS: MS Windows other
VBox Version: OSE other
Guest OSses: MX Linux

Re: Discuss the 4.3.14 release

Post by EgonF »

EgonF wrote:
stefan.becker wrote:
EgonF wrote:I am using VirtualBox 4.2.6. What have I to do updating to 4.3.14?

I don't find anything in the documentation.
Egon
Are you using Clones or Snapshots?

Snapshots

Egon
What is to do upgrading from 4.2.6 to 4.3.14?

Egon
dracula
Posts: 3
Joined: 19. Jun 2012, 21:44

Re: Discuss the 4.3.14 release

Post by dracula »

EgonF wrote:...What is to do upgrading from 4.2.6 to 4.3.14?...
Just install the new version. The installer is clever and updates/adds just the needed files. After that you also should update the extensions if allowed.
socratis
Site Moderator
Posts: 27330
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Discuss the 4.3.14 release

Post by socratis »

EgonF wrote:What is to do upgrading from 4.2.6 to 4.3.14?
Actually if you're on Windows, read this first: 4.3.14 conflicts with anti-virus packages. I would test the 4.3.12 first.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
2uanta
Posts: 1
Joined: 28. Jul 2014, 04:13

Re: Discuss the 4.3.14 release

Post by 2uanta »

I have same problem as Steve Richards but on Windows 8. I also have the Nvdia card.
---------------------------
VirtualBox.exe - Bad Image
---------------------------
C:\Windows\system32\nvinitx.dll is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support. Error status 0xc0000190. 
---------------------------
OK   
---------------------------
socratis
Site Moderator
Posts: 27330
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Discuss the 4.3.14 release

Post by socratis »

@2uanta
Read. The. Rest. Of. The. Thread.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Post Reply