v3.0.6

What's new

The red "too hot" threshold is now one per kind of component. One number for everything could only
ever be right for one of them: 70 °C is an unremarkable afternoon for a CPU and a bad day for a hard
disk. Set it for the CPU and your disks never turn red; set it for the disks and the CPU is red at idle.

Settings → Temperatures → Highlight when hot now has a row each for CPU, GPU, Disks and
Chipset & others, each switchable on its own, offered as 90 / 85 / 55 / 80 °C. Disks sit well below
the chips on purpose — a drive typically declares its own warning around 83 °C, so 55 is a "worth a
look" figure rather than a failure.

If you already had a threshold set, it carries over to all four, so nothing changes colour until you
say so.

The Temperatures page is also reordered, because it had outgrown the window: what to show, in what
unit, whether the CPU can be read at all, and what counts as hot are all visible now, with the tile
sizes — cosmetic, and shared with the Fans page — as the part that scrolls. The Settings window is 40 px
taller, and a label no longer swallows the & in "Chipset & others".

Everything from 3.0.0–3.0.5 is included.

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).

If you use the accurate CPU temperature, this asks for the one-time administrator confirmation again —
the version stamp changes, so the system-rights component is refreshed.

v3.0.5

What's new

Fixed: the temperature and fan tiles wrapped onto a second row while the first still had room.

Six tiles of 46 px need 276 px and had a 300 px window to sit in — but the row was drawn inside a 6 px
margin on each side with 4 px between tiles, so 32 px of spacing was competing for the 24 px left over
and the sixth tile went to the next row. The margin is now 4 px and the spacing 3 px, so the row fits.
The row is centred either way, so the margin only ever showed up in this case — where it was doing harm.

Checked by rendering the tiles across window widths of 250–400 px, tile sizes of 40–60 px and 2 to 8
sensors: nothing else changes row count except where the tiles genuinely do not fit, and no reading is
cut off.

Tiles keep the size you set rather than being squeezed to gain a column, because at 46 px a reading like
2412 already fills 40 of the 42 px inside a tile — squeezing would trade the wrap for 24…. If you do
want more of them per row, Settings → Temperatures / Fans → Tile columns fits them to the width on
purpose.

Everything from 3.0.0–3.0.4 is included.

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).

If you use the accurate CPU temperature, this asks for the one-time administrator confirmation again —
the version stamp changes, so the system-rights component is refreshed.

v3.0.4

What's new

Two fixes to the disk tiles in the Temperatures section, both reported from a desktop with four
drives and Google Drive mounted.

A cloud-storage drive no longer has its letter stuck onto a real disk. Google Drive presents itself
as a fixed drive with its own letter, and that letter was ending up on the boot disk's tile, which read
C: F:. Drive letters are now matched to disks by asking Windows which physical disk a volume lives on
and requiring the answer to be an actual disk — which a virtual file system is not.

SATA drives now report a temperature too. Before, only NVMe drives got a tile, so a machine with two
NVMe and two SATA drives showed two tiles instead of four. NVMe drives answer a standard temperature
query; SATA drives keep the reading in a SMART attribute instead, which LoadView now reads — still with
no driver and no administrator rights, the same as before.

Also: the Fans page now tells you when the chipset and fan switch has nothing to read because the
sensor driver under Temperatures is off. Those readings need it, and previously nothing said so.

Everything from 3.0.0–3.0.3 is included.

A note on how this was tested

The machine this was built on has a single NVMe drive and no cloud drive mounted, so the two fixes above
were verified by exercising the code paths and confirming no regression to the working NVMe tile — not by
reproducing the original faults. If a tile is still missing or mislabelled, %APPDATA%\LoadView and
C:\ProgramData\LoadView\out\helper.log are the places that say why.

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).

If you use the accurate CPU temperature, this asks for the one-time administrator confirmation again —
the version stamp changes, so the system-rights component is refreshed.

LoadView v3.0.3

What's new

Fixed: the CPU temperature tile no longer disappears for a few seconds now and then.

The component that reads the temperature and the overlay that displays it were passing the value through
one small file, and each could lock the other out of it — so a reading was sometimes published several
seconds late, late enough that the overlay treated it as stale and dropped the tile until the next one
arrived.

Measured over three minutes before the fix: 8 failed reads and publish gaps of 3.4 and 8.8 seconds.
After: no failed reads, and the longest gap down to 4.5 seconds — which no longer matters, because a
reading is now kept for 30 seconds rather than 10. A temperature moves slowly, so showing a value a few
seconds old beats a tile that blinks out and back.

Everything from 3.0.0–3.0.2 is included.

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).

If you use the accurate CPU temperature, this asks for the one-time administrator confirmation again —
the fix is partly in the component that runs with system rights, so it has to be refreshed.

