misha wrote: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 logging2. 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 installs3. 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.

Hm, interesting,

Yes, I think the "succeeded install" logs would be useful.
Could you also post those you've backed up (unless you deleted them Unless the setupapi logging was completely switched off (which is not the case for Vista by default) they should contain the info on your previous (failed) installs.
You might strip them and post only the last parts of them concerning the latest installations that were failing.

BTW, the failing installs, did they occur when you install on top of the previous installation or you deleted the previous installation fist? or in both cases?
Also how many times did you try to install before succeeding? I'm actually interested whether it was a second install that succeeded, or it failed more than once?

misha wrote: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 logging2. 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 installs3. 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.

Hm, interesting,

Yes, I think the "succeeded install" logs would be useful.Could you also post those you've backed up (unless you deleted them Unless the setupapi logging was completely switched off (which is not the case for Vista by default) they should contain the info on your previous (failed) installs.You might strip them and post only the last parts of them concerning the latest installations that were failing.

BTW, the failing installs, did they occur when you install on top of the previous installation or you deleted the previous installation fist? or in both cases?Also how many times did you try to install before succeeding? I'm actually interested whether it was a second install that succeeded, or it failed more than once?

For me, 2.1.0 was the first version I've ever installed, and it has failed about 10 times now (I've been trying stuff).

misha wrote:Surye: could you post %windir%\inf\setupapi.dev.log and %windir%\inf\setupapi.app.log (for vista) or %windir%\setupapi.log (for XP) to http://www.virtualbox.org/ticket/1730 or anywhere else?

Already did so this morning I'm quite interested in getting this working. Also, I'm installing the 64bit version, I just noticed this thread is about the 32bit installer

Could you post the setupapi.dev.log as well?
The setupapi.app.log you uloaded does not seem informative btw Have you set the "REG_DWORD LogLevel" value under "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup" to 4800FFFF hexadecimal value - to enable the verbose setupapi logging (as I mentioned in a previous comment)?

misha wrote:Surye: could you post %windir%\inf\setupapi.dev.log and %windir%\inf\setupapi.app.log (for vista) or %windir%\setupapi.log (for XP) to http://www.virtualbox.org/ticket/1730 or anywhere else?

Already did so this morning I'm quite interested in getting this working. Also, I'm installing the 64bit version, I just noticed this thread is about the 32bit installer

Could you post the setupapi.dev.log as well? The setupapi.app.log you uloaded does not seem informative btw Have you set the "REG_DWORD LogLevel" value under "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup" to 4800FFFF hexadecimal value - to enable the verbose setupapi logging (as I mentioned in a previous comment)?

It doesn't seem to be creating a setupapi.dev.log, only a setupapi.app.log. And I did set that key.

I'm having the same problem, I've set the key and run the commmand but only the log file I specify is created.

Surye wrote:

misha wrote:

Surye wrote:

misha wrote:Surye: could you post %windir%\inf\setupapi.dev.log and %windir%\inf\setupapi.app.log (for vista) or %windir%\setupapi.log (for XP) to http://www.virtualbox.org/ticket/1730 or anywhere else?

Already did so this morning I'm quite interested in getting this working. Also, I'm installing the 64bit version, I just noticed this thread is about the 32bit installer

Could you post the setupapi.dev.log as well? The setupapi.app.log you uloaded does not seem informative btw Have you set the "REG_DWORD LogLevel" value under "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup" to 4800FFFF hexadecimal value - to enable the verbose setupapi logging (as I mentioned in a previous comment)?

It doesn't seem to be creating a setupapi.dev.log, only a setupapi.app.log. And I did set that key.