Our take
- Activity
- 19
- Community
- 4
- Issues
- 21
- Pull requests
- no data
+1 stars in the last 30 days
- Fewer contributors than 91% of the projects we track
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
689Forks
31Change since Nov 17, 2026: 0 stars·0 forks
Overview
QDoctor is a Windows emergency-response and anti-rootkit (ARK) tool for investigating potentially compromised hosts. It brings system inventory and low-level inspection into one utility, helping responders locate suspicious processes, persistence, drivers, hooks, and other system activity.
Its structured export and import workflow makes it useful beyond live inspection: analysts can collect host data for later review or feed exported records into their own threat-analysis process. It is aimed at Windows incident responders and security professionals, rather than general-purpose system administration.
Key Features
- Inspect processes, threads, modules, memory, handles, and kernel callbacks, with options to pause or terminate processes and threads.
- Review kernel components and structures, including drivers, callbacks, hooks, and system tables.
- Find common persistence locations such as registry startup items, scheduled tasks, services, drivers, and WMI.
- View per-process IPv4 and IPv6 TCP and UDP connections.
- Export structured information from tabs, including relevant file hashes, and import exports from other machines.
- Inspect system logs, installed software, environment variables, shared folders, and files, with a file manager that can forcibly delete files.
- Run as a single executable that supports both x86 and x86_64 architectures.
Use Cases
- Incident responders triaging a suspected Windows infection can inspect persistence, running processes, kernel components, and network connections on the affected host.
- Security teams can collect structured host data for offline investigation when immediate analysis on the machine is impractical.
- Analysts can import collected data from another machine to compare findings or review a host without inspecting it live.
- Teams with threat-intelligence resources can use exported records as input to a custom automated analysis workflow.
Getting Started
Download the executable from the latest release link. See the README for supported Windows versions, usage notes, and the Chinese documentation.
Alternatives
- systeminformer: System Informer focuses on live system monitoring, process inspection, and debugging, rather than QDoctor's incident-response data collection and offline review.
- PYAS: PYAS emphasizes ongoing threat detection, scanning, and remediation, while QDoctor focuses on examining host activity and exchanging investigation data.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| QDoctor | not specified | not specified | 688 | Not checked yet |
| systeminformer | C | MIT | 16.2k | Active |
| PYAS | YARA | – | 565 | Active |
Considerations
- QDoctor operates at a low level, and its documentation warns that use can cause a blue screen or data loss. Save data before running it.
- The README lists Windows 7 through Windows 11 and several Windows Server releases as supported, with architecture support varying by version. Some newer Windows updates may not yet be adapted.
- On Windows 7 and Windows 8, the required SHA-2 signing support patch or disabled driver-signature verification may be needed for initialization. Memory integrity can also prevent driver loading.
- Security products may flag the executable, including the publisher's own software. Verify its signature before considering any allowlisting.
- The tool is free for personal use within its authorization period. Commercial use requires authorization, so review the repository's terms before using it in a commercial workflow.
Found this useful?
Share it with someone who would like QDoctor.