VB crashes on Win7x64 after update.

[dele]

Host system is Win7x64; guests are many. VB 4.2.12 and 4.2.16 work fine. VB 4.2.14, 4.2.18, 4.3.0, 4.3.2, 4.3.4, and 4.3.6 crash. The crash happens at the end of installation process. After such an incomplete(?) installation, when just start and close Oracle VM VirtualBox manager, it crashes also. Currently I use VB 4.2.16 as the latest stable version. Hope to see the problem fixed in new versions. Some screenshots are attached. Thank you.

[socratis]

Please read the following: Minimum information needed for assistance.

[dele]

Ok. Some additional info.
There are 8 guest systems: Win7x64, WinServer2008R2x64, Win8x64, Win8.1x64, WinServer2012, Ubuntu12.04LTSx64, LinuxMint12x64, Win7x64. Guest additions are installed on all 8 guest systems.
I have not even tried to start any of the guest systems with an unstable version of VB: I do not want to break the system.
I just tried to install all versions of VB after 4.2.16, found that installer crashes at the end. Also I found that Oracle VM VirtualBox manager crashes when it is closed (without starting a guest system). After that I just re-install 4.2.16 and work with that version without any problems.
What else can I say, when I do not even start any guest?

[socratis]

OK, I see, the problem is that you can't even install VirtualBox! The guests have nothing to do with it...

The only thing I can say is to look for similar installation errors on the internet. Maybe your installer is corrupted? I've seen some Microsoft patches to fix the installation database. I wish I could help more...

[mpack]

I'm afraid I don't read Russian, and translators don't work on images.

[dele]

Formally, installers say that "installation is complete". They just can not close themself properly. They crash at the moment, when they should just normally close.
All installers were downloaded from the official site, and they have valid digital signatures of Oracle Corporation.
The small picture above says something like: "VirtualBox - critical error. It was impossible to create COM-object VirtualBox. Code of method error: ..."
The big pictures contain the same window, which says something like: "The program VirtualBox Interface was closed. Signature of the problem: Name of event of the problem: BEX64, Name of application: VBoxSVC.exe, Version of application: 4.3.6.0, Mark of time of application: 52b1cb27, Name of the module with error: LvHook64.dll_unloaded, Version of the module with error: 0.0.0.0, Mark of time of the module with error: 4ddd840a, Exception offset: 0000000180083b14, Code of exception: c0000005, Exception data: 0000000000000008, Version of OS: 6.1.7601.2.1.0.256.1, Language code: 1049, Additional info 1: 866d, Additional info 2: ..., Additional info 3: 5007, ..."

[mpack]

If those are equivalent of the English-language error messages I'm familiar with, then they usually mean that the software was installed for the wrong user or without sufficient admin rights. Many users confuse "admin rights" with the "Admin" user name, and hence install for the "Admin" user instead of themselves. It needs to be installed as the correct user, using "Run as administrator" may be wise, and 64bit Windows hosts should not be configured to silently reject non-Microsoft device drivers: make it at least prompt for permission.

[dele]

Yes, it seems, you are right. I tried to start the installer of 4.3.6 with admin rights, and it did not crash. The same is for Oracle VM VirtualBox Manager.
The guest systems do not start properly, because the proper version of Extension Pack is not installed. I do not want to install it now. I will roll back to 4.2.16.
If you think, that some application must be run with admin rights, you should program it to ask admin rights, not just crash.
Thank you.