ProcFunc - NSIS Process Function Header

All work! Steeply!
Loosed in GoTo))

Thank you for good code!

It is Correct I use your code gentlemen? The Paircouple beside I work only for 1 file!
If I try right behind close one more file that beside me is not got.
Prompt please.

!macro StopExe NAME
StrCpy $tmpRetVal 0
StrCpy $tmpCount 0
DetailPrint "Çàâåðøåíèå ðàáîòû '${NAME}'"

StrCpy $tmpCount 2 ;// ×èñëî ïîïûòîê
${CloseProcess} "${NAME}" $tmpRetVal

${Do}
${If} $tmpRetVal != 0
${ProcessWaitClose} "${NAME}" "1000" $tmpRetVal

${EndIf}
;// -1 - operation timed out
IntOp $tmpCount $tmpCount - 1 ;// Ñ÷åò÷èê ïîïûòîê
${If} $tmpRetVal == 0
StrCpy $tmpCount $tmpRetVal ;Íå íàéäåí ïðîöåññ èëè çàêðûò
${EndIf}

${LoopUntil} $tmpCount == 0 ;// Ïîêà åñòü ïîïûòêè è ïðîöåññ åùå íå óáèò

${If} $tmpRetVal

These functions did not function as I had expected I was hoping to create a semi-automated script for parsing through a list and ending the functions in a list, but when I use ${TerminateProcess} the process is ended and then the .exe file is deleted? and when I use the ${CloseProcess} nothing happens, except for the launcher parsing through the ini file, searching for the process, obtaining the PID, obtaining the path, and attempting to end the process, but it never is ended, did I do something wrong in these two parts of a section?

${CloseProcess} "blah.exe" $1
${If} $1 == 1
  Goto Error
${EndIf}

or

${TerminateProcess} "blah.exe" $1
${If} $1 == 1
  Goto Error
${EndIf}

(edit) turns out the loop was faulty and directed it to the delete option

Can anybody help me, why this code wrong? Why CloseProcess works only once?

Name "NSIS ProcFunc Test"
OutFile "ProcFunc.exe"
ShowInstDetails show
RequestExecutionLevel user

!include "ProcFunc.nsh"

Page components
Page instfiles

Section "Run tests" TESTS

    Exec "notepad.exe"
    Exec "calc.exe"
    Exec "mspaint.exe"

    MessageBox MB_OK "Ready?"

    DetailPrint "Close notepad"
    ${CloseProcess} "notepad.exe" $0
    ${ProcessWaitClose} "notepad.exe" -1 $0

    DetailPrint "Close calc"
    ${CloseProcess} "calc.exe" $0
    ${ProcessWaitClose} "calc.exe" -1 $0

    DetailPrint "Close mspaint"
    ${CloseProcess} "mspaint.exe" $0
    ${ProcessWaitClose} "mspaint.exe" -1 $0

SectionEnd

The ${EnumProcessPaths} only report the installer itself on 64-bit windows. The same code works well on 32-bit windows. Is this a bug?

I l know that this topic is well over 4 years old and I know that much of this has been added into the th ePA Launcher, so do NOT get angry at me for adding to an old thread since I did what everyone tells use to do and search the forums first, heck I even searched Google for my answer and this was one of the first 5 hits.

I amdeveloping amarok, one of the issues I am trying to deal with is that after the main program exits there any where from 4-8 processes still running that prevent you from removing the drive as it is "still in use" I can manually kill them and all is good. SO I was looking into writing some custom launcher code in the post phase to kill the processes which brought me back here. If this code is now part of the PA Launcher can I kill them from within the launcher or use parts of this code to create a post section? Since I know the processes that need killing I think I could just usse the KillProc feature? Any help or ideas appreciated

how can i modify this script to allow me to execute a process hiding his window ?