CLI tool for running Playbooks
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

73 lines
2.7 KiB

1 year ago
  1. Process Hacker is a powerful free and open source process viewer.
  2. == Getting started ==
  3. Simply run ProcessHacker.exe to start Process Hacker. There are two
  4. versions, 32-bit (x86) and 64-bit (x64). If you are not sure which
  5. version to use, open Control Panel > System and check the "System
  6. type". You cannot run the 32-bit version of Process Hacker on a
  7. 64-bit system and expect it to work correctly, unlike other programs.
  8. == System requirements ==
  9. Windows XP SP2 or higher, 32-bit or 64-bit.
  10. == Settings ==
  11. If you are running Process Hacker from a USB drive, you may want to
  12. save Process Hacker's settings there as well. To do this, create a
  13. blank file named "ProcessHacker.exe.settings.xml" in the same
  14. directory as ProcessHacker.exe. You can do this using Windows Explorer:
  15. 1. Make sure "Hide extensions for known file types" is unticked in
  16. Tools > Folder options > View.
  17. 2. Right-click in the folder and choose New > Text Document.
  18. 3. Rename the file to ProcessHacker.exe.settings.xml (delete the ".txt"
  19. extension).
  20. == Plugins ==
  21. Plugins can be configured from Hacker > Plugins.
  22. If you experience any crashes involving plugins, make sure they
  23. are up to date.
  24. The ExtendedTools plugin is only available for Windows Vista and
  25. above. Disk and Network information provided by this plugin is
  26. only available when running Process Hacker with administrative
  27. rights.
  28. == KProcessHacker ==
  29. NOTE: The driver has been very generously signed by the
  30. ReactOS Foundation (http://www.reactos.org).
  31. Process Hacker uses a kernel-mode driver, KProcessHacker, to
  32. assist with certain functionality. This includes:
  33. * Bypassing security software and rootkits in limited ways
  34. * More powerful process and thread termination (*)
  35. * Setting DEP status of processes
  36. * Capturing kernel-mode stack traces
  37. * More efficiently enumerating process handles
  38. * Retrieving names for file handles
  39. * Retrieving names for EtwRegistration objects
  40. * Setting handle attributes
  41. The feature(s) marked with an asterisk (*) are NOT available on 64-bit
  42. versions of Windows.
  43. Certain features such as modifying process protection are disabled
  44. in the released driver binary due to legal reasons. You can enable
  45. them by building KProcessHacker with the "dirty" configuration.
  46. Note that by default, KProcessHacker only allows connections from
  47. processes with SeDebugPrivilege. To allow Process Hacker to show details
  48. for all processes when it is not running as administrator:
  49. 1. In Registry Editor, navigate to:
  50. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\KProcessHacker2
  51. 2. Under this key, create a key named Parameters if it does not exist.
  52. 3. Create a DWORD value named SecurityLevel and set it to 0.
  53. 4. Restart the KProcessHacker2 service (sc stop KProcessHacker2,
  54. sc start KProcessHacker2).