How solve this problem (Critical Process)

[soupetomate]

Hi i am making a software who can kill apps.
At the moment i have sucess listed all .EXE and kill .EXE i want.


But some EXE crash and do a BSOD when it's killed.

I have read over internet and i have see some examples.

http://www.codingvision.net/tips-and-tr ... -if-killed

The goal would be to code a little procedure, so i can disable protection of process then kill.

I have already my kill procedure working it's just about this.

Thanks

[eJan]

Edit: removed <.

[Josh]

Jooooooo, I like it. First post and want kill protected processes

[soupetomate]

:/

I'm still suck at this to translate it right in PureBasic.

[Thorium]

Plain and simple: Dont do it!
Critical processes are critical for a reason and the bsod is there for a reason.
There is no reason to kill a critical process.

[IdeasVacuum]

That is nothing that can't already be done using Task Manager, which is delivered as part of Windows. If you have a really good reason for building an app that does the same as Task Manager, tell us.

[normeus]

soupetomate might be creating a malware deleting program? Benefit of doubt.
I am just posting because I followed his link and I saw the picture of The new windows 8 BSD.
I only have seen this once and I didnt know what it was. I am not saying windows 8 is stable because I had to reinstall it 2 times when it wouldnt even boot. What I am saying is what a stupid looking BSD.
The time I saw it, I figured it was some freeware I was running and I decided the guy who created it was making fun of Mac's sad mac and opted on a sad frog because at that font size it looks like a frog.

@soupetomate
It is dificult when you compile a program and symantec right away decides it is a virus because you are using PureBasic. Thats why you'll get not help unless you state a clear motive for stopping running programs. No one wants PB compiled programs to be black listed.

Norm.

[JHPJHP]

See: Services, Stuff, and Shellhook
- Stuff/MoreStuff/SetCriticalFlag.pb

---------------------------------------------------------------------------------

This script doesn't terminate a critical process it marks the current process as critical, causing a BSOD (Blue Screen of Death) when it ends.
- administrative privileges are required: Request Administrator mode for Windows Vista and above

soupetomate wants to accomplish the opposite of the BSOD script by removing the critical flag from a process so that it can be terminated safely:

The goal would be to code a little procedure, so i can disable protection of process then kill.

---------------------------------------------------------------------------------

I rewrote the script to be a little more intuitive.
- tested on Windows 7 and Windows 8.1

If the script is executed with the current settings:
- warns you that the BSOD may occur if you proceed
- notifies you that the critical flag is present
- notifies you that the critical flag is not present
-- this will avoid the BSOD as the process is no longer marked as critical

Code: Select all

SetCriticalFlag(#Null, #True)
SetCriticalFlag(#Null, #False)

If the first parameter is #Null the script uses the current process, otherwise it expects a PID (process ID).

Second parameter options: #True, #False or Excluded (-1).
- #True: sets the critical flag
- #False: removes the critical flag
- Excluded (-1): checks if the critical flag is present

NB*: With the current settings, removing the second call to the Procedure: SetCriticalFlag will cause the BSOD to occur when the process ends.

[blueznl]

Well, we're all suspicious people in here so let me ask a question: why would someone want to remove that flag? It's there for a reason...

... Then again, I have also some code that terminates other processes. For example in Unirun I sometimes kill an emulator which doesn't support a closewindow / endprocess message. But at least I can give a good reason