• Mojave@lemmy.world
    link
    fedilink
    arrow-up
    34
    ·
    2 months ago

    Clicking end task in windows task manager has definitely let the hanging task live in its non-responsive state for multiple hours before.

    • Björn Tantau@swg-empire.de
      link
      fedilink
      arrow-up
      16
      arrow-down
      1
      ·
      2 months ago

      Been a while since I’ve been on Windows but I distinctly remember some button to kill a task without waiting. Maybe they removed it to make Windows soooo much more user friendly.

      • Rev3rze@feddit.nl
        link
        fedilink
        arrow-up
        18
        ·
        2 months ago

        Off the top of my head: right click the task and hit end process. That has literally never failed me. Back in windows XP it might sometimes not actually kill the process but then there was always the “kill process tree” button to fall back on.

        • Zoot@reddthat.com
          link
          fedilink
          arrow-up
          7
          ·
          2 months ago

          Yep, typically “Kill Process Tree” was like the nuke from orbit. You’ll likely destroy any unsaved data, but it works nice when steam has 12 processes running at once.

      • blind3rdeye@lemm.ee
        link
        fedilink
        arrow-up
        7
        ·
        2 months ago

        The normal Windows task manager’s ‘end task’ button just politely asks the app to close - but then later will tell the user if the app is unresponsive, and offer to brutally murder it instead.

        There is also the sysinternals Process Monitor, which is basically ‘expert’ version of the task manager. Procmon does allow you to just kill a task outright.