thor-troubleshooting

Diagnose stuck, slow, or aborting THOR scans with prioritized evidence collection.

12|2|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/Nextron-Labs/thor-skill --skill thor-troubleshooting-nextron-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: thor-troubleshooting
Source: https://github.com/Nextron-Labs/thor-skill/tree/main/thor-troubleshooting
Command: npx skills add https://github.com/Nextron-Labs/thor-skill --skill thor-troubleshooting-nextron-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

THOR troubleshooting helps identify and resolve why THOR scans are stuck, slow, failing to start, or stopping early, and provides actionable next steps.

Core Features & Use Cases

  • Structured diagnostic workflow for stuck scans, with prioritized likely causes (AV/EDR interference, resources, timeouts)
  • Evidence-guided remediation steps and recommended diagnostics (thor-util diagnostics, log snippets, etc.)
  • Optional helper script for quick environment checks (scripts/quick-env-check.sh)

Quick Start

Run a quick environment check and generate diagnostics to begin triaging a THOR scan issue.

Frequently Asked Questions about thor-troubleshooting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does my THOR scan get stuck or run very slowly on my system?

THOR scans often get stuck or run slowly due to AV/EDR interference, resource bottlenecks, or timeout misconfigurations. A structured diagnostic workflow evaluates these prioritized likely causes to isolate the issue.

How do I diagnose a THOR scan that is aborting or failing to start?

Diagnosing an aborting THOR scan requires evidence-guided remediation steps, collecting log snippets, current process states, and running thor-util diagnostics to identify the failure point.

Can I troubleshoot THOR scan freezes on both Windows and Linux?

Yes, the THOR troubleshooting workflow applies to lab and live environments across Windows, Linux, and macOS to resolve scan freezes, long runtimes, and missing output.

What is the best way to collect forensic diagnostics for a failing THOR scan?

The best way to collect forensic diagnostics is running the quick-env-check helper script alongside thor-util diagnostics to gather prioritized evidence for safe, repeatable resolution.

How do I stop AV or EDR from interrupting my THOR scans?

To stop AV/EDR process-interruption during THOR scans, follow the evidence-guided remediation steps provided after the diagnostic workflow identifies interference as the root cause.