2.1.0 41146 Win_x86 - Install Wizard Ended Prematurely :-O

[rob28192]

Had VirtualBox-2.0.6-39760-Win_x86.msi working great.

Had installed.
Uninstalled
Attempted install of VirtualBox-2.1.0-41146-Win_x86.msi

Aborted when it was nearly done Wizard ended prematurely.

Was able to re-install the older version and re-attempt same problem.

LOG File located at:
http://w17.easy-share.com/1702892089.html

Anyone else have the same issue. XP Pro SP2 2 Ghz Machine 2GB of memory.

Looking at the logs I am still confused..

Rob

[Kent_Geek]

I have the same issue. 2.0.6 working fine, uninstalled it, and 2.1.0 looks like it's installing fine, until just after I approved two "unapproved" driver dialogs. Then the install gets rolled back.

Where did you find your install log? Giving yours a preliminary look, it's pretty difficult to decipher what caused the rollback.

My next step (barring some kind soul here showing me the light) is to use msiexec with some command-line options to hopefully illuminate what is happening.

One more thing: it appears, looking through your log, that line 4678 contains the error that causes the rollback -

VBoxNetCfgWinInstallComponent: Install failed, hr (0x80070490)

Any ideas on how to get that to fly? If I figure it out I'll post here.

[wbvczar]

I saw the same thing as the others. I looked for the latest updated file after the failed install and found the "setupapi.log" in the Windows directory. The last lines I found after the failed install were

[2008/12/17 15:48:10 2052.21]
#-198 Command line processed: C:\WINDOWS\system32\MsiExec.exe -Embedding 858827CF5653F815A814BF5F1727B2C5 M Global\MSI0000
#W334 Failed to verify catalog when scanning file queue. Error 1168: Element not found.
#E360 An unsigned or incorrectly signed file "c:\windows\inf\oem61.inf" for driver "Network Service" will be installed (Policy=Ignore). Error 1168: Element not found.
#-024 Copying file "C:\WINDOWS\system32\DRVSTORE\VBoxNetFlt_4CF0FC75F56E46D425175595DE3172F1220D5DF3\VBoxNetFltNotify.dll" to "C:\WINDOWS\system32\VBoxNetFltNotify.dll".
#E360 An unsigned or incorrectly signed file "C:\WINDOWS\system32\DRVSTORE\VBoxNetFlt_4CF0FC75F56E46D425175595DE3172F1220D5DF3\VBoxNetFltNotify.dll" for driver "Network Service" will be installed (Policy=Ignore). Error 1168: Element not found.
#-336 Copying file "C:\WINDOWS\system32\DRVSTORE\VBoxNetFlt_4CF0FC75F56E46D425175595DE3172F1220D5DF3\VBoxNetFlt.sys" to "C:\WINDOWS\system32\DRIVERS\VBoxNetFlt.sys" via temporary file "C:\WINDOWS\system32\DRIVERS\SET66.tmp".
#E360 An unsigned or incorrectly signed file "C:\WINDOWS\system32\DRVSTORE\VBoxNetFlt_4CF0FC75F56E46D425175595DE3172F1220D5DF3\VBoxNetFlt.sys" for driver "Network Service" will be installed (Policy=Ignore). Error 1168: Element not found.
#W082 Could not locate a non-empty service section [VBoxNetFlt.ndi.Remove.Services] in "C:\windows\inf\oem61.inf". Error 0xe0000102: The required line was not found in the INF.

[rob28192]

I see it says (Policy=Ignore). Strange.

Any ideas on how to fix this?

[rob28192]

I have the same issue. 2.0.6 working fine, uninstalled it, and 2.1.0 looks like it's installing fine, until just after I approved two "unapproved" driver dialogs. Then the install gets rolled back.

Where did you find your install log? Giving yours a preliminary look, it's pretty difficult to decipher what caused the rollback.

My next step (barring some kind soul here showing me the light) is to use msiexec with some command-line options to hopefully illuminate what is happening.

One more thing: it appears, looking through your log, that line 4678 contains the error that causes the rollback -

VBoxNetCfgWinInstallComponent: Install failed, hr (0x80070490)

Any ideas on how to get that to fly? If I figure it out I'll post here.

I enabled the regedit for logging, it created the file in the %temp% user temp area.

What options where you thinking of when you talked about msiexec command line options? What would a provide it to provide additional info that was not in the logs?

My problem occurred at the same location as you said. After the two windows conformations about unsigned drivers. It really seems like everything is going fine till the rollback. (No other warnings or failures)

