PS C:\WDT> .\Invoke-WindowsDiagnostics.ps1

SYSTEM READY

See what Windows is doing.
Change nothing.

A read-only PowerShell diagnostics toolkit with a responsive terminal interface, local reports, Privacy Mode and no telemetry.

Run diagnostics Usage guide Example report
MODE
READ-ONLY
UPLOAD
NONE
RUNTIME
PS 5.1 / 7+
PLATFORM
WIN 10 / 11
WDT / INTERACTIVE DASHBOARDUTF-8
Windows Diagnostics Toolkit Wide terminal dashboard with selected diagnostics and Privacy Mode enabled
[OK] Responsive layout · keyboard-first controls · current selection preserved on resize
[x] READ-ONLY BY DESIGN [x] NO INSTALLER [x] NO TELEMETRY [x] LOCAL TXT + MARKDOWN [x] PRIVACY MODE

01 / INTERFACE

Built around the terminal,
not bolted onto it.

Run the entry point without switches. Select the diagnostic areas, choose report options and review the result without leaving the TUI.

STEP 01SELECT

Choose checks

Toggle ten diagnostic areas, Privacy Mode, Markdown export and the output directory.

↑↓navigateSpacetoggle

STEP 02RUN

Collect locally

Only reviewed diagnostic operations are launched. The toolkit does not apply fixes or reconfigure Windows.

AallRrecommendedEnterrun

STEP 03REVIEW

Read findings

See elapsed time, report paths and aggregated WARN and ERROR counts before opening the report.

EntermenuEscexit

WDT / COLLECTION RESULTCOMPLETE
Windows Diagnostics Toolkit completion screen showing warnings, errors and elapsed time
[WARN] A warning means the observed state deserves review. It does not mean collection failed.

02 / QUICK START

Clone. Run. Diagnose.

No installer and no third-party PowerShell modules. The built-in Windows PowerShell 5.1 is enough.

  • [OK] Interactive TUI opens by default
  • [OK] Recommended checks preselected
  • [OK] Privacy Mode enabled by default
PowerShell
PS> git clone https://github.com/0x0bug/windows-diagnostics-toolkit.git
PS> cd windows-diagnostics-toolkit
PS> .\Invoke-WindowsDiagnostics.ps1
READYExecution policy unchanged

03 / DIAGNOSTICS

One report.
Ten diagnostic modules.

Ten diagnostic modules are grouped here into six troubleshooting areas. Collect broad context or run only the module related to the problem; the findings summary appears before the detailed sections.

DIAGNOSTICS10 MODULES / 6 AREAS
[x]System + performanceOS, CPU, memory, GPU, uptime, pagefile, top processes↗ [x]Security postureDefender, Firewall, Secure Boot, TPM, BitLocker↗ [x]Network contextAdapters, DNS, DHCP, routes, gateways, proxy, reachability↗ [x]Crashes + Event LogsApplication errors, hangs, BugCheck events, dump metadata↗ [x]Disk healthPhysical disk state, volumes and free-space warnings↗ [x]Time + Windows UpdateW32Time, update services, recent updates, reboot indicators↗
UP/DOWN NAVIGATESPACE TOGGLEENTER SELECTESC EXIT

04 / PRIVACY

Local first.
Share only what you choose.

Reports stay in the selected output directory. Privacy Mode replaces common identifying values with stable per-report tokens.

  • [x]Read-onlyNo registry, service, firewall, DNS or system configuration changes.
  • [x]No telemetryNo upload, remote collection or tracking endpoint.
  • [x]AuditableSource code, validation policy and tests are public.
PRIVACY MODEENABLED
ComputerName : <HOST-1>
UserName     : <USER-1>
IPv4Address  : <IP-1>
MacAddress   : <MAC-1>
DeviceId     : <ID-1>

[!] Process, application and dump-file names remain visible because they are diagnostically useful.

05 / GUIDES

Start from the symptom.

Each guide explains which module to run, what evidence it collects, how to interpret the output and what the toolkit intentionally leaves untouched.

01Collect a support reportRedacted TXT and Markdown outputOPEN ↗ 02Application keeps crashingErrors, hangs, BugCheck and dumpsOPEN ↗ 03Windows uses too much memoryRAM, pagefile and top processesOPEN ↗ 04Update may need a restartUpdates, services and reboot indicatorsOPEN ↗ 05Unexpected route or proxyRoutes, gateways, DNS and proxy contextOPEN ↗
Browse all troubleshooting guides

06 / FAQ

Expected behavior,
without guesswork.

Does the toolkit change Windows settings?

No. Production diagnostics collect and report state without applying automatic fixes, changing services, editing the registry or reconfiguring the network.

Why do I see the ASCII logo?

Automatic mode uses Unicode only for compatible interactive UTF-8 output. OEM encodings such as cp866, redirected output and unsupported hosts receive the printable ASCII fallback.

Does resizing restart diagnostics?

No. Resize events redraw the current interface and preserve the current selection. A running diagnostic operation is not restarted.

Where are reports stored?

Reports are written to the selected output directory. Nothing is uploaded automatically.

Does WARN mean the tool failed?

No. WARN describes observed state that deserves review. A module execution failure is reported separately with a non-zero exit code.

READY / RUN

Diagnose Windows before changing Windows.

Open source, dependency-free and designed to produce evidence you can actually share.

Quick start View source Report a problem