It's 'very smart' to think that there is an installer file in a TEMP-directory after weeks or month to use it for uninstalling

[virtualboxuser]

It's 'very smart' to think that there is an installer file in a TEMP-directory after weeks or month to use it for uninstalling.

Actually the installer of VirtualBox 3.1.4 couldn't install because the old *.msi couldn't be found to deinstall the old version. Very natural in times when a lot of cleaning tools are around or TEMP and CACHE-Directories are put on RAM-Disks to get rid of this stuff on reboot.

So if you need something for deinstalling or repairing the TEMP-Dir of a user or the system is obviously the wrong place, you should put it into a subdirectory of the installation directory and everything is fine, no cleaning tool will empty those directories, when shutting down or during startup.

And as you already have done it the wrong way, you have to enable new installers to get rid of old versions by itself or deliver a special deinstallation tool.

Don't forget old settings have to be kept for the new version.

PS: I'm not a native English speaker, so everyone is allowed to keep any typing or grammatical errors she or he finds in the Text. ;-)

[pentagonik]

That actually is not true. Our stub loader (.exe) extracts the appropriate .MSI files in the temp directory you've written about to start it from there; after installation the actual MSI script/resources for this installer are kept in an interal Windows database which does *not* rely on the .MSI extracted into the temp directory previously mentioned in any way. Other .MSI installers of apps or games which come from a CD or USB-Stick also wouldn't work if they need to be present on the system all the time.

Instead of accusing us doing something 'silly' that fast without any real proof please provide more background information on this issue (how to reproduce the error you got and/or technical specs for MSIs on how to handle temporary storage).