Create a Windows diagnostic report for tech support
Generate one local TXT and Markdown report for Windows 10 or Windows 11, review the findings summary and share only the redacted evidence relevant to the support request.
1. Create the combined Windows report
Open PowerShell in the toolkit directory and run:
pwsh -NoProfile -File .\Invoke-WindowsDiagnostics.ps1 `
-All -PrivacyMode -ExportMarkdownFor Windows PowerShell 5.1:
powershell.exe -NoProfile -ExecutionPolicy Bypass `
-File .\Invoke-WindowsDiagnostics.ps1 `
-All -PrivacyMode -ExportMarkdownThe one-run execution-policy bypass applies only to that PowerShell process. It does not change the machine-wide execution policy.
2. Understand what the report contains
Findings summary
Actionable conditions are grouped as OK, WARN or ERROR before the detailed diagnostic output.
System and performance
Windows build, hardware summary, uptime, memory, CPU snapshot, pagefile and top processes.
Security and updates
Defender, Firewall, Secure Boot, TPM, BitLocker, installed updates and reboot indicators.
Network and time
Adapters, DNS, DHCP, routes, proxy state, reachability, W32Time source and synchronization context.
Disk, services and tasks
Physical disk health, free space, automatic services not running and optional startup or scheduled-task context.
Crashes and Event Logs
Recent application failures, hangs, BugCheck events, dump metadata and critical or error events.
3. Read the report efficiently
- Start with the overall status and findings summary.
- Match each warning or error to the symptom and time when the problem occurred.
- Open only the detailed module sections connected to the support request.
- Do not treat every WARN item as a required fix; some states are expected on particular systems.
4. Review privacy before sharing
Privacy Mode replaces common computer names, user names, profile paths, IP and MAC addresses, SIDs, GUIDs and device identifiers with stable per-report tokens. It is intended to make a support report safer to share, not to guarantee complete anonymity.
- Search the report for your real user name and computer name.
- Review application names, dump names, Event Log messages, DNS suffixes and proxy hosts.
- Remove credentials, access tokens, private server names and organization-specific details.
- Share only the relevant excerpt when the entire report is unnecessary.
Invoke-WindowsDiagnostics.ps1.5. Attach useful evidence to the support request
A useful report is accompanied by a short description of the symptom. Include:
- the Windows version and build;
- the exact command used;
- the time the problem happened;
- steps that reproduce the problem;
- the relevant redacted findings and detailed section;
- the toolkit version, release or commit SHA.
What the toolkit does not do
- It does not upload the report or send it to a support provider.
- It does not automatically fix Windows.
- It does not replace a debugger, malware scanner or vendor-specific diagnostic package.
- It does not guarantee that every third-party application or hardware fault will appear in the report.