LoadView v3.0.2

What's new

Fans now sits below Temperatures, which is where it belongs. 3.0.0 added both new sections directly
under the clock but inserted them at the same spot, so the second one ended up in front of the first.

If your configuration came from 3.0.0 or 3.0.1 it is corrected once, automatically. The correction is
deliberately narrow — only the exact clock, Fans, Temperatures arrangement that the bug produced — so
if you have moved either section yourself, your layout is left alone. You can always drag them in
Settings → Sections.

Everything from 3.0.0 and 3.0.1 is included: the Temperatures tile section (disk temperatures
need no driver), the Fans section, the Dark / Light / Follow-system theme, and the rearranged settings.

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).

If you use the accurate CPU temperature, this asks for the one-time administrator confirmation again.
That happens on every version change by design: the component that runs with system rights is always
refreshed to match the app, rather than being trusted to still be the right one.

LoadView v3.0.1

What's new

Two small fixes on top of 3.0.0.

• The note at the bottom of Settings ran underneath the OK button. It now ends well clear of the
  buttons, and reads as a whole sentence rather than being cut off. The cause was not the wording: that
  strip is narrower than the window (it sits beside the category list), and the buttons only move to
  their final position once the window lays out — so it was being measured against the wrong width.
• About did not list the theme. The 3.0.0 notes were written before the theme was built, so the one
  genuinely new setting was the one thing missing from the list. It is there now, under 3.0.0, where it
  shipped.

Everything from 3.0.0 is included: the Temperatures tile section (with disk temperatures that need
no driver), the Fans section, the Dark / Light / Follow-system theme, and the rearranged settings.

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).

Coming from 3.0.0 with the accurate CPU temperature enabled: this asks for the one-time administrator
confirmation again, because the component that runs with system rights is refreshed with the version.

LoadView v3.0.0

What's new in 3.0

Temperatures get a section of their own, fans get one too, there's a light theme, and the settings
dialog has been rearranged so things are where you'd look for them. Your existing configuration is
kept — nothing needs redoing.

Temperatures, as labelled tiles

Small squares under the clock, one per component, instead of a number squeezed onto the CPU and GPU
graph headers.

• Disk temperatures need no driver and no administrator. LoadView asks the drive itself, using a
  query Windows allows any user to make, so your SSD's temperature simply appears — labelled by drive
  letter where one can be worked out.
• GPU works wherever the graphics driver reports it (NVIDIA / AMD / Intel).
• CPU uses the ACPI sensor your firmware exposes, or the real core temperature if you enable the
  optional driver.
• Chipset temperature where the motherboard exposes one.

A Fans section

Fan speeds in RPM, same tile layout. These live on the motherboard's controller chip and cannot be read
without the optional driver and a second switch of their own — and plenty of laptops expose no fan
at all even then. When there is nothing to read, the section hides itself rather than showing an empty
box.

Both fully configurable

Choose which components appear and in what order, and set tile and text sizes. Choices are stored per
component — by serial number for disks — so adding a drive later doesn't shuffle what you picked. A
component you selected that is currently missing stays in the list, marked, instead of being dropped.

Light theme

Settings → Window → Theme: Follow system (default), Dark or Light. Follow system tracks
the Windows app theme and switches while running. If you never chose your own clock / date / weekday
colours, they move to colours that suit the new background; colours you did choose are left alone.

Settings that make sense

Eight pages, one subject each. Graph height now sits with the graphs rather than under "Layout", the NET
graph's two colours sit with the NET graph instead of on another page, and everything about the IP
section is in one place instead of spread across three. Unit choices name both options rather than being
a checkbox you have to guess at, "0 means off" became Auto and At checkboxes, and every row has a
tooltip.

Fixed

Switching the hot-temperature highlight off no longer comes back as "red from 30 °C" after a restart.

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).

Using the accurate CPU temperature already? This version refreshes the component that runs with
system rights, so it asks for the one-time administrator confirmation once more.

Not verified on the machine this was built on

Said plainly, because it matters for what you should expect:

• Fan speeds and chipset temperatures. The laptop this was developed on exposes none — the probe
  reports "(none exposed)" — which is normal for laptops and not a fault in the app. The code path runs
  and publishes correctly; whether your board exposes anything is up to the board.
• More than one disk, and SATA/HDD drives: only a single NVMe drive was available to test with.

LoadView v2.11.0

What's new

A security review of the whole app, not just the optional CPU-temperature feature — plus the
fixes it turned up and a measurable drop in idle cost. Everyone should update; nothing here changes
how LoadView looks or behaves.

A DLL left next to LoadView.exe is no longer loaded

