LoadView v2.10.1

What's new

Security fix for the optional accurate-CPU-temperature setup, plus the first real test of two code
paths v2.10.0 shipped without ever running. If you use that feature, update. If you leave it off
(the default), nothing here affects you.

The bug: a file left in the folder beforehand could redirect a system-rights write

The setup creates C:\ProgramData\LoadView and locks it down — but C:\ProgramData lets any standard
user create a folder there first. Setup handled that: it takes ownership and replaces the permissions.
What it did not do was remove files that were already inside, and whoever created those files
stays their owner — which is enough to grant themselves write access back.

That matters because the reader, which runs with system rights, wrote to out\cputemp.tmp and appended
to out\helper.log. Either name planted in advance as an NTFS hard link would have redirected that
write to the linked file. Verified: a write through a hard link does replace the target's contents. So
any file the planter could read, the reader would have overwritten with a temperature value.

Fixed: setup now empties its folders before locking them down (and again afterwards, in case
something slipped in while permissions were being replaced), and the reader never writes into a file
that already exists. Deleting a planted link removes only that entry, which is what breaks the redirect.

Two paths that had never actually run

• Installing PawnIO. On the machine v2.10.0 was built on, the driver was already present from an
  earlier test, so setup always took its "already installed" shortcut — meaning the download,
  verification and install had never once executed for real. They have now, and they work. The
  installer is additionally checked against a pinned SHA-256, on top of its signature and
  publisher.
• Refusing a bad installer. Deliberately requiring the wrong publisher confirmed the check fails
  closed: it logged the real certificate, refused, and did not run the file.

Better diagnostics, and a sensor that was worth catching

The log now lists every CPU temperature sensor found and which one was used. That immediately
showed LibreHardwareMonitor reporting Distance to TjMax values (25–29 while the cores read 71–75) as
temperature sensors — thermal headroom, not a temperature. On a machine without a package sensor, the
"hottest sensor" fallback could have shown one of those as your CPU temperature. They are now excluded.

Install

Download LoadView.exe below and run it — no install, no dependencies, works on any Windows
10/11 PC. Unsigned, so SmartScreen/Defender may warn on first run (More info → Run anyway).

Already using the accurate CPU temperature? The new version asks for the one-time administrator
confirmation again, because the reader it installs has to be refreshed.