HW Blackbox 1.1.0

The hardware's own errors and the drives' health, Windows notifications, times with their time zone, and Home
Assistant as an add-on. The settings and the history carry over.

New: hardware errors

The CPU, the memory and PCI Express report errors to Windows (WHEA). A corrected one did no harm, but it's the first
sign of a part or a setting on the edge (an overclock, XMP / EXPO, a loose card or riser); a fatal one is a blue
screen. HW Blackbox now records them, and the drives' own errors too: bad blocks, reads and writes retried, a drive's
controller reset, a damaged file system.

• Diagnose has a Hardware errors check: how many, from which part, and what to do about each (the CPU, the
  memory, a PCIe link).
• Events has a Hardware group.
• A power-off report lists the hardware's error records around it, and names a blue screen's stop code
  (0x124 WHEA_UNCORRECTABLE_ERROR: the hardware reported an error it couldn't correct...).
• A board that reports a corrected error every few seconds doesn't flood the records: each kind is written 30 times
  an hour at most, and the next one says how many were left out.

New: the drives' health

Once an hour, each drive's health as Windows judges it, its temperature, how worn it is, and the errors it has
counted (Windows' storage counters: Get-StorageReliabilityCounter).

• Diagnose has a Drives check: a drive Windows calls unhealthy, errors it couldn't correct (and whether they
  grew this month), worn out, running hot, or the error records of the last week, each with what to do.
• The Overview's Disks card shows each drive, and a new Hardware card sums it up.
• A drive Windows calls unhealthy is a problem: "back it up now".

New: notifications

A Windows notification, so you hear of it without opening the page: the PC went off without shutting down, an app
crashed, the hardware or a drive reported an error, or something stopped working. Clicking one opens the page where
it's explained.

• Each signed-in user gets their own, and chooses which on the new Settings tab, with Send a test
  notification.
• They're rationed: one of a kind every 10 minutes, six an hour. A problem is announced once it has lasted a minute.
  Nothing from before the install is announced.
• They show as HW Blackbox (the installer registers the name and its icon with Windows).

Home Assistant: an add-on, on the Settings tab

Most people don't run Home Assistant, so it's no longer on the Overview. On Settings → Home Assistant,
Set up… asks Windows for an admin, then a window asks for the address and a long-lived token, tries them, and only
then keeps them. Turn off… stops it and offers to delete the token. (From a prompt, as admin:
python -m hwblackbox homeassistant, --off to turn it off.) An existing setup carries on as it was. The status
gains last_hardware_error, last_drive_error and drives.

Times with their time zone

Every time in the logs and records now carries its offset from UTC (2026-11-10T18:23:02-05:00). Until now, when
daylight saving ended the repeated hour was written twice the same way, and the charts drew it over itself. Older
logs are read in order to tell the two apart. The status's own lines (the last incident, the last power loss) keep
their form, so a Home Assistant automation that watches them doesn't fire because of the update.

Smaller

• Crashes are named by their program: "python.exe (QGIS 3.44.15), in gdal313.dll" rather than "python.exe": a
  python.exe can be anyone's.
• An extra Explorer quitting isn't an incident. A program that opens a folder or starts another program through
  explorer.exe makes an Explorer that hands the job to the taskbar's and quits with exit code 1 (seen when the Ollama
  and LocalCast updaters started their programs). It's on the Events tab, not an incident. The taskbar's own Explorer
  ending, and any crash, still are.
• The logs are packed once they're two days old (.csv.gz, about a tenth of the size) and read as before: six
  months of history in tens of megabytes rather than hundreds.
• A row cut off by a power loss stays on a line of its own: the next row isn't glued onto it.
• Accessibility: dark controls, more contrast on the counts and tags, labels for the search boxes, which segment
  is pressed, rows that open as buttons, an alert banner that says what went wrong (not "can't reach" when the page's
  server answered with an error), and charts readable with the keyboard (Tab to one, then the arrow keys).

Security

From the November review's remaining findings:

• Each user's folder is theirs alone. sessions\ was a folder any user could make folders in, named by user
  name: anyone could make another user's first, write records into it, or read theirs. Now the service makes each
  user's folder as they sign in, named by their account's SID, for that user, admins and the service only; users
  can't make folders there. An older version's folder moves to the new name with its history, if it was made by its
  own user; one someone else made is moved aside.
