wm_destroy

Discussion in 'ProcessGuard' started by tokdok, Nov 24, 2005.

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

    tokdok Registered Member

    Joined:
    Aug 4, 2004
    Posts:
    11
    Location:
    Slapout, Alabama
    Hope everyone is having a great Thanksgiving--turkey & dressing on the way here....

    I did a Windows Update, MS .NET Framework, and now get the following PG warning on bootup:

    Process Name: Explorer.exe
    Thunder RTGFormDC
    Message: WM_Destroy

    "Do you really want to allow?" (Type in the letters....)

    Disallowing it makes the QuickLaunch tray go awry. Allowing it usually makes things go normally, but not always. Mostly little things and not consistently, but it is a nuisance. Any idea how to solve this?

    Thanks,
    cp

    PS I'll be back in a few hours after adding to the waistline....:rolleyes:
     
    Last edited: Nov 24, 2005
  2. Gavin - DiamondCS

    Gavin - DiamondCS Former DCS Moderator

    Joined:
    Feb 10, 2002
    Posts:
    2,080
    Location:
    Perth, Western Australia
    Remove Close Message Handling for explorer.exe, you dont need it :)
     
  3. tokdok

    tokdok Registered Member

    Joined:
    Aug 4, 2004
    Posts:
    11
    Location:
    Slapout, Alabama
    Sorry, I didn't know I had a reply. Do you mean "secure message handling?"
     
  4. Gavin - DiamondCS

    Gavin - DiamondCS Former DCS Moderator

    Joined:
    Feb 10, 2002
    Posts:
    2,080
    Location:
    Perth, Western Australia
    Hi, yes sorry my mistake. This should only be set in rare circumstances, the default protection is all most processes need.

    ALLOW access are the other boxes in the same place, and only apps which request such rights really need them. Trusted apps should be given rights they request. Learning Mode is designed for this and will protect/allow everything given a little time to do so..
     
  5. tokdok

    tokdok Registered Member

    Joined:
    Aug 4, 2004
    Posts:
    11
    Location:
    Slapout, Alabama
    Thanks, Gavin.

    Take care,
    cp
     
Thread Status:
Not open for further replies.