APT

Discussion in 'ProcessGuard' started by Anim8, Aug 7, 2006.

Thread Status:
Not open for further replies.
  1. Anim8

    Anim8 Registered Member

    Joined:
    Jun 7, 2006
    Posts:
    19
    When I try and kill a process with APT, PG stops all kill types. When I use the Multi kill tool in ATP the kill modes 6 and up kill apps. Am I setting somthing wrong? Using 3.405 full, all global protection options turned on.

    Thanks.

    Edit: Doesn't seem to be the case any more. I tried to reinstall, same options set but now PG fails at test 2,3 and 4. (Tested on notepad)
     
    Last edited: Aug 7, 2006
  2. Paranoid2000

    Paranoid2000 Registered Member

    Joined:
    May 2, 2004
    Posts:
    2,839
    Location:
    North West, United Kingdom
    Make sure that APT does not have Terminate or Modify permissions in Process Guard and that the process in question is protected against both modification and termination. Kill methods 2, 3 and 4 will need PG's Secure Message Handling option active on the protected application (if that application has a window open on your desktop).
     
  3. Anim8

    Anim8 Registered Member

    Joined:
    Jun 7, 2006
    Posts:
    19
    Ok after putting on Secure Message Handling option active, it now blocks all kill types. I don't like having it on cause I dont like having to put in the code to kill the app each time.

    Thanks for your help, Paranoid2000
     
  4. Remouald

    Remouald Registered Member

    Joined:
    Dec 16, 2005
    Posts:
    99
    I hope it's okay to post it in this thread...

    I have PG 3.150.

    With APT, I can kill procguard.exe using the method 3 (WM_QUIT) even though I have "Secure Message Handling" selected.

    I use the INSERT key to make the "exit" function on PG tray icon recognized by the secure message handling method and it works.

    But when I try to kill procguard.exe with APT Kill 3, APT tell me "Process still exists, termination appears to have been unsuccessful" and I have the "secure message handling" popup appearing but NO PG tray icon which means procguard.exe was killed. And indeed, procguard.exe is no more running.
     
  5. some made up name

    some made up name Registered Member

    Joined:
    Jan 31, 2006
    Posts:
    60
    PG3.4b1 fixes WM_QUIT protection

    as WM_QUIT exits the app it still needs to cleanup (destroy) any resources (eg windows) and that is probably still being caught by PG 3.150 (even though the app has actually exited)
     
  6. Remouald

    Remouald Registered Member

    Joined:
    Dec 16, 2005
    Posts:
    99
    Thanks for your reply!
    I guess I should upgrade to 3.405 :)
     
Thread Status:
Not open for further replies.