• The install is checked before it's put in place. The installer copies the program into a folder of its own in
  Program Files and checks every file against the manifest while the installed version keeps running. Only the
  build's files are copied: anything else in the release folder (a .pth file would have run as SYSTEM) is left out.
  If a file doesn't match, nothing installed is touched. Until now the copy went over the installed program and was
  checked after.
• The build is tighter. It checks the packages are the tested versions (requirements.txt) and the bundled DLLs
  are the ones shipped (by SHA-256), and copies only the packages the program uses: 1,991 files instead of 2,420.
  This release's Python is 3.12.10.
• A crash record names an exe's path, and any program can write one: HW Blackbox looks up a short path's full name
  only under Program Files, and never a network path.

Install or update

From 1.0.10 or later: the page offers this version; click Update. From 1.0.9 or earlier: download
HWBlackbox-win64.zip below, unzip it, and double-click Install.cmd. An update keeps the settings and the
history. New here? See Install: it offers the PawnIO driver if
it's missing.

Check the download

Get-FileHash .\HWBlackbox-win64.zip -Algorithm SHA256

SHA-256: 771dd65c42f6d483f14771ac467623692aa85b0fd2f143c8d9bca91081138659

HW Blackbox 1.0.12

A laptop's battery in Diagnose. The settings and the history carry over.

New: the battery in Diagnose

On a laptop, the Diagnose tab now has a Battery check:

• Its wear: how much of the charge it held new it still holds ("Holds 30 Wh of the 55 Wh it was made for: 45 %
  worn"). Under 20 % worn is fine; 20 to 40 % is normal for a battery a few years old, with how to slow it (a charge
  limit, less heat); 40 % or more says to plan a replacement, and to keep it plugged in for long work meanwhile, since
  a worn battery can cut out near empty before Windows warns.
• How it was used over the last day: the time on battery, how fast it drained, and how long a full charge would
  last at that rate.
• How low it ran: down to 5 % or less on battery, it says so, and how to make Windows hibernate at its critical
  level so running out never loses work.
• For the battery's whole history, it points to Windows' own powercfg /batteryreport.

Desktops have no battery, and no Battery check.

Also

• The README says HW Blackbox has now been tested on two PCs: the AMD desktop it started on, and an Intel laptop.

Install or update

From 1.0.10 or later: the page offers this version; click Update. From 1.0.9 or earlier: download
HWBlackbox-win64.zip below, unzip it, and double-click Install.cmd. An update keeps the settings and the
history. New here? See Install: it offers the PawnIO driver if
it's missing.

Check the download

Get-FileHash .\HWBlackbox-win64.zip -Algorithm SHA256

SHA-256: 45c6f8a4294ceb53643312a7df2ac1c7ed47854d20bb7f240a3e8128ed7f14ab

HW Blackbox 1.0.11

Uninstall from Settings, and laptops install cleanly. The settings and the history carry over.

Installed apps

• HW Blackbox is listed in Settings → Apps → Installed apps, with its version, size and links. Its
  Uninstall asks Windows for an admin, removes the service, the agent's task, the program, the shortcut and the
  entry, and shows what it did; the window closes by itself after 15 seconds (or stays, with any warnings).
• The data stays in C:\ProgramData\HWBlackbox (logs, reports, settings), as with Uninstall.cmd. Delete the
  folder to remove it too, or run install.ps1 -Uninstall -RemoveData.
• Uninstall.cmd works from C:\Program Files\HWBlackbox too. Run from there, it was removing the folder it ran
  from: it could leave the folder behind (still the process's current folder) and end with "The batch file cannot be
  found". It now leaves the folder first, and ends cleanly.

Fixes

• A click no longer freezes the install or update window. Windows' QuickEdit starts selecting text on a click, and
  while it selects, the window's program waits: an update looked stuck at its last step until the window was closed.
  QuickEdit is now off in these windows, and the last step says what it's waiting for (the service's first readings,
  usually 10-40 seconds).

• A laptop's install no longer ends "DONE WITH PROBLEMS: no rail voltages". The installer's last check took no
  rails for a fault; a laptop (or a board whose sensor chip can't be read) has none to read. It says so instead. With
  1.0.10's updater this also kept the update window open, showing a problem that wasn't one.

Install or update

From 1.0.10: the page offers this version; click Update. From 1.0.9 or earlier: download HWBlackbox-win64.zip
below, unzip it, and double-click Install.cmd. An update keeps the settings and the history. New here? See
Install: it offers the PawnIO driver if it's missing.

Check the download

Get-FileHash .\HWBlackbox-win64.zip -Algorithm SHA256

SHA-256: 28701f41a385214f5c9cf6dfb0fc8f3df6bd8a06e0d06b34b3ddbf7465a83dc6

HW Blackbox 1.0.10

Updates from the page. The settings and the history carry over.

New: updates

• Once a day the page asks GitHub for the latest release. When there's a newer one, the top of the page says so,
  with What's new (the release's page) and Update. The Overview's Service card says when it last asked, with
  check now.

