Scan the affected PC
Save a local report with the Windows companion.
A clear path to repair.
Scan the affected Windows computer with the companion, then import its report here for explained findings and a practical repair plan. The website never changes your computer’s settings.
Before you download: the safe starting point
Development release: the Windows companion is unsigned and repair testing is pending. Do not bypass security warnings. This website cannot scan another PC through a normal USB cable or confirm every hardware fault.
- Protect your data. Back up important files and keep recovery keys private. Note the exact model, symptom and recent changes.
- Use the affected Windows PC. Read the setup guide and inspect the included source before considering the development companion. If it cannot boot, use official manufacturer guidance.
- Collect and transfer evidence. Export the companion JSON report. Transfer it privately to the device where you opened this page.
- Import, review and retest. Select the JSON report below. Review unknown checks, choose an appropriate next step and repeat the original failing task after any approved repair.
On a phone? Review brand guides here; the Windows companion must run on the affected computer. A sample report demonstrates the interface only and is not evidence about your device.
Import your report
Review available evidence and unverified checks.
Choose a next step
Read the guide, confirm changes and rescan.
Diagnostic report
Waiting for a report. The site has not scanned any device.
Reports provide evidence only; repair instructions and support links come from this site’s built-in catalogue. Invalid files leave existing results unchanged. Reports are processed in memory on this device. Refresh or clear to discard them. A second report from the same model can be compared as a follow-up; confirm it is the same physical computer.
Practise report import without a Windows PC
These files are synthetic examples, not a scan of your device. They contain no private data and do not run repair tools. Imported test results replace the report displayed in this tab; reload to clear them.
- Download the sample JSON and select it under Import a Genius diagnostic JSON report.
- Expect the device to say Synthetic training device, a sample storage warning, and unmeasured checks to say Not verified.
- Download and import the invalid test file. Expect an error while the previous sample findings remain unchanged.
- Use Clear imported reports or reload to remove the sample from memory. Do not use sample findings to make real repair decisions.
Brand-specific repair guides
20 brand groups and 19 symptom workflows. Select a brand, verify the exact model and review its diagnosis, repair options and official resources. Common Windows procedures are shared across Windows brands; OEM tools and service procedures vary by model.
Selecting a tab does not detect, connect to or authorize changes to a device. OEM tools are external resources, not integrated repair executors. Unlisted brands use the Custom / other brands tab. Not an authorized-service or all-fault coverage claim.
Windows repair tools
Scan → review evidence → confirm one action → repeat the original failing task. Run the companion on the affected Windows PC. These tools do not repair physical hardware or access another laptop through a normal USB cable.
Unsigned development release · Windows PowerShell and .NET Framework 4.x · executable and complete source included. Repairs have not been validated across hardware models. Settings shortcuts open Windows controls; they do not perform repairs automatically.
Verify the result.
After any action, read its output and retest. A successful process exit alone does not establish that the problem is fixed. This checklist is manual and resets when you leave the page.
Website checks and remaining release requirements
Browser learning tools and report-import workflows can be tested without a Windows repair PC. Passing those checks does not validate a Windows repair or certify accessibility.
- Website: retest navigation, learning progress, downloads, error feedback and backups after changes.
- Accessibility: verify actual TalkBack and VoiceOver announcements, focus order, forms, media controls and enlarged text on real phones.
- Windows companion: development release. Controlled repair, rollback and hardware testing still require a disposable Windows PC or VM.
- Commercial release: publisher signing, security review, supported-device evidence, privacy and payment processes still need review before release. Do not treat this checklist as approval.
OpenAI and customer AI access must remain closed during the current testing phase. This section does not change provider settings or enable access.
Open the screen-reader test guide →Help and repair limits
Can I diagnose any laptop by connecting a USB cable?
No. A normal USB connection does not expose another PC’s operating system, logs, memory, motherboard or sensors. Run the companion on the affected Windows PC. You may transfer its report using a USB drive or supported file-transfer connection. Direct remote diagnostics would require an explicitly authorized companion, compatible transport and secure pairing on the target computer.
What if the computer cannot start?
This Windows companion cannot scan a computer that cannot boot into its supported operating system. Use the manufacturer’s preboot diagnostics, a qualified technician, or a suitable recovery environment. Protect valuable data before repair attempts.
Will it find and repair every hardware problem?
No. Software can report only the evidence its sensors and operating system provide. RAM integrity tests, physical inspection and component-level diagnosis need additional tools. The report includes unknown checks so missing evidence is visible.
What happens after a repair?
Read the actual repair tool output, repeat the original failing task and generate a fresh report. A warning disappearing means that reported condition was no longer observed. It does not prove every component is healthy or that an intermittent issue is resolved.
Technical basis: Windows storage telemetry, System File Checker, and DISM image repair.