Windows looks for a program's libraries next to the program first. LoadView needs four system
libraries (pdh.dll for the performance counters, plus the NVIDIA/AMD/Intel libraries for GPU
temperature), and because it is a portable exe that people keep in Downloads, on a USB stick or in a
shared folder, a file with one of those names placed beside it would be loaded as part of the app.

LoadView now refuses to use any of those libraries if it finds one sitting next to the exe — the
affected reading simply shows n/a. Two more obvious fixes were tried first and measured to not
work: restricting the library search path does nothing here, and pre-loading the genuine library
from Windows first still let the planted file be loaded and run. Only refusing outright actually
prevents it.

The optional CPU-temperature setup

• The driver installer's certificate is now matched exactly. The old check searched for the
  publisher's name anywhere in the certificate details, so a certificate issued to a look-alike
  domain such as namazso.eu.somebodyelse.example would have satisfied it.
• A file handed to the setup on the command line is now checked before being copied anywhere,
  and the setup's working folder is no longer readable by other users. Previously an
  administrator-approved run could be pointed at any file on the machine and would place a copy of
  it somewhere every user could read.
• The "administrators only" check on the folders the privileged reader runs from now also verifies
  who owns them, not just the permissions — an owner can always rewrite permissions later.

Web lookups are treated as untrusted

The optional country/flag display took the country code straight from a web service and used it in a
file name; a two-character reply such as c: was enough to make the file land outside the intended
folder. Only two letters are accepted now, replies from all three services are size-capped, and
downloads no longer offer your Windows credentials to the server they are talking to.

Two fixes worth naming

• A hand-edited settings.ini can no longer break the app. A font size of 0 made it fail at
  startup, every time, until the file was deleted by hand. All values are now range-checked on load.
• Helper commands can no longer hang instead of timing out. The timeout could never fire, because
  of the order in which the program read the command's output — which means the one-time setup could
  in principle wait forever.

Lower idle cost

Measured on the same machine with identical settings, interleaved 2-minute runs: CPU time dropped to
80% of the previous version (8.13 s → 6.49 s per 2 minutes), with the same memory use. The GPU
figure is now assembled without allocating anything each second, the graphs reuse their drawing
objects instead of recreating them, and both the overlay and the temperature reader stopped polling
files more often than the data actually changes.

One "optimisation" was measured, found to be twice as slow, and reverted — the note is in the
code so nobody repeats it.

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).

Prefer a folder only you can write to. And if you use the accurate CPU temperature, this version
asks for the one-time administrator confirmation again, because the reader it installs is refreshed.

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.

LoadView v2.10.0

What's new

Accurate CPU temperature now works without an administrator account

If your Windows account is not a local administrator — the normal situation on a managed work
PC — the optional accurate CPU temperature used to stay blank, even after you ticked the box and
confirmed the administrator prompt. It now works.

Why it failed: the CPU die temperature is read through the PawnIO driver, whose device can only
be opened by SYSTEM or an administrator. The helper task was registered to run as you with
"highest available privileges" — and for a standard user the highest available token is just the
ordinary one, so the read was denied and the sensor silently reported nothing. This was never about
Memory Integrity (HVCI) or the PawnIO version.

The fix: the reader now runs as the SYSTEM account, which is fully privileged regardless of
your own account. You still only get one administrator prompt, once, during setup — afterwards
the temperature appears silently on every launch.

Hardened, because a privileged task deserves it

A task that runs as SYSTEM and can be started by any signed-in user must never execute or load a
file that a normal user could replace. So the setup now:

• stages the reader and LibreHardwareMonitor into C:\Program Files\LoadView, read-only for
  users, and points the task at that copy instead of at your portable LoadView.exe;
• splits the data channel by direction — SYSTEM writes C:\ProgramData\LoadView\out (users read),
  and only ever looks at the timestamp of ...\in, the single folder the overlay may write to;
• rebuilds each folder's permissions from scratch and refuses junctions, so a folder someone
  created first cannot be inherited with the wrong owner;
• grants the task's start permission to interactive users without the right to modify it.

Two older weaknesses in the setup path went with it: helper tools are now launched by absolute path
(a file planted next to LoadView.exe could otherwise have been run by the elevated setup), and the
PawnIO installer is version-pinned, staged in the protected folder, and checked against its
publisher rather than merely having some valid signature.

Also

• New: LoadView.exe --temp-remove (from an administrator prompt) removes the task and both
  folders, undoing the setup completely. PawnIO is left installed, since other tools may use it.
• Failed helper commands now record their error text in
  C:\ProgramData\LoadView\out\helper.log.
• Upgrading from 2.9.x re-runs the one-time setup once, and the old per-user files in
  %APPDATA%\LoadView\lib are cleaned up automatically.

Everything here is opt-in: leave Settings → Temperatures → "Accurate CPU temp (driver)" off
(the default) and LoadView stays a driver-free, admin-free single exe that installs nothing.

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).