Menu
Only has an effect when combined with '/SILENT' and '/VERYSILENT'. See '/SUPPRESSMSGBOXES' under Setup Command Line Parameters for more details. Causes Uninstall to create a log file in the user's TEMP directory detailing file uninstallation and UninstallRun actions taken during the uninstallation process. This can be a helpful. Once the actual installation process begins, this is the order in which the various installation tasks are performed: InstallDelete is processed. The entries in UninstallDelete are stored in the uninstall log (which, at this stage, is stored in memory).; The application directory is created, if necessary. Inno Setup Kill Process Before Install Average ratng: 3,7/5 7101 votes End a process with Inno setup. 2018//02/22 - Dallas. These two functions will ctry to close the process gt4t.exe at installation and uninstallation. Inno Setup Kill Process Before Install. 7/9/2018 admin. For years I have been making installers with innosetup, on Windows XP SP3. I have just installed the latest.
- Orange Lamp Kill Process
- Inno Setup Install Service
- Kill Process Program
- Inno Setup Kill Process Before Install Windows 10
- Inno Setup Kill Process Before Install Windows 10
- Inno Setup Install Prerequisite Software
2020腾讯云10周年活动,优惠非常大!(领取2860元代金券),
地址:https://cloud.tencent.com/act/cps/redirect?redirect=1040
地址:https://cloud.tencent.com/act/cps/redirect?redirect=1040
2020阿里云最低价产品入口,含代金券(新老用户有优惠),
地址:https://www.aliyun.com/minisite/goods
地址:https://www.aliyun.com/minisite/goods
up vote 14 down vote favorite 11 This should be simple, I need to stop any previous version of my program from running when the installer starts. Most people suggested making an exe which does this and calling it before Inno Setup starts. I created an exe using AutoIt which kills all processes of my program. The problem is I don't know how to get Inno Setup to call it before it installs anything. How do I call an executable before installing files? Alternatively, if I can just detect if a program is running and tell the user to close it, that would work too. installer inno-setup
|
this question edited Jun 21 '16 at 5:54 Martin Prikryl 48.3k 15 68 171 asked Aug 17 '10 at 23:46 Daisetsu 1,818 6 37 56
| 9 Answers|
this question edited Jun 21 '16 at 5:54 Martin Prikryl 48.3k 15 68 171 asked Aug 17 '10 at 23:46 Daisetsu 1,818 6 37 56
up vote 24 down vote ---Accepted---Accepted---Accepted---
If the application has a Mutex, you can add an AppMutex value in your Inno Setup installer and it will display a message telling the user to stop the program. You might be able to find the Mutex (if it's got one) by using SysInternals Process Explorer and selecting the program / process and looking at the Handles (CTRL-H) in the Lower Pane. Here's a link to the a KB article that mentions several methods: http://www.vincenzo.net/isxkb/index.php?title=Detect_if_an_application_is_running Alternatively, you might try this (UNTESTED) code in the InitializeSetup: [Setup]
;If the application has
Mutex, uncomment the line below, comment the InitializeSetup function out, and use the AppMutex.
;AppMutex=MyApplicationMutex
[Code]
const
WM_CLOSE = 16;
function InitializeSetup : Boolean;
var winHwnd: Longint;
retVal : Boolean;
strProg: string;
begin
Result := True;
try
//Either use FindWindowByClassName. ClassName can be found with Spy++ included with Visual C++.
strProg := 'Notepad';
winHwnd := FindWindowByClassName(strProg);
//Or FindWindowByWindowName.
If using by Name, the name must be exact and is case sensitive.
strProg := 'Untitled - Notepad';
winHwnd := FindWindowByWindowName(strProg);
Log('winHwnd: ' + IntToStr(winHwnd));
if winHwnd <> 0 then
Result := PostMessage(winHwnd,WM_CLOSE,0,0);
except
end;
end;
|
this answer edited Jun 21 '16 at 6:02 Martin Prikryl 48.3k 15 68 171 answered Aug 18 '10 at 1:34 mirtheil 5,661 17 21 Thanks Mirtheil, this is exactly what I needed. Everyone else provided reasonable answers but this turns out to be the perfect solution. – Daisetsu Aug 18 '10 at 18:35 does not work on Windows 7 – Mason Zhang Oct 19 '11 at 15:11 Actually, it didn't work on anything. Once the correct window name was used, it does work on Windows 7 and other OSes. I also added an alternative to FindWindowByWindowName which is FindWindowByClassName. FindWindowByClassName might be a better choice if your program's window name changes. – mirtheil Oct 19 '11 at 19:23 3 For Inno 5.5.0+ there's a new solution, as I explain in my late response to this question. – jachguate Nov 27 '12 at 11:25 According to the documentation, it is better to use the function PrepareToInstall instead of InitializeSetup to shutdown the application to update. – Zac Oct 27 '16 at 8:48 | show 1 more comment up vote 11 down vote In version 5.5.0 (Released on May 2012) Inno Setup added support for the Restart Manager API on Windows Vista and newer. Quote from MSDN linked documentation (emphasis mine): The primary reason software installation and updates require a system restart is that some of the files that are being updated are currently being used by a running application or service. Restart Manager enables all but the critical applications and services to be shut down and restarted. This frees the files that are in use and allows installation operations to complete. It can also eliminate or reduce the number of system restarts that are required to complete an installation or update. The good thing is not you don't need to write custom code in the installer or your application to ask the user to close it, or close it automatically. If you want your application to restart after the update is complete, you have to call the RegisterApplicationRestart function from your application first. The default values for the new directives closes all the .exe, .dll and .chm files contained within the [Files] section of the installer. The changes related to it are (from release notes): Added new [Setup] section directive: CloseApplications, which defaults to yes. If set to yes and Setup is not running silently, Setup will now pause on the Preparing to Install wizard page if it detects applications using files that need to be updated by the [Files] or [InstallDelete] section, showing the applications and asking the user if Setup should automatically close the applications and restart them after the installation has completed. If set to yes and Setup is running silently, Setup will always close and restart such applications, unless told not to via the command line (see below). Added new [Setup] section directive: CloseApplicationsFilter, which defaults to *.exe,*.dll,*.chm. Controls which files Setup will check for being in use. Setting this to *.* can provide better checking at the expense of speed. Added new [Setup] section directive: RestartApplications, which defaults to yes. Note: for Setup to be able to restart an application after the installation has completed, the application needs to be using the Windows RegisterApplicationRestart API function. Added new command line parameters supported by Setup: /NOCLOSEAPPLICATIONS and /NORESTARTAPPLICATIONS. These can be used to override the new CloseApplications and RestartApplications directives. Added new [Code] support function: RmSessionStarted. TWizardForm: Added new PreparingMemo property.
|
this answer edited Jun 21 '16 at 5:57 Martin Prikryl 48.3k 15 68 171 answered Nov 27 '12 at 11:23 jachguate 14.6k 1 35 73 2 great answer, thanks! – João Moreno Aug 7 '15 at 10:22
answer (and the follow up by jachguate) but it wouldn't kill my application. It looks like part of the reason was that my application window had no text associated with it but whatever is the real reason, I used shell command to kill it and that worked. In the [code] section, you want to add the following function. It is called just before setup files are copied. function PrepareToInstall(var NeedsRestart: Boolean): String;
var
ErrorCode: Integer;
begin
ShellExec('open',
'taskkill.exe', '/f /im MyProg.exe',',SW_HIDE,ewNoWait,ErrorCode);
end;
|
this answer edited Sep 20 '16 at 20:59 answered Aug 5 '13 at 16:48 zar 3,033 3 30 68
|
this answer answered Aug 18 '10 at 0:13 Conor Boyd 803 5 13 That won't work as the program has been released for years and I will need to close down old versions too. – Daisetsu Aug 18 '10 at 0:27 | up vote 3 down vote Here's a link to an Inno Setup script that prompts a user to close the target program, if it detects that the program is running. After the user closes the program, they can click on a 'Retry' button to proceed with the installation: http://www.domador.net/extras/code-samples/inno-setup-close-a-program-before-reinstalling-it/ This script is based on a simpler script, found in the Inno Setup Extensions Knowledge Base: http://www.vincenzo.net/isxkb/index.php?title=Call_psvince.dll_on_install_and_uninstall
|
this answer answered May 18 '11 at 21:20 Andres Cabezas Ulate 51 2 | up vote 1 down vote If you are happy to write your own DLL, you can use the tool help API for TlHelp32.pas to determine what applications are running, and then get a window handle for them using EnumWindows, then send a WM_CLOSE to the window handle. It's a bit of a pain, but it should work: I have some utility wrapper classes I developed with a friend a while back. Can't remember if we based it on someone else's code. TWindows.ProcessISRunning and TWindows.StopProcess may help. interface
uses
Classes,
Windows,
SysUtils,
Contnrs,
Messages;
type
TProcess = class(TObject)
public
ID: Cardinal;
Name: string;
end;
TWindow = class(TObject)
private
FProcessID: Cardinal;
FProcessName: string;
FHandle: THandle;
FProcessHandle : THandle;
function GetProcessHandle: THandle;
function GetProcessID: Cardinal;
function GetProcessName: string;
public
property Handle : THandle read FHandle;
property ProcessName : string read GetProcessName;
property ProcessID : Cardinal read GetProcessID;
property ProcessHandle : THandle read GetProcessHandle;
end;
TWindowList = class(TObjectList)
private
function GetWindow(AIndex: Integer): TWindow;
protected
public
function Add(AWindow: TWindow): Integer; reintroduce;
property Window[AIndex: Integer]: TWindow read GetWindow; default;
end;
TProcessList = class(TObjectList)
protected
function GetProcess(AIndex: Integer): TProcess;
public
function Add(AProcess: TProcess): Integer; reintroduce;
property Process[AIndex: Integer]: TProcess read GetProcess; default;
end;
TWindows = class(TObject)
protected
public
class function GetHWNDFromProcessID(ProcessID: Cardinal; BuildList: Boolean = True): THandle;
class function GetProcessList: TProcessList;
class procedure KillProcess(ProcessName: string);
class procedure StopProcess(ProcessName: string);
class function ExeIsRunning(ExeName: string): Boolean;
class function ProcessIsRunning(PID: Cardinal): Boolean;
end;
implementation
uses
Forms,
Math,
PSAPI,
TlHelp32;
const
cRSPUNREGISTERSERVICE = 0;
cRSPSIMPLESERVICE = 1;
type
TProcessToHWND = class(TObject)
public
ProcessID: Cardinal;
HWND: Cardinal;
end;
function RegisterServiceProcess(dwProcessID, dwType: DWord): DWord; stdcall; external 'KERNEL32.DLL';
function GetDiskFreeSpaceEx(lpDirectoryName: PChar;
var lpFreeBytesAvailableToCaller, lpTotalNumberOfBytes: TLargeInteger;
lpTotalNumberOfFreeBytes: PLargeInteger): Boolean; stdcall;external 'KERNEL32.DLL' name 'GetDiskFreeSpaceExA'
var
GProcessToHWNDList: TObjectList = nil;
function EnumerateWindowsProc(hwnd: HWND; lParam: LPARAM): BOOL; stdcall;
var
proc: TProcessToHWND;
begin
if Assigned(GProcessToHWNDList) then
begin
proc := TProcessToHWND.Create;
proc.HWND := hwnd;
GetWindowThreadProcessID(hwnd, proc.ProcessID);
GProcessToHWNDList.Add(proc);
Midi files cinderella. Result := True;
end
else
Result := False; // stop enumeration
end;
{ TWindows }
class function TWindows.ExeIsRunning(ExeName: string): Boolean;
var
processList: TProcessList;
i: Integer;
begin
Result := False;
processList := GetProcessList;
try
for i := 0 to processList.Count - 1 do
begin
if (UpperCase(ExeName) = UpperCase(processList[i].Name)) or
(UpperCase(ExeName) = UpperCase(ExtractFileName(processList[i].Name))) then
begin
Result := True;
Break;
end;
end;
finally
processList.Free;
end;
end;
class function TWindows.GetHWNDFromProcessID( Sybase sql anywhere 12 free download.
ProcessID: Cardinal; BuildList: Boolean): THandle;
var
i: Integer;
begin
Result := 0;
if BuildList or (not Assigned(GProcessToHWNDList)) then
begin
GProcessToHWNDList.Free;
GProcessToHWNDList := TObjectList.Create;
EnumWindows(@EnumerateWindowsProc, 0);
end;
for i := 0 to GProcessToHWNDList.Count - 1 do
begin
if TProcessToHWND(GProcessToHWNDList[i]).ProcessID = ProcessID then
begin
Result := TProcessToHWND(GProcessToHWNDList[i]).HWND;
Break;
end;
end;
end;
class function TWindows.GetProcessList: TProcessList;
var
handle: THandle;
pe: TProcessEntry32;
process: TProcess;
begin
Result := TProcessList.Create;
handle := CreateToolhelp32Snapshot(TH32CS_SNAPPROCESS, 0);
pe.dwSize := Sizeof(pe);
if Process32First(handle, pe) then
begin
while True do
begin
process := TProcess.Create;
process.Name := pe.szExeFile;
process.ID := pe.th32ProcessID;
Result.Add(process);
if not Process32Next(handle, pe) then
Break;
end;
end;
CloseHandle(handle);
end;
function EnumWindowsProc(Ahwnd : HWND;
// handle to parent window
ALParam : Integer) : BOOL;stdcall;
var
List : TWindowList;
Wnd : TWindow;
begin
Result := True;
List := TWindowList(ALParam);
Wnd := TWindow.Create;
List.Add(Wnd);
Wnd.FHandle := Ahwnd;
end;
class procedure TWindows.KillProcess(ProcessName: string);
var
handle: THandle;
pe: TProcessEntry32;
begin
// Warning: will kill all process with ProcessName
// NB won't work on NT 4 as Tool Help API is not supported on NT
handle := CreateToolhelp32Snapshot(TH32CS_SNAPPROCESS, 0);
try
pe.dwSize := Sizeof(pe);
if Process32First(handle, pe) then
begin
while True do begin
if (UpperCase(ExtractFileName(pe.szExeFile)) = UpperCase(ExtractFileName(ProcessName))) or
(UpperCase(pe.szExeFile) = UpperCase(ProcessName)) then
begin
if not TerminateProcess(OpenProcess(PROCESS_TERMINATE, False,
pe.th32ProcessID), 0) then
begin
raise Exception.Create('Unable to stop process ' + ProcessName + ': Error Code ' + IntToStr(GetLastError));
end;
end;
if not Process32Next(handle, pe) then
Break;
end;
end;
finally
CloseHandle(handle);
end;
end;
class function TWindows.ProcessIsRunning(PID: Cardinal): Boolean;
var
processList: TProcessList;
i: Integer;
begin
Result := False;
processList := GetProcessList;
try
for i := 0 to processList.Count - 1 do
begin
if processList[i].ID = PID then
begin
Result := True;
Break;
end;
end;
finally
processList.Free;
end;
end;
class procedure TWindows.StopProcess(ProcessName: string);
var
processList: TProcessList;
i: Integer;
hwnd: THandle;
begin
// Warning: will attempt to stop all process with ProcessName
if not Assigned(GProcessToHWNDList) then
GProcessToHWNDList := TObjectList.Create
else
GProcessToHWNDList.Clear;
// get list of all current processes
processList := GetProcessList;
// enumerate windows only once to determine the window handle for the processes
if EnumWindows(@EnumerateWindowsProc, 0) then
begin
for i := 0 to processList.Count - 1 do
begin
if UpperCase(ExtractFileName(processList[i].Name)) = UpperCase(ExtractFileName(ProcessName)) then
begin
hwnd := GetHWNDFromProcessID(processList[i].ID, False);
SendMessage(hwnd, WM_CLOSE, 0, 0);
end;
end;
end;
end;
{ TProcessList }
function TProcessList.Add(AProcess: TProcess): Integer;
begin
Result := inherited Add(AProcess);
end;
function TProcessList.GetProcess(AIndex: Integer): TProcess;
begin
Result := TProcess(Items[AIndex]);
end;
{ TWindowList }
function TWindowList.Add(AWindow: TWindow): Integer;
begin
Result := inherited Add(AWindow);
end;
function TWindowList.GetWindow(AIndex: Integer): TWindow;
begin
Result := TWindow(Items[AIndex]);
end;
{ TWindow }
function TWindow.GetProcessHandle: THandle;
begin
if FProcessHandle = 0 then
FProcessHandle := OpenProcess(Windows.SYNCHRONIZE or Windows.PROCESS_TERMINATE,
True, FProcessID);
Result := FProcessHandle;
end;
function TWindow.GetProcessID: Cardinal;
var
Pid : Cardinal;
begin
if FProcessID = 0 then
begin
Pid := 1;
GetWindowThreadProcessId(Handle, Pid);
FProcessID := Pid;
end;
Result := FProcessID;
end;
function TWindow.GetProcessName: string;
var
Buffer : packed array [1.1024] of char;
len : LongWord;
begin
FillChar(Buffer, SizeOf(Buffer), 0);
if FProcessName = ' then
begin
len := GetWindowModuleFileName(Handle, @Buffer[1], 1023);
FProcessName := Copy(Buffer, 1, Len);
end;
Result := FProcessName;
end;
end.
|
this answer answered Aug 18 '10 at 9:48 Gerry Coll 5,198 1 18 32 Failed to compile in InnoSetup, could anyone fix it? I never used pascal before. – Mason Zhang Oct 19 '11 at 14:34
var Macdraw pro.
ResultCode: Integer;
wmicommand: string;
begin
// before installing any file
if CurStep = ssInstall then
begin
wmicommand := ExpandConstant('PROCESS WHERE 'ExecutablePath like '{app}%%'' DELETE');
// WMIC 'like' expects escaped backslashes
StringChangeEx(wmicommand, ', ', True);
// you can/should add an 'if' around this and check the ResultCode
Exec('WMIC', wmicommand, ', SW_HIDE, ewWaitUntilTerminated, ResultCode);
end;
end;
You can also do it in the InitializeSetup but if you do, keep in mind you don't have yet access to the {app} constant. My program doesn't ask for install path, but yours might.
|
this answer edited Mar 20 at 10:18 Community ♦ 1 1 answered Oct 6 '16 at 13:14 thomasb 3,040 2 36 67
| up vote 0 down vote InnoSetup allows you to attach Pascal scripts to various places in the build process. Try attaching a script that calls ShellExecute. (Which you may have to import to the script engine if it doesn't already have it.) |
this answer edited Mar 20 at 10:18 Community ♦ 1 1 answered Oct 6 '16 at 13:14 thomasb 3,040 2 36 67
|
this answer answered Aug 18 '10 at 0:12 Mason Wheeler 60k 30 198 369 The script engine has Exec() so that's not the problem. I can't figure out how to write the pascal code though to extract the bundled exe file and run it. – Daisetsu Aug 18 '10 at 0:27 | up vote 0 down vote Well, I think the easier way to perform this may be creating a DLL in Delphi that detects if your program is running and ask the user to close it, put that DLL in your setup and use the flag 'dontcopy' (check in http://www.jrsoftware.org/ishelp/ under Pascal Scripting Using DLLs for an example). Btw, next time use mutexes, Inno Setup also support that and is far more easier. EDIT: and for extracting a file (if you want to use that .exe you mention), just use ExtractTemporaryFile().
|
Orange Lamp Kill Process
this answer answered Aug 18 '10 at 0:41 someone 896 1 5 8 |
Inno Setup Install Service
up vote 14 down vote favorite 11 This should be simple, I need to stop any previous version of my program from running when the installer starts. Most people suggested making an ex
- 1android静默安装apk已经成功实现
- 2安装打包之VisualStuido
- 3[Oracle] UNIX与Windows 2000上Oracle的差异(III)
- 4使用Opencv 2.1/2.2 编译64位程序时,编译器内部错误 error c1001
- 5ORA-06553: PLS-213: package STANDARD not accessible
- 1微信公众号文章采集,并发布到WordPress
最新文章
Kill Process Program
- 1linux之universal usb installer安装ubuntu
- 2Windows程序安装包制作——Qt Installer Framework
- 3path too long installer unable to modify path 导致PCL配置失败记
- 4android sdk manager的extras中没有intel emulator accelerator(HAXM installer)
- 5Cloud Foundry 部署问题(2)buildpack时间过长
- 6VS2010程序打包操作(超详细的)
Beginning with Inno Setup 3.0.3, the Setup program may return one of the following exit codes:
Inno Setup Kill Process Before Install Windows 10
0 | Setup was successfully run to completion or the /HELP or /? command line parameter was used. |
1 | Setup failed to initialize. |
2 | The user clicked Cancel in the wizard before the actual installation started, or chose 'No' on the opening 'This will install..' message box. |
3 | A fatal error occurred while preparing to move to the next installation phase (for example, from displaying the pre-installation wizard pages to the actual installation process). This should never happen except under the most unusual of circumstances, such as running out of memory or Windows resources. |
4 | A fatal error occurred during the actual installation process. Note: Errors that cause an Abort-Retry-Ignore box to be displayed are not fatal errors. If the user chooses Abort at such a message box, exit code 5 will be returned. |
5 | The user clicked Cancel during the actual installation process, or chose Abort at an Abort-Retry-Ignore box. |
6 | The Setup process was forcefully terminated by the debugger (Run | Terminate was used in the IDE). |
7 | The Preparing to Install stage determined that Setup cannot proceed with installation. (First introduced in Inno Setup 5.4.1.) |
8 | The Preparing to Install stage determined that Setup cannot proceed with installation, and that the system needs to be restarted in order to correct the problem. (First introduced in Inno Setup 5.4.1.) |
Inno Setup Kill Process Before Install Windows 10
Before returning an exit code of 1, 3, 4, 7, or 8, an error message explaining the problem will normally be displayed.
Inno Setup Install Prerequisite Software
Future versions of Inno Setup may return additional exit codes, so applications checking the exit code should be programmed to handle unexpected exit codes gracefully. Any non-zero exit code indicates that Setup was not run to completion.