ISBEW64.exe left on the system

[NAndre]

After my product is installed there are several files ISBEW64.exe left on the system (in C:\Program FIles\Administrator\Local Settings\Temp\{guid}\).

This file is Install Shield 64-bit Setup Engine.

We using BasicMSI projects with IS script custom actions.

How can I configure my installation to have these files removed after install or not installed at all?

[NAndre]

Hello, what can I do now?

In the setup.rul I have replaced:
#include "isrt.h"
#include "iswi.h"
(this is from IS 12)
with:
#include "ifx.h"
(this is from IS 2009).

But it does not help.
After my product is installed there are several files ISBEW64.exe left on the system with Vista 64 (in ..\Local Settings\Temp\{guid}\).

Best regards
NAndre

[NAndre]

Hello, is there any help?
The problem still exist.:confused:

Best regards
NAndre

[joshstechnij]

We currently have a work order open regarding this issue (IOC-000081591). Since this file is not removed from a volatile location (there's no guarantee that temp folder contents will always be available), this should not be a critical issue.

[bisdakbabbles]

Has this been solved?
This thread started many years ago but it seems that the issue is not closed.

I'm using InstallShield 2012 and this problem now occurs in Windows 10.