• Update asks Windows for an admin (the same prompt as Install.cmd), then opens a window that:

  1. downloads the release's zip into C:\ProgramData\HWBlackbox\update, where only SYSTEM and admins can write;
  2. checks it against the SHA-256 GitHub gives for it, and the one in the release notes;
  3. unpacks it, and checks it's the version offered;
  4. runs that version's installer (which checks every file again, keeps the settings and the history, and offers
     the PawnIO driver if it's missing);
  5. deletes the download.

  Done, the window closes by itself after 15 seconds and the page reloads into the new version. If the installer
  had problems, the window stays open to show them. If any check fails, nothing is installed and the running
  version carries on.

• Nothing installs by itself. HW Blackbox runs as SYSTEM, so a new version goes in only when someone at the PC
  clicks Update and says yes to Windows.

• The check sends GitHub nothing but the request itself (with HW Blackbox's version in it). updates.check: false in
  config.json turns the daily check off; check now still asks when clicked.

• From an elevated prompt: & "C:\Program Files\HWBlackbox\python\python.exe" -m hwblackbox update (--dry-run
  stops before the install).

This is the first version with the updater: from 1.0.9 or earlier, update with this version's Install.cmd. From
here on, the page offers each new version.

Install or update

Download HWBlackbox-win64.zip below, unzip it, and double-click Install.cmd. An update keeps the settings
and the history. New here? See Install: it offers the PawnIO driver
if it's missing.

Check the download

Get-FileHash .\HWBlackbox-win64.zip -Algorithm SHA256

SHA-256: bb83305474217aef6d305a43f920ba7c8590138442d06d5c937950f1affc0de5

HW Blackbox 1.0.9

Laptops, why a PC went off, and the installer offers the sensor driver. The settings and the history carry over.

The installer offers PawnIO

The CPU's and the motherboard's sensors need the PawnIO driver. Until now the installer only warned when it was
missing, and the warning was easy to miss. Now it asks: Install PawnIO now? [Y/n]. Y (or Enter) installs it with
winget, in the installer's window, and HW Blackbox starts with the sensors working. N goes on without it. Without
winget, it opens PawnIO's download page. With nobody to answer (a scripted install), it leaves it out, as before;
install.ps1 -PawnIO yes installs it without asking.

Already installed without it? Run Install.cmd again and answer yes: the settings and history are kept.

Laptops

On a laptop, 1.0.8 reported two problems that weren't: "No rail voltages" (a laptop has no power supply rails to
read) and "No CPU temperature (the sensor driver may be gone)" when the driver had never been installed.

• The PawnIO driver is now checked directly. When it isn't installed or isn't running, that's the one problem
  shown, saying what it costs (the CPU's temperature and power; on a desktop, the rails too) and how to install it
  (run Install.cmd again). Diagnose gives the steps.
• No rails is no problem where there are none: on a laptop, or a desktop board whose sensor chip
  LibreHardwareMonitor can't read. The page says so in a note instead. A board chip that answered before and doesn't
  now is still a problem.
• The battery: on a laptop the Overview's Board card becomes a Battery card: the charge, plugged in or on
  battery, the rate it charges or drains, and its wear. The 5-second log records the charge and whether it was
  plugged in, and Charts can draw the charge.
• Without the driver, the CPU's power and an Intel GPU's power are no longer shown as a made-up 0 W.
• An Intel GPU's memory is labelled shared: it borrows the PC's own.
• The GPU card names an Intel GPU, rather than "GPU".

Why it went off

Every power-off report now says what Windows recorded about it (its Kernel-Power 41 record): a blue screen (with
the stop code), the power button held down, going into or coming out of sleep, or nothing (the power cut, or
a freeze too hard to record anything). On a laptop it also says what the battery was at just before. Reports written
before 1.0.9 get the same answer, looked up from Windows' records while they still have it.

Diagnose's advice follows from that: a blue screen, a forced power-off, a sleep problem or a flat battery each get
their own steps, and a laptop no longer gets advice about power supplies and wall sockets.

Fixes

• Intel CPU temperature: the rails log (4 a second) only knew AMD's sensor names, so on an Intel CPU its CPU
  columns stayed blank. The 5-second log took the highest of the CPU's temperatures, and on Intel those include each
  core's "distance to TjMax" (how far below its limit it runs, higher when cooler), so an idle Intel CPU could be
  logged hotter than it was. Both now read the package temperature.
• The Overview's power-off card says when the last one was even when there are no readings from before it (one that
  came before HW Blackbox was installed): "before" the time the PC came back on.
