Docs · P0

Windows × Ghidra wiring

Bring-your-own Ghidra on Windows for read-oriented native PE/DLL work — env vars, doctor, and cold-start reality.

Bring your own installs

REA does not download Ghidra or a JDK. Install a supported Ghidra build and a 64-bit JDK outside REA, then export absolute paths before setup:

setx GHIDRA_INSTALL_DIR C:\path\to\ghidra_PUBLIC
setx JAVA_HOME C:\path\to\jdk-21
setx REA_ANALYSIS_PROVIDER ghidra

Open a new shell so the variables are visible, then:

npx -y rea-agents@latest doctor --provider ghidra --json
npx rea-agents@latest setup

What Windows P0 is (and is not)

Oriented toward approved native x86-64 PE applications and related DLL inspection via headless Ghidra.
Read-oriented tool surface: inventory, decompilation, references — not a GUI puppet that mutates your Ghidra project arbitrarily.
Historical docs once disagreed about Windows native authority gates; if doctor says the provider is disabled, upgrade and re-read current upstream Windows Ghidra notes before assuming the product lied.

Cold start & timeouts

First headless launch can exceed short default timeouts (community reports of multi-minute JVM/Ghidra bring-up). If the first query fails with a provider timeout while later retries work, lengthen startup patience (see large-binary guide) rather than thrashing install paths.

Authorized targets only

Point Ghidra+REA at binaries you own, build, or have written permission to analyze.