hermes-windows-services.yaml 2.6 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243
  1. name: hermes-windows-services
  2. repo: https://github.com/Yicheng-Mark/hermes-windows-plugins
  3. sha: 1d1027f864aa3c1388eac08e6eee84fb862fbe91
  4. subdir: windows-services
  5. description: >-
  6. Answer "what runs as a service on this machine, why did one fail, and what does it depend on"
  7. on Windows: win_service_table lists every service with its state (Running, Stopped, Paused),
  8. its start mode (Auto, Manual, Disabled, with the delayed flag folded in as "Auto, delayed"),
  9. the pid it runs under, the account and binary it runs as, the dependency edges both ways, and
  10. what its exit code means - 1077 is one that has not tried to start since the last boot, 1053
  11. one that did not answer in time, 1075 one whose dependency failed first, 2 one whose binary
  12. is gone. win_service_detail takes one service and gives what Windows does when it fails (the
  13. FailureActions blob decoded: restart the service, restart the computer, run a command, after
  14. how many seconds, and when the count resets), whether the registered binary is still on
  15. disk, and the Service Control Manager's own event-log record behind the failure - 7000
  16. failed to start, 7009 a start request that timed out, 7024 a service-specific error, 7031 an
  17. unexpected end, 7045 an install. Use it for what died after the last update, for finding
  18. what an uninstalled program left registered, and for the dependency order before a restart.
  19. Read-only: nothing is started, stopped, reconfigured or deleted. The listing comes from one
  20. Get-CimInstance Win32_Service call because its property names and enum values do not change
  21. with the display language while sc.exe localizes both; dependencies and failure actions are
  22. read from the registry, because CIM's DependOnService property is never populated and the
  23. failure policy exists nowhere in CIM at all. The plugin declares no Python dependencies;
  24. there is no network call and no file write. Windows only. Disclosure - the tools report
  25. service names, display names, command lines, logon accounts and the event-log history to the
  26. model, and those reveal what the person has installed, what runs as their machine's system
  27. accounts, and the paths under C:\Program Files and C:\Users\<name>; treat the output like a
  28. Services window opened on their machine.
  29. maintainer: Yicheng-Mark
  30. tier: community
  31. category: tools
  32. requires_hermes: ">=0.21.4"
  33. docs_url: https://github.com/Yicheng-Mark/hermes-windows-plugins/tree/main/windows-services
  34. version: "0.1.0"
  35. platforms:
  36. - windows
  37. capabilities:
  38. provides_tools:
  39. - win_service_table
  40. - win_service_detail
  41. provides_hooks: []
  42. provides_middleware: []
  43. requires_env: []