PC Hardware Health Report
A tiny readable script reads what the browser can't — drive health, battery wear, crash history — and this page explains it.
1 — Get a report
The script reads your machine locallyThe collector is a plain script, not a program — open it in any editor and read exactly what it does before running it. It writes one file, runthetests-report.json, and makes no network requests: nothing about your machine is sent anywhere, including to this site.
Windows 10 / 11
Download rtt-collect.ps1Right-click the downloaded file and pick the PowerShell entry in the menu. Windows asks once and proceeds; the report appears next to the file.
Read the script firstmacOS
Download rtt-collect-mac.zipUnpack the zip and open rtt-collect.command. macOS refuses the first try because the script is unsigned: choose Done, then System Settings → Privacy & Security → Open Anyway. The report lands beside the file.
Read the script first2 — Read it here
Analysed in your browser — never uploadedHow this reads your output
A browser cannot read SMART data, battery wear, installed memory or your crash history — that is a security boundary, and every page on this site that runs into it says so. This tool is the honest way past it: a small collector script you download, read, and open yourself. It is deliberately a script rather than a program, because a script can be inspected in any editor before it is ever opened — you can see for yourself that it makes no network requests and changes nothing, rather than trusting a compiled binary. It asks the operating system for the figures that actually decide repair-or-replace questions: each drive's self-reported health, wear and temperature where the platform releases them, installed memory, battery capacity against its design capacity, and the last month of unexpected shutdowns from the event log. It writes everything into one JSON file beside itself and stops. Drop that file back here and this page reads it — in your browser, like every other tool on this site — and turns the figures into a verdict with the reasoning shown, ready to export as a dated PDF for a ticket, a warranty claim or a resale listing.
What the results mean
- Drive health
- The drive's own self-assessment (SMART). Healthy is the normal state; Warning or Unhealthy from a drive is the one result on this page that should change your plans today — back up first, diagnose second.
- Unexpected shutdowns
- Windows Kernel-Power event 41: the machine lost power without shutting down cleanly. Crashes, hard power-offs and failing supplies all land here, and more than a couple in a month is a pattern, not noise.
- Battery capacity
- What the battery can hold now as a share of what it held new. Below about 80%, runtime falls off quickly and manufacturers themselves call it due for replacement.
- Elevated / administrator
- Some Windows counters — drive wear, temperature, power-on hours — are only readable from an administrator window. Run without one, the report simply marks them unreadable rather than guessing.
Common problems and fixes
- Why a script and not a proper app?
- Trust, mostly. An app asks you to trust opaque compiled code; a script is its own source. Open it in Notepad or TextEdit before using it — the whole point is that you can check the claim that nothing leaves your machine, rather than take our word for it.
- Windows blocks the script when I open it
- Right-click the file and pick the PowerShell entry in the menu — Windows shows a one-time prompt and proceeds. If it still refuses, open the file's Properties and tick Unblock, which clears the downloaded-file flag, then try the right-click again. No setting is permanently changed either way.
- macOS says it could not verify the file
- Expected for an unsigned script, and the allowance is deliberate on Apple's part — it is just two steps now. Choose Done in the warning, then open System Settings, go to Privacy & Security, scroll to the line naming rtt-collect.command and press Open Anyway; macOS asks you to confirm once and it opens normally after that. On macOS 14 and earlier the shortcut still works: right-click the file and choose Open.
- Drive wear shows as not readable
- On Windows those counters are only released to an elevated process, so the standard double-click run cannot see them — the report marks them unreadable rather than guessing. The drive's own Healthy or Unhealthy verdict is collected either way, and that is the figure that decides anything urgent. On macOS no user-space tool can read wear at all.
- The report is for a different machine than the one I'm on
- That is the normal case for helping family or assessing a second-hand purchase: generate it there, send yourself the JSON, and use the paste box here. The analysis is identical — the page never cares which machine it runs on.
Frequently asked questions
Is any of this sent to your servers?
No, twice over. The collector script makes no network requests at all — it reads system counters and writes a local file, and it is short enough to verify that in a minute. And this page parses the file in your browser, like every tool on this site: the report never leaves your machine unless you yourself attach it to a ticket or an email.
Why would I run this instead of a tool like HWiNFO or Speccy?
Those are excellent, deeper tools — and if you already use them, this site's interpreters read their exports directly. This collector is for the other situation: you want the repair-deciding numbers in one pass, explained in plain language, from something you can audit before running, without installing anything.
Can it tell me if my PC is about to die?
It can tell you what the machine itself is admitting to: a drive reporting ill health, a battery below its replacement threshold, a month of unexpected shutdowns. Those are the strongest predictors a user-space tool can read. What nothing can promise is the absence of surprises — a drive can fail without ever warning, which is why the report's real output is a backup decision.
What do I do with the report file afterwards?
Keep it or delete it — it is a plain text file on your machine. Dated reports are worth keeping: one from when the machine was healthy is the baseline that makes next year's report meaningful, and one generated while a fault is present is exactly what a repair ticket or warranty claim wants attached.
Put this on your own site
Free to embed, no attribution required beyond the source link the frame carries itself. It runs entirely in your visitor's browser, sets no cookies and loads no third-party script.
<iframe src="https://runthetests.com/embed/pc-hardware-report/" width="100%" height="720" style="border:1px solid #e5e5e5;border-radius:8px" title="PC Hardware Health Report" loading="lazy"></iframe>
Preview it at https://runthetests.com/embed/pc-hardware-report/. Embedded pages are marked noindex, so yours stays the canonical copy — not this one.
More in Repair
- Device Info / Spec ReportEverything this browser reports about your device — and what it cannot see.
- Used Device Buying ChecklistThe fifteen checks worth doing before handing over money for a used device.
- Repair vs Replace CalculatorCompare a repair quote with a replacement on cost per remaining year.