Generate and Share Support Bundle
Collect AutoDoctor reports, logs, telemetry, and metadata for troubleshooting and support handoff without losing execution context.
Categories:
Who This Is For
- Users sharing diagnostic evidence with support.
- Operators collecting reproducible evidence from endpoints.
Files to Collect
reports/AutoDoctor_Report.htmlreports/AutoDoctor_Report.jsonlogs/autodoctor.loglogs/autodoctor_api.log(if service/API used)server/latest_run.json- Latest
telemetry/Telemetry_*.json
Optional for deep triage:
db/autodoctor.db
PowerShell Example (Installed Path)
$root = "C:\ProgramData\AutoDoctor"
$out = Join-Path $env:TEMP ("AutoDoctor_Support_" + (Get-Date -Format "yyyyMMdd_HHmmss"))
New-Item -ItemType Directory -Path $out -Force | Out-Null
Copy-Item "$root\reports\AutoDoctor_Report.html" $out -ErrorAction SilentlyContinue
Copy-Item "$root\reports\AutoDoctor_Report.json" $out -ErrorAction SilentlyContinue
Copy-Item "$root\logs\autodoctor.log" $out -ErrorAction SilentlyContinue
Copy-Item "$root\logs\autodoctor_api.log" $out -ErrorAction SilentlyContinue
Copy-Item "$root\server\latest_run.json" $out -ErrorAction SilentlyContinue
Copy-Item "$root\telemetry\Telemetry_*.json" $out -ErrorAction SilentlyContinue
Compress-Archive -Path "$out\*" -DestinationPath "$out.zip" -Force
$out + ".zip"
Privacy and Redaction Guidance
Before sharing externally:
- Review hostnames and usernames in telemetry/JSON files
- Remove sensitive local paths if required by policy
- Share DB only when deeper SQL analysis is required
Next Steps
- See Troubleshooting Playbook
- For API-specific issues, see Service Startup Issues