• A log file begun by an older version gets the new column names written again, partway down, at the update, and the
  page reads the rows after them by those.

Install or update

Download HWBlackbox-win64.zip below, unzip it, and double-click Install.cmd. An update keeps the settings
and the history. New here? See Install: it offers the PawnIO driver
if it's missing.

Check the download

Get-FileHash .\HWBlackbox-win64.zip -Algorithm SHA256

SHA-256: 9f35cb87ef7cfe3f1cda23a9a30ed4590d0a59015dde9fde3c80c4af0a81fe7f

HW Blackbox 1.0.8

A Diagnose tab that checks what HW Blackbox has recorded and says what to do, and each program's memory, graphics
memory and GPU use over time, next to its CPU. The settings and the history carry over.

New: Diagnose

A new tab checks what HW Blackbox has recorded, and for each thing it finds, shows what it saw and what to do about
it. It reads and suggests; it changes nothing.

• Power-offs in the last 30 days, with the last readings before each.
• Programs crashing in the last 7 days. When several different programs crash the same way, it suggests testing
  the memory and running it at stock speed, since that points at the PC rather than at one program.
• Display driver resets.
• CPU and GPU heat, with the busiest program at the hottest moment.
• The power supply's rails against the ATX limits.
• A program keeping the CPU busy. For Windows' own programs (the desktop compositor, Explorer, Defender, Search
  and others) it says what the program is and what usually fixes it.
• A program whose memory keeps growing, with the times it jumped. It says when the jumps came right after the
  screens changed (a remote session, a monitor, the resolution or scaling).
• RAM and graphics memory running full, with the biggest programs at that moment.
• Disk space, a Windows update waiting for a restart, and uptime.

The Overview says when Diagnose has found something, and the tab shows a count.

New: memory, graphics memory and the GPU by program

The Processes tab's history now has four measures: CPU, Memory, GPU memory and GPU. Each shows its
leading programs over 1 hour to 7 days, with a chart and a table.

• Memory: each program's private memory, all its processes together. The table shows what each holds now, its
  average, the most it held and when, and how much it grew. A gigabyte or more that a program still holds is
  highlighted, since that's what a leak looks like.
• GPU memory and GPU: from Windows' own GPU counters (the ones Task Manager's GPU columns use), so they work for
  any make of GPU. NVIDIA's own interface can't tell programs apart on Windows.
• The log is now logs\programs_YYYYMMDD.csv, a row per program a minute with all four measures. 1.0.7's
  cpu_YYYYMMDD.csv is still read, so the CPU history carries on unbroken.

Fixes

