3.2.8 on Win7 64-bit will not install - hangs at end of install w/o finishing

[Peter G. Chase]

Host is Windows 7 64-bit. 3.2.8-64453-Win will not install - hangs at end of install w/o finishing. Tried to upgrade from 3.2.6 r63112 twice. Goes through install routine but does not finish. Had to force quit w/ task manager and reboot to get network back. 3.2.6 continues to work OK.

[misha]

Please attach ​msi & setupapi logs for your installation here.
Also did you try to first uninstall the 3.2.6 and then install 3.2.8? does this work?

[Peter G. Chase]

attached

setupapi.app.log

and

VirtualBox-3.2.8-r64453-MultiArch_amd64.msi

[Peter G. Chase]

Your system is reporting an internal server error when I try to upload the file

VirtualBox-3.2.8-r64453-MultiArch_amd64.msi

"500 Internal Server Error (Maximum attachment size: 400000 bytes)" The upload file size is 23,628 KB.

NOTE: I am running Windows 7 64-bit on Intel NOT AMD as the MSI filename suggests. This could be a problem right there.

[Radha Krishna. S.]

Same issue noticed on my Windows XP SP2.

The installer begins - the machine loses its network connection (I guess its installing some VBox network filter drivers), goes into sort of hang state. The installer is responsive - the installer window can be moved around.

I have to kill the installer and reboot the box to get back my network. I believe something totally amiss here.

[misha]

Replying to pchase: why would you want to attach msi here? please attach the *log* file, whose name is in the format like msi<hex_number>.log. Please also attach setupapi.dev.log.

[misha]

Replying to sradhakrishna: please attach ​msi & setup api logs as well, and we'll have a look at what could be done here.

To all: please specify which other third-party networking-related software do you have installed (like antivirus, firewall, VPN, other virtualizers, etc. )

[Peter G. Chase]

Replying to pchase: why would you want to attach msi here? <<

Because you asked for it in your original reply, ("Please attach msi & setupapi logs for your installation here.") but the file is too big for your system to accept. I used the "Attachments" section to attempt the upload. setupapi.dev.log (which did not initially appear after the earlier registry changes) is being uploaded.

Antivirus is Microsoft Security Essentials. Firewall is Windows 7 -provided. No VPN or other stuff. Apple Airport Extreme router, if that matters.

[ddn]

pchase: misha is asking you to provide MSI logs.

example: msiexec.exe /i <msipackage.msi> /l* file.log

[Peter G. Chase]

Adding MSI logs. There were two because on the first attempt, the installer said it was interrupted, although I did not do anything to interrupt it. Per your instructions on ​http://www.virtualbox.org/wiki/MSI_Logging, I am going to C:\Users\pchase\AppData\Local\Temp. Sorting by creation date, the most recent files produced right after another installation attempt are MSI45fa1.LOG and MSI95d56.LOG (see note above). Also including setupapi.app.log and setupapi.dev.log

[Peter G. Chase]

Your system will not allow me to attach the second log file (MSI95d56.LOG); it is 931 KB in size. Your system says it is too big (over 400000 bytes). This log file was created during a second installation attempt of VirtualBox-3.2.8-64453-Win.exe. While it did not report being interrupted it did hang after a couple of minutes as in every other attempt. I let it sit for several minutes before killing it with Task Manager and rebooting to get the network back.

[Peter G. Chase]

Split MSI95d56.LOG into three parts clearly labeled.

[Frank Mehnert]

Please reopen if still relevant with VBox 4.1.22.