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.