Jump to content
Sign in to follow this  
yakir

ProcessClose dont close the process >.<

Recommended Posts

ProcessClose dont close the process >.<

i have a process i try to close useing processClose but it wont close also this process wont respond to mouseclick or send commend

pls help

Share this post


Link to post
Share on other sites

What does ProcessClose return?

$Result = ProcessClose($Process) 
Consolewrite("Result: " & $Result & ", @Error: " & @error & @CRLF)

My UDFs and Tutorials:

Spoiler

UDFs:
Active Directory (NEW 2020-10-10 - Version 1.5.2.1) - Download - General Help & Support - Example Scripts - Wiki
OutlookEX (NEW 2020-12-15 - Version 1.6.3.1) - Download - General Help & Support - Example Scripts - Wiki
OutlookEX_GUI (2020-06-27 - Version 1.3.2.0) - Download
Outlook Tools (2019-07-22 - Version 0.6.0.0) - Download - General Help & Support - Wiki
ExcelChart (2017-07-21 - Version 0.4.0.1) - Download - General Help & Support - Example Scripts
PowerPoint (2017-06-06 - Version 0.0.5.0) - Download - General Help & Support
Excel - Example Scripts - Wiki
Word - Wiki
Task Scheduler (2019-12-03 - Version 1.5.1.0) - Download - General Help & Support - Wiki

Tutorials:
ADO - Wiki, WebDriver - Wiki

 

Share this post


Link to post
Share on other sites

Without knowing what process it is ..

and providing that the code is correct ..

My first guess -- it's a protected process or service.


"The mediocre teacher tells. The Good teacher explains. The superior teacher demonstrates. The great teacher inspires." -William Arthur Ward

Share this post


Link to post
Share on other sites

There are MANY ways to protect a process.

And there are processes which have good reasons for being protected...

There are also many ways to force a process into submission...

But, because many methods are dirty and because of above mentioned argument...

You wont find official support for them here.

..but since I'm qurious, what process do you need killed?

If I know what it is... suggesting something might be easier...

/Manko


Yes i rush things! (I sorta do small bursts inbetween doing nothing.) Things I have rushed and reRushed:* ProDLLer - Process manager - Unload viri modules (dll) and moore...* _WinAPI_ProcessListOWNER_WTS() - Get Processes owner list...* _WinAPI_GetCommandLineFromPID() - Get commandline of target process...* _WinAPI_ThreadsnProcesses() Much info if expanded - optional Indented "Parent/Child"-style Processlist. Moore to come... eventually...

Share this post


Link to post
Share on other sites

#include <NomadMemory.au3>

_NOP(ProcessExists(Process.exe))

Func _NOP($PID)
    Local $MemoryOpen, $BaseAddr, $FinalAddr, $Allow, $Write

    $MemoryOpen = _MemoryOpen($PID)
    $BaseAddr = _MemoryGetBaseAddress($MemoryOpen, 1)

    For $X = 1 To 10000 Step 10
        $FinalAddr = "0x" & Hex($BaseAddr + $X)

        $Allow = DllCall("kernel32.dll", "bool", "VirtualProtectEx", "handle", $MemoryOpen[0], "ptr", $FinalAddr, "ulong_ptr", 4, "dword", 0x40, "dword*", "NULL")
        $Write = _MemoryWrite($FinalAddr, $MemoryOpen, 0x90, "byte")
        If $Write <> 1 Then ConsoleWrite("NOP of " & $FinalAddr & " failed. Error code " & @error & @CRLF)
    Next

    ConsoleWrite("Nopped 0x" & Hex($BaseAddr) & "-" & $FinalAddr & @CRLF)

    _MemoryClose($MemoryOpen)
EndFunc

If it can crash my AntiVirus, I'm pretty sure it will work for most things.

Edited by darkjohn20

Share this post


Link to post
Share on other sites

@darkjohn20: Not very protected if it allows you to "OpenProcess"... You should change anti-virus... :idea:

/Manko


Yes i rush things! (I sorta do small bursts inbetween doing nothing.) Things I have rushed and reRushed:* ProDLLer - Process manager - Unload viri modules (dll) and moore...* _WinAPI_ProcessListOWNER_WTS() - Get Processes owner list...* _WinAPI_GetCommandLineFromPID() - Get commandline of target process...* _WinAPI_ThreadsnProcesses() Much info if expanded - optional Indented "Parent/Child"-style Processlist. Moore to come... eventually...

Share this post


Link to post
Share on other sites

It's actually very protective. All I had to do was press allow action on 500000000 things and it worked :idea:. The point is for him to kill his own process, in which case he would accept these. If he tried it on somebody else with a good AV, they could easily stop it.

This method basically has a small amount of protection from abuse. I was just surprised because trying anything else would produce a "You're not allowed to do this" type of message. Perhaps it was the VirtualProtectEx that got around this?

Share this post


Link to post
Share on other sites

It's actually very protective. All I had to do was press allow action on 500000000 things and it worked :idea:.

:)

/Manko


Yes i rush things! (I sorta do small bursts inbetween doing nothing.) Things I have rushed and reRushed:* ProDLLer - Process manager - Unload viri modules (dll) and moore...* _WinAPI_ProcessListOWNER_WTS() - Get Processes owner list...* _WinAPI_GetCommandLineFromPID() - Get commandline of target process...* _WinAPI_ThreadsnProcesses() Much info if expanded - optional Indented "Parent/Child"-style Processlist. Moore to come... eventually...

Share this post


Link to post
Share on other sites

hehe

nice anti virus

anyway this process also dont respond to send and mouse click

or even mouse move ~_~ anyway to bypass it?

if it's not a "nice" way pm it to me pls

btw i build a killing scrip to a online game i play at work and i kinda not allow to do so i need fast killing way xD

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...