Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. C#
  4. disable task manager when called....

disable task manager when called....

Scheduled Pinned Locked Moved C#
help
29 Posts 12 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D Daniel Grunwald

    The KISS way is to open the group policy options and click on 'disable task manager'.

    M Offline
    M Offline
    Mubeen asim
    wrote on last edited by
    #21

    nice what does the KISS way tel about doing the same gpedit.msc way from c# code.. hope its simple....!

    1 Reply Last reply
    0
    • M Mubeen asim

      thans but u are telling to block harmful actions not the programs... but i think it is easy to block the taskman rather than allowing it to open and then block it from ending my applications process..... if such code exists or if i could hide my applications process from the taskman like virus do then also it would be more complex code generation... so the KISS way.... block the taskmgr.exe....

      P Offline
      P Offline
      Pete OHanlon
      wrote on last edited by
      #22

      All right. If you're so bloody clever figure out the code for yourself. You've been told by several experts that the way to do this is to use policies to cope with it, and yet you persist in arguing. Fine - write the code, post it up and then see how long it is before somebody finds a way to work round it (btw - somebody could rename tastmanager.exe and launch that so any approach you had to block it by name would fail).

      "WPF has many lovers. It's a veritable porn star!" - Josh Smith

      My blog | My articles | MoXAML PowerToys

      M 2 Replies Last reply
      0
      • M Mubeen asim

        i am dosing this work as a graduation project.... and i do have knowkedge that task manaver can be accessed sinply by renaming the System.IO.File.Open("renamed_taskmagr.exe".... but i should try some thing to help me in not ending my program by the task man at the start up by the student who should login and provide his information...

        C Offline
        C Offline
        Christian Graus
        wrote on last edited by
        #23

        max.4u wrote:

        but i should try some thing to help me in not ending my program by the task man at the start up by the student who should login and provide his information...

        If you want to do *something*, write a service that checks if the application has closed, and re-opens it. That might make your teacher happy, but if he's not a moron, he'll know that whatever you do, was a waste of time, it's not the place to try to enforce what you want. Overall, you are wasting a lot of time on something really stupid. If your teacher did not ask you to do this, then stop wasting your time, as you've been told over and over, you can't do it this way, not in a foolproof way.

        Christian Graus Driven to the arms of OSX by Vista.

        1 Reply Last reply
        0
        • P Pete OHanlon

          All right. If you're so bloody clever figure out the code for yourself. You've been told by several experts that the way to do this is to use policies to cope with it, and yet you persist in arguing. Fine - write the code, post it up and then see how long it is before somebody finds a way to work round it (btw - somebody could rename tastmanager.exe and launch that so any approach you had to block it by name would fail).

          "WPF has many lovers. It's a veritable porn star!" - Josh Smith

          My blog | My articles | MoXAML PowerToys

          M Offline
          M Offline
          Mubeen asim
          wrote on last edited by
          #24

          hey man you are on fire... why dont you just help by telling how to call the policy manager from the code and disable the taskmanager.....

          C 1 Reply Last reply
          0
          • P Pete OHanlon

            All right. If you're so bloody clever figure out the code for yourself. You've been told by several experts that the way to do this is to use policies to cope with it, and yet you persist in arguing. Fine - write the code, post it up and then see how long it is before somebody finds a way to work round it (btw - somebody could rename tastmanager.exe and launch that so any approach you had to block it by name would fail).

            "WPF has many lovers. It's a veritable porn star!" - Josh Smith

            My blog | My articles | MoXAML PowerToys

            M Offline
            M Offline
            Mubeen asim
            wrote on last edited by
            #25

            hello.. am extreamly sorry for whats happening here... i was only making new ways of doing the thing.... sorry if i have hurted any one.... once more...

            N 1 Reply Last reply
            0
            • M Mubeen asim

              hello.. am extreamly sorry for whats happening here... i was only making new ways of doing the thing.... sorry if i have hurted any one.... once more...

              N Offline
              N Offline
              Najmal
              wrote on last edited by
              #26

              you are right Max..... Sometimes taskmanager must be disabled for security purpose...

              M 1 Reply Last reply
              0
              • M Mubeen asim

                hey man you are on fire... why dont you just help by telling how to call the policy manager from the code and disable the taskmanager.....

                C Offline
                C Offline
                Colin Angus Mackay
                wrote on last edited by
                #27

                max.4u wrote:

                why dont you just help by telling how to call the policy manager from the code and disable the taskmanager.....

                I can see that you were told 11 minutes before you posted this message. See this post[^]

                * Developer Day Scotland 2 - Free community conference * The Blog of Colin Angus Mackay


                Vogon Building and Loan advise that your planet is at risk if you do not keep up repayments on any mortgage secured upon it. Please remember that the force of gravity can go up as well as down.

                1 Reply Last reply
                0
                • N Najmal

                  you are right Max..... Sometimes taskmanager must be disabled for security purpose...

                  M Offline
                  M Offline
                  Mubeen asim
                  wrote on last edited by
                  #28

                  thans...

                  1 Reply Last reply
                  0
                  • M Mubeen asim

                    hellu... i got this codes from microsoft to capture when a key is pressed... i have modified to disable the task manager being called but it dowsnt work.... sohuld i have to tweak the code more.. plz help me.. protected override bool ProcessCmdKey(ref Message msg, Keys keyData) { const int WM_KEYDOWN = 0x100; const int WM_SYSKEYDOWN = 0x104; if ((msg.Msg == WM_KEYDOWN) || (msg.Msg == WM_SYSKEYDOWN)) { switch (keyData) { //looking for the task manager combination case Keys.Control|Keys.Alt|Keys.Delete: MessageBox.Show("task manager called."); break; } } return base.ProcessCmdKey(ref msg, keyData); }

                    L Offline
                    L Offline
                    Lost User
                    wrote on last edited by
                    #29

                    Imagine that one of the processes on the computer goes banana's. I know that it's unusual, since Windows is such a stable platform, but for arguments sake, let's imagine that there is a virus-checker on your system and that it's gone into an infinite loop, eating away 100% cpu time. ..and the virus-scanner starts when Windows start, rendering your machine useless. That's why we have a task-manager :)

                    I are troll :)

                    1 Reply Last reply
                    0
                    Reply
                    • Reply as topic
                    Log in to reply
                    • Oldest to Newest
                    • Newest to Oldest
                    • Most Votes


                    • Login

                    • Don't have an account? Register

                    • Login or register to search.
                    • First post
                      Last post
                    0
                    • Categories
                    • Recent
                    • Tags
                    • Popular
                    • World
                    • Users
                    • Groups