virtualbox.org

When I tried to install the latest version, I received the following error.

Any ideas??

Windows 7 home premium. Intel i5 processor, 8gb memory, was running the previous version, and it uninstalled before it tried to install the latest version.

4.3.12 is not the latest version. Please be explicit about your version number when reporting a problem. Luckily the dialog caption has the actual version.

Try using "Run as administrator" to run the installer. Don't change any of the installation options.

mpack wrote:4.3.12 is not the latest version. Please be explicit about your version number when reporting a problem. Luckily the dialog caption has the actual version.

Try using "Run as administrator" to run the installer. Don't change any of the installation options.

Sorry man, I figured the version number in the picture would be enough. I tried the latest version (running as admin) with the same results. I disabled my avast antivirus b4 installing. Win7 x64.
Here is the original version I had installed:
VirtualBox GUI VM Selector Window 4.3.10 r93012 win.amd64 (Mar 26 2014 18:53:57) release log
00:00:00.996057 Log opened 2014-08-23T15:41:54.919022000Z
00:00:00.996057 Build Type: release
00:00:00.996057 OS Product: Windows 7
00:00:00.996057 OS Release: 6.1.7601
00:00:00.996057 OS Service Pack: 1
00:00:01.003057 DMI Product Name: MS-7680
00:00:01.006057 DMI Product Version: 3.0
00:00:01.006057 Host RAM: 7911MB total, 4552MB available
00:00:01.006057 Executable: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
00:00:01.006057 Process ID: 7104
00:00:01.006057 Package type: WINDOWS_64BITS_GENERIC
00:00:01.024058 UIMediumEnumerator: Medium-enumeration started...
00:00:01.234070 UIMediumEnumerator: Medium-enumeration finished!

Any help would be appreciated. I will try to reinstall this version.

The GUI log is not very useful in this context.

This is an MS Installer error, so a better log would be the MSI install log for VirtualBox. This Microsoft support page tells you how to enable MSI logging.

mpack wrote:The GUI log is not very useful in this context.

This is an MS Installer error, so a better log would be the MSI install log for VirtualBox. This Microsoft support page tells you how to enable MSI logging.

Here is the file output from the log.

You seem to have moved the goalposts again. This was an attempt to install 4.3.14? I would return to 4.3.12 if I was you.

Otherwise...

MSI.log wrote: MSI (s) (04:80) [19:11:57:889]: Source type from package 'VirtualBox-4.3.14-r95030-MultiArch_amd64.msi': 2
MSI (s) (04:80) [19:11:57:944]: SECREPAIR: Hash Database: C:\Windows\Installer\SourceHash{8DD94059-60C6-42E3-AB59-8F37445ACC79}
MSI (s) (04:80) [19:11:57:944]: SECREPAIR: SourceHash database file already exists. Deleting it.
MSI (s) (04:80) [19:11:58:094]: Note: 1: 2262 2: SourceHash 3: -2147287038
MSI (s) (04:80) [19:12:01:527]: SECREPAIR: New Hash Database creation complete.
MSI (s) (04:80) [19:12:01:910]: SECREPAIR: A general error running CryptAcquireContext
MSI (s) (04:80) [19:12:01:910]: SECREPAIR: Crypt Provider not initialized. Error:-2146893813
MSI (s) (04:80) [19:12:01:910]: SECUREREPAIR: Failed to CreateContentHash of the file: VirtualBox-4.3.14-r95030-MultiArch_amd64.msi: for computing its hash. Error: -2146893813
MSI (s) (04:80) [19:12:01:910]: SECREPAIR: Failed to create hash for the install source files
MSI (s) (04:80) [19:12:01:910]: Note: 1: 2262 2: SourceHash 3: -2147287038
MSI (s) (04:80) [19:12:01:910]: SECUREREPAIR: SecureRepair Failed. Error code: 8009000bF67834B8
Key not valid for use in specified state.

I'm not convinced this is even a VirtualBox problem. At this point VBox code isn't even running, all that's happening is that the Windows Installer service (MSI) is unpacking a package created by... whatever tool an MSI packager uses. No VBox bug could influence it AFAICS unless it was badly packaged... in which case I also don't see how this could retroactively affect past VBox versions like 4.3.10 or 4.3.12.

I'm thinking this is a bug introduced by Windows Update. Do you have automatic Windows Updates enabled?

VBox users don't seem to be alone in reporting this problem:
https://www.google.com/search?hl=en&as_ ... ate%22+MSI

And perhaps this is interesting too: KB2918614 breaks Windows Installer Service.

A similar thread on this site is here, and also links to a possible solution.

mpack wrote:You seem to have moved the goalposts again. This was an attempt to install 4.3.14? I would return to 4.3.12 if I was you.

I'm not convinced this is even a VirtualBox problem. At this point VBox code isn't even running, all that's happening is that the Windows Installer service (MSI) is unpacking an package created by... whatever tool an MSI packager uses. No VBox bug could influence it AFAICS unless it was badly packaged... in which case I also don't see how this could retroactively affect past VBox versions like 4.3.10 or 4.3.12.

I'm thinking this is a bug introduced by Windows Update. Do you have automatic Windows Updates enabled?

VBox users don't seem to be alone in reporting this problem:
https://www.google.com/search?hl=en&as_ ... ate%22+MSI

And perhaps this is interesting too: KB2918614 breaks Windows Installer Service.

A similar thread on this site is here, and also links to a possible solution.

Thanks for your help. I will check out the other threads. I do have automatic updates on.

Edit: You, my friend, hit the nail on the head. I uninstalled the update and then was able to install VirturalBox with no problems!! I installed the latest .14 version and all is well! Thank You again!@ Now I will go back and turn off the logging if MSI.

4.3.14 has problems of its own over and above this MSI bug, which is why I recommended that you stick to 4.3.12 for now. No doubt the problems will be resolved in a month or two and you can upgrade then.