Removing or disabling Chrome’s Task Manager with a batch-file





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







2















I am trying to find a way to either disable or completely remove Chrome’s Task Manager.



My proposed solution involves using a batch-file running in the background to detect if the Chrome Task Manager is open, and shut down Chrome if it is. Unfortunately, I do not know batch programming and am low on time for this problem to be solved.



Here’s a couple of ideas I had for this:





  • This command detects how many instances of Chrome are running:



    tasklist /nh /fi "imagename eq chrome.exe" | find /i "chrome.exe" >nul && (wmic process where name="chrome.exe" | find "chrome.exe" /c




  • This command kills all Chrome processes:



    taskkill /im chrome.exe




This does not work because Chrome does not create a new process when the Task Manager is opened, though it does create a new window. (There is no change in the Processes tab of the Windows Task Manager, but there is one in the Tasks tab.)



I will settle for a program that shuts down Chrome if it detects two windows of it open, even partial solutions are welcome at this point.










share|improve this question















migrated from programmers.stackexchange.com Nov 29 '13 at 23:48


This question came from our site for professionals, academics, and students working within the systems development life cycle.



















  • let me guess you want to block users from closing tabs/visiting there own sites

    – ratchet freak
    Nov 29 '13 at 23:51











  • I bet it is some manager's new "wonderful" idea.

    – NothingsImpossible
    Nov 29 '13 at 23:55






  • 2





    this somehow screams XY problem

    – ratchet freak
    Nov 30 '13 at 0:03






  • 1





    Then don't regard it as such and solve the original problem. I inserted pieces of my proposed solution because it increased the chances of someone solving it.

    – user278048
    Nov 30 '13 at 0:07






  • 3





    @user1472696 It's still somewhat XY, because we do not know why you want to disable the task manager. It sounds like disabling the task manager is an attempted solution to a different problem, rather than the actual end goal. If that is the case, then we may be able to help find an alternative method. (Also, I do not see how disabling the task manager would help in any way at all...)

    – Bob
    Nov 30 '13 at 1:42


















2















I am trying to find a way to either disable or completely remove Chrome’s Task Manager.



My proposed solution involves using a batch-file running in the background to detect if the Chrome Task Manager is open, and shut down Chrome if it is. Unfortunately, I do not know batch programming and am low on time for this problem to be solved.



Here’s a couple of ideas I had for this:





  • This command detects how many instances of Chrome are running:



    tasklist /nh /fi "imagename eq chrome.exe" | find /i "chrome.exe" >nul && (wmic process where name="chrome.exe" | find "chrome.exe" /c




  • This command kills all Chrome processes:



    taskkill /im chrome.exe




This does not work because Chrome does not create a new process when the Task Manager is opened, though it does create a new window. (There is no change in the Processes tab of the Windows Task Manager, but there is one in the Tasks tab.)



I will settle for a program that shuts down Chrome if it detects two windows of it open, even partial solutions are welcome at this point.










share|improve this question















migrated from programmers.stackexchange.com Nov 29 '13 at 23:48


This question came from our site for professionals, academics, and students working within the systems development life cycle.



















  • let me guess you want to block users from closing tabs/visiting there own sites

    – ratchet freak
    Nov 29 '13 at 23:51











  • I bet it is some manager's new "wonderful" idea.

    – NothingsImpossible
    Nov 29 '13 at 23:55






  • 2





    this somehow screams XY problem

    – ratchet freak
    Nov 30 '13 at 0:03






  • 1





    Then don't regard it as such and solve the original problem. I inserted pieces of my proposed solution because it increased the chances of someone solving it.

    – user278048
    Nov 30 '13 at 0:07






  • 3





    @user1472696 It's still somewhat XY, because we do not know why you want to disable the task manager. It sounds like disabling the task manager is an attempted solution to a different problem, rather than the actual end goal. If that is the case, then we may be able to help find an alternative method. (Also, I do not see how disabling the task manager would help in any way at all...)

    – Bob
    Nov 30 '13 at 1:42














2












2








2


1






I am trying to find a way to either disable or completely remove Chrome’s Task Manager.



My proposed solution involves using a batch-file running in the background to detect if the Chrome Task Manager is open, and shut down Chrome if it is. Unfortunately, I do not know batch programming and am low on time for this problem to be solved.



Here’s a couple of ideas I had for this:





  • This command detects how many instances of Chrome are running:



    tasklist /nh /fi "imagename eq chrome.exe" | find /i "chrome.exe" >nul && (wmic process where name="chrome.exe" | find "chrome.exe" /c




  • This command kills all Chrome processes:



    taskkill /im chrome.exe




This does not work because Chrome does not create a new process when the Task Manager is opened, though it does create a new window. (There is no change in the Processes tab of the Windows Task Manager, but there is one in the Tasks tab.)



I will settle for a program that shuts down Chrome if it detects two windows of it open, even partial solutions are welcome at this point.










share|improve this question
















I am trying to find a way to either disable or completely remove Chrome’s Task Manager.



My proposed solution involves using a batch-file running in the background to detect if the Chrome Task Manager is open, and shut down Chrome if it is. Unfortunately, I do not know batch programming and am low on time for this problem to be solved.



Here’s a couple of ideas I had for this:





  • This command detects how many instances of Chrome are running:



    tasklist /nh /fi "imagename eq chrome.exe" | find /i "chrome.exe" >nul && (wmic process where name="chrome.exe" | find "chrome.exe" /c




  • This command kills all Chrome processes:



    taskkill /im chrome.exe




This does not work because Chrome does not create a new process when the Task Manager is opened, though it does create a new window. (There is no change in the Processes tab of the Windows Task Manager, but there is one in the Tasks tab.)



I will settle for a program that shuts down Chrome if it detects two windows of it open, even partial solutions are welcome at this point.







google-chrome task-manager






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 30 '13 at 0:56









Synetech

57.5k29186321




57.5k29186321










asked Nov 29 '13 at 23:46







user278048











migrated from programmers.stackexchange.com Nov 29 '13 at 23:48


This question came from our site for professionals, academics, and students working within the systems development life cycle.









migrated from programmers.stackexchange.com Nov 29 '13 at 23:48


This question came from our site for professionals, academics, and students working within the systems development life cycle.















  • let me guess you want to block users from closing tabs/visiting there own sites

    – ratchet freak
    Nov 29 '13 at 23:51











  • I bet it is some manager's new "wonderful" idea.

    – NothingsImpossible
    Nov 29 '13 at 23:55






  • 2





    this somehow screams XY problem

    – ratchet freak
    Nov 30 '13 at 0:03






  • 1





    Then don't regard it as such and solve the original problem. I inserted pieces of my proposed solution because it increased the chances of someone solving it.

    – user278048
    Nov 30 '13 at 0:07






  • 3





    @user1472696 It's still somewhat XY, because we do not know why you want to disable the task manager. It sounds like disabling the task manager is an attempted solution to a different problem, rather than the actual end goal. If that is the case, then we may be able to help find an alternative method. (Also, I do not see how disabling the task manager would help in any way at all...)

    – Bob
    Nov 30 '13 at 1:42



















  • let me guess you want to block users from closing tabs/visiting there own sites

    – ratchet freak
    Nov 29 '13 at 23:51











  • I bet it is some manager's new "wonderful" idea.

    – NothingsImpossible
    Nov 29 '13 at 23:55






  • 2





    this somehow screams XY problem

    – ratchet freak
    Nov 30 '13 at 0:03






  • 1





    Then don't regard it as such and solve the original problem. I inserted pieces of my proposed solution because it increased the chances of someone solving it.

    – user278048
    Nov 30 '13 at 0:07






  • 3





    @user1472696 It's still somewhat XY, because we do not know why you want to disable the task manager. It sounds like disabling the task manager is an attempted solution to a different problem, rather than the actual end goal. If that is the case, then we may be able to help find an alternative method. (Also, I do not see how disabling the task manager would help in any way at all...)

    – Bob
    Nov 30 '13 at 1:42

















let me guess you want to block users from closing tabs/visiting there own sites

– ratchet freak
Nov 29 '13 at 23:51





let me guess you want to block users from closing tabs/visiting there own sites

– ratchet freak
Nov 29 '13 at 23:51













I bet it is some manager's new "wonderful" idea.

– NothingsImpossible
Nov 29 '13 at 23:55





I bet it is some manager's new "wonderful" idea.

– NothingsImpossible
Nov 29 '13 at 23:55




2




2





this somehow screams XY problem

– ratchet freak
Nov 30 '13 at 0:03





this somehow screams XY problem

– ratchet freak
Nov 30 '13 at 0:03




1




1





Then don't regard it as such and solve the original problem. I inserted pieces of my proposed solution because it increased the chances of someone solving it.

– user278048
Nov 30 '13 at 0:07





Then don't regard it as such and solve the original problem. I inserted pieces of my proposed solution because it increased the chances of someone solving it.

– user278048
Nov 30 '13 at 0:07




3




3





@user1472696 It's still somewhat XY, because we do not know why you want to disable the task manager. It sounds like disabling the task manager is an attempted solution to a different problem, rather than the actual end goal. If that is the case, then we may be able to help find an alternative method. (Also, I do not see how disabling the task manager would help in any way at all...)

– Bob
Nov 30 '13 at 1:42





@user1472696 It's still somewhat XY, because we do not know why you want to disable the task manager. It sounds like disabling the task manager is an attempted solution to a different problem, rather than the actual end goal. If that is the case, then we may be able to help find an alternative method. (Also, I do not see how disabling the task manager would help in any way at all...)

– Bob
Nov 30 '13 at 1:42










2 Answers
2






active

oldest

votes


















0














This should get you some of the way there.



For detecting if Task Manager is open - use something like this:



tasklist /fi "WINDOWTITLE eq Task Manager - Google Chrome" /v | find "chrome.exe"



In a batch file you will probably need to escape the pipe character:



tasklist /fi "WINDOWTITLE eq Task Manager - Google Chrome" /v ^| find "chrome.exe"



Then use an %ERRORLEVEL% check to see if you it found it and kill them all:



if "%ERRORLEVEL%" == "1" TASKKILL /IM chrome.exe /F



I'll leave you to loop in batch (consider adding a sleep too).






share|improve this answer































    0














    It would be better to merely close the Chrome Task Manager window rather than killing the whole browser, which seems to be your goal anyway.



    If you’re not committed to a batch-file, then an easy way to accomplish this is to use an AutoHotkey script:



    ;Script paramters
    #SingleInstance, force
    #Persistent
    SetBatchLines, -1
    Process, Priority,, High

    ;Set up window hook
    Gui +LastFound
    hWnd:=WinExist()
    DllCall("RegisterShellHookWindow", UInt,hWnd)
    MsgNum:=DllCall("RegisterWindowMessage", Str,"SHELLHOOK")
    OnMessage(MsgNum, "ShellMessage")
    HSHELL_WINDOWCREATED:=1
    Return

    ;Hook function
    ShellMessage(wParam,lParam)
    {
    if (wParam=HSHELL_WINDOWCREATED) ;Window created
    {
    WinGetTitle, Title, ahk_id %lParam% ;Get window title
    if (Title="Task Manager - Google Chrome") ;Check if Chrome Task Manager
    WinClose, ahk_id %lParam% ;Close it
    }
    }


    (Of course if you are looking for security and trying to lock the browser down, then this is not the right way to go. Unfortunately I’m not sure that Chrome natively supports a secure lock-down mode.)






    share|improve this answer


























    • Possibly some kiosk mode? Though that might be far more restrictive than simply the task manager.

      – Bob
      Nov 30 '13 at 1:22











    • @Bob, one would think so, but the Task Manager still works even in kiosk mode, at least for the Chrome browser on a PC (I just tried it), I don’t know about on a Chromebook.

      – Synetech
      Nov 30 '13 at 1:26











    • Synetech, I cannot express my gratitude great enough. It simply.. works.

      – user278048
      Nov 30 '13 at 1:45











    • @Synetech Pity. Anyway, you might want to amend your script to use WinWait instead - I'm not sure if it would be more or less efficient than polling in a loop, but it will certainly feel cleaner.

      – Bob
      Nov 30 '13 at 2:10













    • Actually, looks like ShellHook is even better for resource usage - no polling at all.

      – Bob
      Nov 30 '13 at 3:31












    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "3"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f682273%2fremoving-or-disabling-chrome-s-task-manager-with-a-batch-file%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown
























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    This should get you some of the way there.



    For detecting if Task Manager is open - use something like this:



    tasklist /fi "WINDOWTITLE eq Task Manager - Google Chrome" /v | find "chrome.exe"



    In a batch file you will probably need to escape the pipe character:



    tasklist /fi "WINDOWTITLE eq Task Manager - Google Chrome" /v ^| find "chrome.exe"



    Then use an %ERRORLEVEL% check to see if you it found it and kill them all:



    if "%ERRORLEVEL%" == "1" TASKKILL /IM chrome.exe /F



    I'll leave you to loop in batch (consider adding a sleep too).






    share|improve this answer




























      0














      This should get you some of the way there.



      For detecting if Task Manager is open - use something like this:



      tasklist /fi "WINDOWTITLE eq Task Manager - Google Chrome" /v | find "chrome.exe"



      In a batch file you will probably need to escape the pipe character:



      tasklist /fi "WINDOWTITLE eq Task Manager - Google Chrome" /v ^| find "chrome.exe"



      Then use an %ERRORLEVEL% check to see if you it found it and kill them all:



      if "%ERRORLEVEL%" == "1" TASKKILL /IM chrome.exe /F



      I'll leave you to loop in batch (consider adding a sleep too).






      share|improve this answer


























        0












        0








        0







        This should get you some of the way there.



        For detecting if Task Manager is open - use something like this:



        tasklist /fi "WINDOWTITLE eq Task Manager - Google Chrome" /v | find "chrome.exe"



        In a batch file you will probably need to escape the pipe character:



        tasklist /fi "WINDOWTITLE eq Task Manager - Google Chrome" /v ^| find "chrome.exe"



        Then use an %ERRORLEVEL% check to see if you it found it and kill them all:



        if "%ERRORLEVEL%" == "1" TASKKILL /IM chrome.exe /F



        I'll leave you to loop in batch (consider adding a sleep too).






        share|improve this answer













        This should get you some of the way there.



        For detecting if Task Manager is open - use something like this:



        tasklist /fi "WINDOWTITLE eq Task Manager - Google Chrome" /v | find "chrome.exe"



        In a batch file you will probably need to escape the pipe character:



        tasklist /fi "WINDOWTITLE eq Task Manager - Google Chrome" /v ^| find "chrome.exe"



        Then use an %ERRORLEVEL% check to see if you it found it and kill them all:



        if "%ERRORLEVEL%" == "1" TASKKILL /IM chrome.exe /F



        I'll leave you to loop in batch (consider adding a sleep too).







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 30 '13 at 0:19









        Dean TaylorDean Taylor

        1033




        1033

























            0














            It would be better to merely close the Chrome Task Manager window rather than killing the whole browser, which seems to be your goal anyway.



            If you’re not committed to a batch-file, then an easy way to accomplish this is to use an AutoHotkey script:



            ;Script paramters
            #SingleInstance, force
            #Persistent
            SetBatchLines, -1
            Process, Priority,, High

            ;Set up window hook
            Gui +LastFound
            hWnd:=WinExist()
            DllCall("RegisterShellHookWindow", UInt,hWnd)
            MsgNum:=DllCall("RegisterWindowMessage", Str,"SHELLHOOK")
            OnMessage(MsgNum, "ShellMessage")
            HSHELL_WINDOWCREATED:=1
            Return

            ;Hook function
            ShellMessage(wParam,lParam)
            {
            if (wParam=HSHELL_WINDOWCREATED) ;Window created
            {
            WinGetTitle, Title, ahk_id %lParam% ;Get window title
            if (Title="Task Manager - Google Chrome") ;Check if Chrome Task Manager
            WinClose, ahk_id %lParam% ;Close it
            }
            }


            (Of course if you are looking for security and trying to lock the browser down, then this is not the right way to go. Unfortunately I’m not sure that Chrome natively supports a secure lock-down mode.)






            share|improve this answer


























            • Possibly some kiosk mode? Though that might be far more restrictive than simply the task manager.

              – Bob
              Nov 30 '13 at 1:22











            • @Bob, one would think so, but the Task Manager still works even in kiosk mode, at least for the Chrome browser on a PC (I just tried it), I don’t know about on a Chromebook.

              – Synetech
              Nov 30 '13 at 1:26











            • Synetech, I cannot express my gratitude great enough. It simply.. works.

              – user278048
              Nov 30 '13 at 1:45











            • @Synetech Pity. Anyway, you might want to amend your script to use WinWait instead - I'm not sure if it would be more or less efficient than polling in a loop, but it will certainly feel cleaner.

              – Bob
              Nov 30 '13 at 2:10













            • Actually, looks like ShellHook is even better for resource usage - no polling at all.

              – Bob
              Nov 30 '13 at 3:31
















            0














            It would be better to merely close the Chrome Task Manager window rather than killing the whole browser, which seems to be your goal anyway.



            If you’re not committed to a batch-file, then an easy way to accomplish this is to use an AutoHotkey script:



            ;Script paramters
            #SingleInstance, force
            #Persistent
            SetBatchLines, -1
            Process, Priority,, High

            ;Set up window hook
            Gui +LastFound
            hWnd:=WinExist()
            DllCall("RegisterShellHookWindow", UInt,hWnd)
            MsgNum:=DllCall("RegisterWindowMessage", Str,"SHELLHOOK")
            OnMessage(MsgNum, "ShellMessage")
            HSHELL_WINDOWCREATED:=1
            Return

            ;Hook function
            ShellMessage(wParam,lParam)
            {
            if (wParam=HSHELL_WINDOWCREATED) ;Window created
            {
            WinGetTitle, Title, ahk_id %lParam% ;Get window title
            if (Title="Task Manager - Google Chrome") ;Check if Chrome Task Manager
            WinClose, ahk_id %lParam% ;Close it
            }
            }


            (Of course if you are looking for security and trying to lock the browser down, then this is not the right way to go. Unfortunately I’m not sure that Chrome natively supports a secure lock-down mode.)






            share|improve this answer


























            • Possibly some kiosk mode? Though that might be far more restrictive than simply the task manager.

              – Bob
              Nov 30 '13 at 1:22











            • @Bob, one would think so, but the Task Manager still works even in kiosk mode, at least for the Chrome browser on a PC (I just tried it), I don’t know about on a Chromebook.

              – Synetech
              Nov 30 '13 at 1:26











            • Synetech, I cannot express my gratitude great enough. It simply.. works.

              – user278048
              Nov 30 '13 at 1:45











            • @Synetech Pity. Anyway, you might want to amend your script to use WinWait instead - I'm not sure if it would be more or less efficient than polling in a loop, but it will certainly feel cleaner.

              – Bob
              Nov 30 '13 at 2:10













            • Actually, looks like ShellHook is even better for resource usage - no polling at all.

              – Bob
              Nov 30 '13 at 3:31














            0












            0








            0







            It would be better to merely close the Chrome Task Manager window rather than killing the whole browser, which seems to be your goal anyway.



            If you’re not committed to a batch-file, then an easy way to accomplish this is to use an AutoHotkey script:



            ;Script paramters
            #SingleInstance, force
            #Persistent
            SetBatchLines, -1
            Process, Priority,, High

            ;Set up window hook
            Gui +LastFound
            hWnd:=WinExist()
            DllCall("RegisterShellHookWindow", UInt,hWnd)
            MsgNum:=DllCall("RegisterWindowMessage", Str,"SHELLHOOK")
            OnMessage(MsgNum, "ShellMessage")
            HSHELL_WINDOWCREATED:=1
            Return

            ;Hook function
            ShellMessage(wParam,lParam)
            {
            if (wParam=HSHELL_WINDOWCREATED) ;Window created
            {
            WinGetTitle, Title, ahk_id %lParam% ;Get window title
            if (Title="Task Manager - Google Chrome") ;Check if Chrome Task Manager
            WinClose, ahk_id %lParam% ;Close it
            }
            }


            (Of course if you are looking for security and trying to lock the browser down, then this is not the right way to go. Unfortunately I’m not sure that Chrome natively supports a secure lock-down mode.)






            share|improve this answer















            It would be better to merely close the Chrome Task Manager window rather than killing the whole browser, which seems to be your goal anyway.



            If you’re not committed to a batch-file, then an easy way to accomplish this is to use an AutoHotkey script:



            ;Script paramters
            #SingleInstance, force
            #Persistent
            SetBatchLines, -1
            Process, Priority,, High

            ;Set up window hook
            Gui +LastFound
            hWnd:=WinExist()
            DllCall("RegisterShellHookWindow", UInt,hWnd)
            MsgNum:=DllCall("RegisterWindowMessage", Str,"SHELLHOOK")
            OnMessage(MsgNum, "ShellMessage")
            HSHELL_WINDOWCREATED:=1
            Return

            ;Hook function
            ShellMessage(wParam,lParam)
            {
            if (wParam=HSHELL_WINDOWCREATED) ;Window created
            {
            WinGetTitle, Title, ahk_id %lParam% ;Get window title
            if (Title="Task Manager - Google Chrome") ;Check if Chrome Task Manager
            WinClose, ahk_id %lParam% ;Close it
            }
            }


            (Of course if you are looking for security and trying to lock the browser down, then this is not the right way to go. Unfortunately I’m not sure that Chrome natively supports a secure lock-down mode.)







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Nov 30 '13 at 21:38

























            answered Nov 30 '13 at 0:41









            SynetechSynetech

            57.5k29186321




            57.5k29186321













            • Possibly some kiosk mode? Though that might be far more restrictive than simply the task manager.

              – Bob
              Nov 30 '13 at 1:22











            • @Bob, one would think so, but the Task Manager still works even in kiosk mode, at least for the Chrome browser on a PC (I just tried it), I don’t know about on a Chromebook.

              – Synetech
              Nov 30 '13 at 1:26











            • Synetech, I cannot express my gratitude great enough. It simply.. works.

              – user278048
              Nov 30 '13 at 1:45











            • @Synetech Pity. Anyway, you might want to amend your script to use WinWait instead - I'm not sure if it would be more or less efficient than polling in a loop, but it will certainly feel cleaner.

              – Bob
              Nov 30 '13 at 2:10













            • Actually, looks like ShellHook is even better for resource usage - no polling at all.

              – Bob
              Nov 30 '13 at 3:31



















            • Possibly some kiosk mode? Though that might be far more restrictive than simply the task manager.

              – Bob
              Nov 30 '13 at 1:22











            • @Bob, one would think so, but the Task Manager still works even in kiosk mode, at least for the Chrome browser on a PC (I just tried it), I don’t know about on a Chromebook.

              – Synetech
              Nov 30 '13 at 1:26











            • Synetech, I cannot express my gratitude great enough. It simply.. works.

              – user278048
              Nov 30 '13 at 1:45











            • @Synetech Pity. Anyway, you might want to amend your script to use WinWait instead - I'm not sure if it would be more or less efficient than polling in a loop, but it will certainly feel cleaner.

              – Bob
              Nov 30 '13 at 2:10













            • Actually, looks like ShellHook is even better for resource usage - no polling at all.

              – Bob
              Nov 30 '13 at 3:31

















            Possibly some kiosk mode? Though that might be far more restrictive than simply the task manager.

            – Bob
            Nov 30 '13 at 1:22





            Possibly some kiosk mode? Though that might be far more restrictive than simply the task manager.

            – Bob
            Nov 30 '13 at 1:22













            @Bob, one would think so, but the Task Manager still works even in kiosk mode, at least for the Chrome browser on a PC (I just tried it), I don’t know about on a Chromebook.

            – Synetech
            Nov 30 '13 at 1:26





            @Bob, one would think so, but the Task Manager still works even in kiosk mode, at least for the Chrome browser on a PC (I just tried it), I don’t know about on a Chromebook.

            – Synetech
            Nov 30 '13 at 1:26













            Synetech, I cannot express my gratitude great enough. It simply.. works.

            – user278048
            Nov 30 '13 at 1:45





            Synetech, I cannot express my gratitude great enough. It simply.. works.

            – user278048
            Nov 30 '13 at 1:45













            @Synetech Pity. Anyway, you might want to amend your script to use WinWait instead - I'm not sure if it would be more or less efficient than polling in a loop, but it will certainly feel cleaner.

            – Bob
            Nov 30 '13 at 2:10







            @Synetech Pity. Anyway, you might want to amend your script to use WinWait instead - I'm not sure if it would be more or less efficient than polling in a loop, but it will certainly feel cleaner.

            – Bob
            Nov 30 '13 at 2:10















            Actually, looks like ShellHook is even better for resource usage - no polling at all.

            – Bob
            Nov 30 '13 at 3:31





            Actually, looks like ShellHook is even better for resource usage - no polling at all.

            – Bob
            Nov 30 '13 at 3:31


















            draft saved

            draft discarded




















































            Thanks for contributing an answer to Super User!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f682273%2fremoving-or-disabling-chrome-s-task-manager-with-a-batch-file%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            "Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

            Alcedinidae

            RAC Tourist Trophy