Temp folder not cleaning up

[skincaid]

Hello,

I'm running some tests here on our installer and it looks like InstallAware 18 is not cleaning up files in the Temp if a reboot/resume occurs during installation in Windows 7. The scenario is as follows:

1) InstallAware unpacks itself upon execution into a 7z(ID).tmp file in AppData\Local\Temp.

2) InstallAware runs various MSI's/Installers until a reboot is required. User clicks ok to initiate the reboot, but the original 7z(ID).tmp file is not removed when InstallAware exits right before the reboot.

3) When the computer comes back up, InstallAware extracts itself a second time but into a second 7z(ID2).tmp file.

4) If no other reboot occurs, InstallAware will cleanup the second 7z(ID2).tmp file but never touch the original 7z(ID).tmp file, leaving 2GB of data around on the users system.

If there are multiple reboots, then there will be 1+ files left in the temp folder depending on the number of reboots that occur during the installation. This scenario also happens in Windows XP when running InstallAware 12 but some of the files inside of the mia(ID).tmp folder are cleaned up (unsure of which ones). In both cases though, the original temp folder is not being cleaned up if a reboot/resume occurs. Is there anyway to have InstallAware clean up all of these temporary files, regardless of the a reboot/resume?

[FrancescoT]

Dear User,

probably I haven't been able to follow your identical steps, but I am unable to replicate your issue.

If you are able to replicate this behavior with a test project, post it and I'll try to verify it.

Regards

[skincaid]

There isn't anything that's specifically ours in this prerequisite installer. Our project consists of the following:

.NET 2.0 with Service Pack 2
.NET 3.0
.NET 3.0 Service Pack 2
.NET 3.5 with Service Pack 1
.NET 4.0
.NET 4 Client
Microsoft SQL Server Express 2008 R2
C++ Runtime 10.0
Windows Installer 4.5
Microsoft XML Parser 6.0.

If you enable these in the application runtimes, build an installer, and run the installer on a machine that would require multiple reboots with this configuration (Windows XP). It should be reproducible.

[FrancescoT]

let me check.

Regards