• Links to a view on the Processes tab (#processes:mem) open that measure and scroll to it.
• A screen change that never happened is no longer recorded each time the session agent starts (it read the
  screens before asking Windows for their real size and scaling, so the first look after its start saw them "change").

Install or update

Download HWBlackbox-win64.zip below, unzip it, and double-click Install.cmd. An update keeps the settings
and the history. New here? See Install (the PawnIO driver
first).

Check the download

Get-FileHash .\HWBlackbox-win64.zip -Algorithm SHA256

SHA-256: 029299b715297643d39e715ea673333a21072a850d1362885d805d86b30da460

HW Blackbox 1.0.7

A history of which programs used the CPU, and a fix for a busy core slowing the rail readings. The settings and the
history carry over.

New: CPU by program, over time

Windows keeps no history of which program used the CPU: Task Manager only shows now. HW Blackbox now logs every
program's CPU use each minute (logs\cpu_YYYYMMDD.csv, kept 183 days). It comes from the process list the service
already takes every 2 seconds, so it costs next to nothing.

• The Processes tab charts it over 1 hour to 7 days. Hover anywhere on the chart to see the busiest programs at
  that moment, and click a program in the table to put it on the chart or take it off.
• A program is all of its processes together (a browser's dozens are one row). There's also a row for System
  interrupts, the time the processors spend on drivers' interrupts, which Windows charges to no program.
• The Overview names the busiest program of the last hour.
• App incident reports list the busiest programs of the last 3 minutes.

Fixes

• A busy core no longer slows the rail readings. Reading the CPU's sensors means visiting each core in turn. On
  the PC this was built on, one core was kept busy all night, most likely by the Windows desktop compositor, which
  runs at a higher priority than HW Blackbox. Every CPU read waited for that core, the rails were read on the same
  thread, and they dropped from 4 readings a second to about 2. The CPU now has a thread of its own, read once a
  second, and the rails never wait for it. The rails log's CPU columns hold the newest of those once-a-second
  readings.
• A slow rails lane is no longer a "problem". It sent Home Assistant alerts ("The rails lane is slow") that read
  like a fault in the power, when the rails were still being read and were fine. It's now a note on the Overview.
  A rails lane that stops altogether is still a problem.
• When the CPU's sensors are held up, the problem now says so ("No CPU readings for 42 s: reading the CPU's
  sensors is held up"), instead of blaming the sensor driver.

Install or update

Download HWBlackbox-win64.zip below, unzip it, and double-click Install.cmd. An update keeps the settings
and the history. New here? See Install (the PawnIO driver
first).

Check the download

Get-FileHash .\HWBlackbox-win64.zip -Algorithm SHA256

SHA-256: dbdd8a0d727a95369feb52de07ef6a30cb36aa8e1146e4c8c473cd496777e7b8

HW Blackbox 1.0.6

Security fixes from an outside review, plus a small dashboard change. Nothing changes in what's recorded or in the
files it writes; the settings and the history carry over. Updating is recommended, above all on a PC with more
than one account.

Security

These need someone signed in to the same PC with an account of their own. On a PC with one account, they don't
apply.

• Two ways a standard account could run code as SYSTEM are closed.
  • The service, starting a stopped session agent again, used pywin32's COM cache in C:\Windows\Temp, where any
    account can create files. The cache is now in the program's own folder, which only admins can change, and the
    service won't use COM if it's anywhere else.
  • On a first install, the installer created the data folder's subfolders before locking it down, and kept a data
    folder someone else had made. Now the folder is made with its final owner and permissions before anything goes
    in it. A folder someone else made first, or a link to somewhere else, is moved aside rather than used. The
    service won't write through a link, and install.ps1 -Uninstall -RemoveData no longer follows one.
• Another account can't keep the service from starting. It used a lock name any account could take first. Started
  by Windows, the service no longer needs one.
• The Events tab: a session folder (which every account can create) can no longer pass itself off as the service,
  and one damaged line can no longer break the tab for everyone.
• Command lines: the Ports page and its files hide password-like values (--password ***,
  https://user:***@host), since every account can read them.
• App reports: at most 20 an hour, since crash records in Windows' log can be written by any program. Old ones go
  after 183 days, like the records; power-off reports are kept.
• The dashboard:
  • it refuses data requests from other websites;
  • a chart request can't ask for one reading thousands of times over (that could use gigabytes of memory);
  • a program holding the dashboard's port can no longer hang the session agent.
• Home Assistant: a redirect is reported as an error instead of being followed, so the token isn't sent on to
  wherever it points.
• A network share in a program's path is no longer looked at by the service.

Fixes

• The power-off check doesn't depend on Windows' display language any more. It read the English "Date:" label in
  Windows' event text, so it would never have written a power-off report on Windows in another language.
• The power-off check runs first, without waiting for the sensors to open, so a slow sensor driver after a power
  loss can't hold up its report.
• A typo in config.json no longer stops the service, for example "interval_s": "fast". A setting of the wrong
  kind keeps its default, and the Overview names it.

Dashboard

• The page's version is in the header, next to the name.
• After an update, an open page says so, with a Reload button that keeps the tab you're on. A page that's
  open while you install 1.0.6 is still the old one, so reload it once; from then on it tells you.

Install or update

Download HWBlackbox-win64.zip below, unzip it, and double-click Install.cmd. An update keeps the settings
and the history. New here? See Install (the PawnIO driver
first).

Check the download

Get-FileHash .\HWBlackbox-win64.zip -Algorithm SHA256

SHA-256: 6e5d752cf78844427441cd08b901cdf99179f3e55e85c17ce8ffc0241e46412b

HW Blackbox 1.0.5

A polish release for the dashboard and the installer. Nothing changes in what's recorded or in the files it writes;
the settings and the history carry over.

Dashboard

• Phones and narrow windows: no more sideways scrolling on the Power and Processes tabs. The header's four
  status chips fit on one line with short names. On Charts, the list of readings folds away so the charts come first.
  Opening a report scrolls to it, and the selected tab stays in view.
• Layout: the four Overview cards go 4 → 2×2 → 1 instead of leaving one card alone on a row. One or two charts
  get a taller plot. A lone fifth chart on the Power tab takes the whole row. Long tables (Sensors, Events, Ports)
  keep their column names in view as you scroll.
• Easier to read:
  • times like "1 h 60 min" can't happen any more;
  • events say "ran 3 h 34 min" instead of "ran 3h 34m 12s";
  • a program that restarted on its port says so ("restarted (pid 29652, now 31000)");
  • Windows Error Reporting names are in words;
  • axis labels carry only the decimals they need;
  • a rail that didn't move says "steady".
• The rails: each rail's chart spans at least 2 % of the rail, so the sensor chip's one-step flicker no longer
  fills the whole +5 V chart.
• Charts: readings that share a chart never share a colour, and tooltips work with touch and pen.
• Incidents: the list shows each report's title on up to two lines and its kind, with the file name in the
  tooltip. A report has a Copy button.
• Empty and error states: with no power-offs, the Power table says so instead of staying blank; with no sensors
  yet, so do Sensors and the Overview. When the page can't reach HW Blackbox, the status chips grey out and the time
  turns red, instead of staying green.
• While you work with it: the timed refresh no longer clears text you're selecting, and a Power chart's tooltip
  survives the 5-second redraw. The page stops polling while it's hidden or minimized.
• Keyboard and contrast: visible focus. The tabs work with the arrow keys, Home and End. Enter or Space opens a
  sensor group, an event or a report. Dim text is brighter (4.8:1 contrast instead of 3.1:1).

Installer

• It checks for the PawnIO driver and says how to install it when it's missing. "No rail voltages" says what to do.
• It ends by saying where to open the dashboard.
• If the admin prompt is declined, Install.cmd says it wasn't installed, instead of showing the previous install's
  report.

Install or update

Download HWBlackbox-win64.zip below, unzip it, and double-click Install.cmd. An update keeps the settings
and the history. New here? See Install (the PawnIO driver
first).

Check the download

Get-FileHash .\HWBlackbox-win64.zip -Algorithm SHA256

SHA-256: d155de1036928a125e18bf97633c750290f32f94d7800563a33dcd25e7145965

HW Blackbox 1.0.4

The first public release of HW Blackbox: a hardware monitor and black box for Windows. It records every sensor,
the voltage rails four times a second, power-offs, app crashes and exits, shutdown requests, ports and disk space,
from boot, whether or not anyone signs in. You read it all in a local dashboard, and optionally in Home Assistant.

Install

1. For the CPU and motherboard sensors, install the PawnIO driver first: winget install namazso.PawnIO.
2. Download HWBlackbox-win64.zip below and unzip it.
3. Double-click Install.cmd. It asks for admin rights, installs the service and the agent, and shows what it
   did.
4. Open HW Blackbox from the Start menu (or http://127.0.0.1:9070/).

Running Install.cmd again later updates it and keeps the settings and the history. Uninstall.cmd removes it and
keeps the data.

Check the download

Get-FileHash .\HWBlackbox-win64.zip -Algorithm SHA256

SHA-256: f9ecfe5b253f6c65628418a2f397c240d3d8f962551638d537e1a9096b27bd62

The installer then checks every file against the release's manifest. The scripts aren't code-signed, so Windows
SmartScreen may warn the first time you run Install.cmd.

What it records

• Sensors: every reading LibreHardwareMonitor finds, every 5 s; the +12/+5/+3.3 V rails, Vcore, SoC and CPU
  power 4 times a second. Every row is on disk before the next is taken, so the last seconds before a power loss
  survive.
• Power-offs: at the next boot, a report with when the PC really went down (the last logged row, not Windows'
  guess), how long it was off, and the last two minutes of readings.
• Apps: starts, exits and crashes of the apps you choose, with what the exit code means, and an incident report
  with the last three minutes of everything.
• Windows: crashes, hangs, display driver resets, who asked for a shutdown or restart, sessions, sleep, and a
  Windows update waiting for a restart.
• Ports (who listens where, and clashes), and disk space for every drive, with a warning when the Windows
  drive fills up fast.

Requirements: Windows 10 or 11, 64-bit, and an administrator account to install. It's been tested on one PC so far
(Ryzen 5 5600G, B550, RTX 3060); see Limitations in the README.