This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
NAndre
Level 3
‎Apr 01, 2009 09:11 AM

ISBEW64.exe left on the system

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?
Labels (1)
Labels
0 Kudos

(4) Replies
NAndre
Level 3
‎Apr 03, 2009 01:41 AM

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
0 Kudos
NAndre
Level 3
‎Jun 24, 2009 05:12 AM

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

Best regards
NAndre
0 Kudos
joshstechnij
Level 10 Flexeran
Level 10 Flexeran
‎Jun 24, 2009 12:13 PM

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.
0 Kudos
bisdakbabbles
Level 3
‎Jun 28, 2016 02:05 AM

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.
0 Kudos