The uninstall was a clean, no problems, so that is what would lead me to think the install of the new version should work fine. I think maybe I will do a install, reboot, uninstall, reboot, install and see what happens. Maybe there is non-complete uninstall (locked) file that is happening. I checked the program files sun directory and it was clean. (empty) before trying the new version. So that is not the problem there.

Thanks.

Robert

[rob28192]

Code: Select all

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]
"Logging"="voicewarmupx"

That I found to enable the logging.....

[rob28192]

Ok Did

1. Install of older version (AOK)
2. Reboot
3. Uninstall Older Version (AOK)
4. Reboot
5. Install of latest version (Not Ok)
Seemed to die when it says "Registering Product". At least that is what I thought flashed by before the roll back.

Rob

[S2K]

Also installed new version, but it did not install. I received following error:



Rebooting and reinstalling did not solve anything. Earlier version worked without problems. Reinstall with 2.0.6 worked ok.

[MasterYoda34]

I've been having the same issue with all versions of Virtual Box on this machine. Vista Ultimate 64bit.

[Surye]

Same issue here, Vista 64bit:

http://pastebin.com/f5b974bc5 Log.

[misha]

for all seeing the install issues, could you do the following:
1. in the registry set the "REG_DWORD LogLevel" value under "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\" to 4800FFFF hexadecimal value - this will enable the verbous setupapi logging
2. move the %windir%/inf/setupapi.dev.log and %windir%/inf/setupapi.app.log - for Vista or %windir%/setupapi.log - for XP to some backup folder not to mix the installation info with the one of the previous installs
3. run virtualbox installer with verbose logging: in the command line type:
msiexec /i <vbox_installer_name>.msi /l*xv <path_to_the_logfile_to_be_created>
4. once the installation is completed (with the failure) please attach the newly generated setupapi log files (%windir%/inf/setupapi.dev.log and %windir%/inf/setupapi.app.log - for Vista or %windir%/setupapi.log - for XP) and installer log file (the one specified in the <path_to_the_logfile_to_be_created> in step#3) to the bug tracker: http://www.virtualbox.org/ticket/1730

This should help us to figure out the problem.

[mdietze]

Howdy,

i found a solution for unsigned driver installation here:

http://www.tech-recipes.com/rx/1429/vis ... forcement/

So just do the following:

Turn off Digital Driver Signing Check in Vista:

1. Right-click on cmd.exe and select Run as administrator

2. When the command window opens, type or paste the following and press ENTER:

Code: Select all

Bcdedit.exe /set nointegritychecks ON 

3. Reboot and then try installing VirtualBox-2.1.0, build 41146 Win x86.

4. After the Installation just enable the integritycheck:

5. Right-click on cmd.exe and select Run as administrator

6. When the command window opens, type or paste the following and press ENTER:

Code: Select all

Bcdedit.exe /set nointegritychecks OFF

Cheers
Martin

[misha]

still this seems to be a bug in the installation since the installed driver packages are signed and there should be no integrity issues,
So log files would be very useful

[misha]

when posting logs please also specify the OS version you are seeing the failure on

[S2K]

for all seeing the install issues, could you do the following:
1. in the registry set the "REG_DWORD LogLevel" value under "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup" to 4800FFFF hexadecimal value - this will enable the verbous setupapi logging
2. move the %windir%/inf/setupapi.dev.log and %windir%/inf/setupapi.app.log - for Vista or %windir%/setupapi.log - for XP to some backup folder not to mix the installation info with the one of the previous installs
3. run virtualbox installer with verbose logging: in the command line type:
msiexec /i <vbox_installer_name>.msi /l*xv <path_to_the_logfile_to_be_created>
4. once the installation is completed (with the failure) please attach the newly generated setupapi log files (%windir%/inf/setupapi.dev.log and %windir%/inf/setupapi.app.log - for Vista or %windir%/setupapi.log - for XP) and installer log file (the one specified in the <path_to_the_logfile_to_be_created> in step#3) to the bug tracker: http://www.virtualbox.org/ticket/1730

This should help us to figure out the problem.

Hi, I just did what you suggested, but I deinstalled version 2.0.6 first. And now with above actions it installs without problems. Maybe the installation and deinstallation of 2.0.6 resolved this. If you're interested in the logfiles, I still have them.

But unfortunately when starting 2.1.0 now gives me a new message about the xml file.

I removed the file C:\Documents and Settings\<username>\.VirtualBox\VirtualBox.xml (I think it was remnant of the previous install).

Now it works.