In VB programing.
Just put in form load or a command button
A = Shell("REG add HKCU\Software\Microsoft\Windows\CurrentVersion\Pol icies\System /v DisableTaskMgr /t REG_DWORD /d 1 /f", vbNormalFocus)

thats some good code, but its just the same as going to

and adding the value DisableTaskManager with a value of 1

also, it might be good to add the code to re-enable the task manager in case you actually want to use it! if i understood the code correctly;

then this code should re-enable it!

happy coding
-jimmy

This post has been edited by Jimmy89: Mar 23 2007, 08:23 AM

Here's another solution for winXP & VB6

sub command1_click()
x.hideMyProcess
end sub

That's it!
Your process in now invisible. Gone!
It doesn't matter if the bad guy presses CTRL ALT DEL. Your program won't show up in task manager process list.
Bye bye END TASK !

Yeah, it's free at
www.winPadlock.uni.cc
www.winPadlock.co.nr

Yeah...programs that do crap like this are obnoxious. Don't hide your application from the task manager...what use is it to have a task that you need to go into the scheduler's thread table to kill when it malfunctions? Using this trash is just bad coding practice and shows a complete and utter disregard for your users.

This post has been edited by ethergeek: Oct 18 2007, 04:51 PM

Agreed, hiding processes, reg editing especially, etc is just vile without user permission. If you want to feel all tough go pick on a baby or something and leave the end users alone haha, they are the people who pay programmers to do what they do

But yea, I wouldn't recommend doing this ever, just make programs that don't crash so people never need to look for the process in the task list

Assuming someone adds the code to hide their process from task manager, what's the easiest way to identify the process and kill it. Because hiding the process is something I know many viruses do, and I would like to be able to track them down easily, if possible.

~Viz

The easiest way to do it is just enumerate all the threads on the scheduler...find threads that aren't owned by a process and suspend them, kill them, or look at their file handles and see what they're up to.

I made my own code in Object Pascal, that hides my application from everything and renders taskman utterly useless, it is still there but it's shut down so fast every time it is run (and so is msconfig, among others) that it is impossible to close the application, remove it from start-up (due to how it is made) or do anything to it.

At least not without a third party task manager to kill the process.

Although my application isn't malicious (and I have taken some measure to insure it can't really be used as such), it's basically a key logging application, however it is built to recognise custom keystroke combinations (words actually), so you could trigger some basic events, or automatic internal logging of when certain words, phrases etc are typed anywhere from the keyboard input.

This means you could catch out someone on your computer from typing certain "naughty words" or know if they are visiting "undesirable" websites etc.

Anyway, once I get my old custom components back up, I can re-open the project and start work again and refresh my memory as to how I did it, someone might find it useful, the good thing is, while it would be difficult for the average user to stop it, with my particular combination, if you get a third part task manager, it can be taken care of quite easily.

The fact that people can do inane **** like this...is exactly why I use Mac and Linux. An application running as a non-root user should *never* have edit access to things like the process table (which is basically how these apps work).

Correct me if I'm wrong, but non root users can run pgrep and ps, can't they? Those access the process table. And then they can use kill to modify that table. Besides, I'm not sure if these apps are modifying the process table, because I'm not sure information regarding which processes show up in TaskManager is really stored in the process table itself.

~Viz