Overseer FAQ

Overseer is a Windows hardware monitoring application for viewing supported temperatures, usage, power, memory and storage information.

Overseer is free to download and its source code is available under the Mozilla Public License 2.0.

View the Overseer source code on GitHub.

Overseer is a TechPvnk project.

The current project targets 64-bit Windows 10 and Windows 11. Overseer does not currently provide a macOS or Linux build.

Use the current release format provided on the Download page. An installer should be run normally; a ZIP release should be fully extracted before launching Overseer.

Overseer can display CPU telemetry made available by supported Intel and AMD hardware through its monitoring stack. The sensors exposed vary by processor, motherboard, firmware and driver.

Overseer detects supported graphics hardware and displays telemetry that the GPU, driver and monitoring stack expose. Detecting a GPU does not guarantee that every temperature, usage or power sensor will be available.

It can work on laptops, but laptop firmware and OEM implementations often expose fewer sensors than desktop hardware. Missing readings on a laptop do not automatically mean a fault.

Hardware identification and sensor access are separate. Firmware, drivers, a device's sensor support, permissions and the monitoring library can all affect available telemetry.

Temperature and power are exposed independently. A CPU can provide a usable temperature sensor without providing a supported power sensor, and missing CPU power does not indicate a CPU problem by itself.

GPU sensor availability differs by graphics hardware, drivers and platform support. Integrated GPUs in particular can expose limited telemetry depending on the system.

SATA, NVMe, USB enclosures, drive firmware and storage interfaces can expose different temperature and health data. Overseer uses SMART and smartctl-backed details where the drive and connection provide them.

No. Monitoring applications can use different access methods, support different hardware and group sensors differently, so the available values and labels may differ.

N/A generally means Overseer could not obtain a supported value for that reading. It does not necessarily indicate hardware failure.

See missing readings in Getting Started for a concise explanation, or the Readings guide for more detail.

1. Confirm that the related hardware is detected.
2. Restart Overseer and allow the sensor views a moment to initialize.
3. Verify that relevant Windows and graphics drivers are installed.
4. Check whether LibreHardwareMonitor itself shows the value.
5. Report the issue if the reading appears supported but Overseer does not display it.

This can point to an Overseer mapping or display issue. Please report it on GitHub Issues with your hardware details and the affected sensor.

Some CPU temperature and power sensors need low-level access that ordinary desktop applications cannot read. Overseer can use the PawnIO helper through LibreHardwareMonitor, and Windows may request permission while that helper is installed or used.

Confirm that you are using a current supported Windows release, that a ZIP download was fully extracted before launch, and that you approved the required administrator prompt. Use the current release notes for any runtime requirements.

Yes. Hardware monitoring is intended for observing systems under load, including games. Resource use can vary with the PC and the sensor data available, so avoid assuming zero performance impact.

Applications may select different sensors, use different labels, refresh at different intervals or aggregate values differently. The Readings guide explains how to interpret the values Overseer shows.

PawnIO is a helper used by the LibreHardwareMonitor stack for supported low-level hardware access. Some sensors are not available to normal Windows applications, so Overseer can use that access path when needed.

Overseer uses LibreHardwareMonitor, which can use PawnIO or other supported access paths to read hardware sensors.

LibreHardwareMonitor is an open-source hardware monitoring project used as part of Overseer's monitoring stack. Overseer builds its own interface and functionality around the telemetry that stack makes available.

View LibreHardwareMonitor on GitHub.

The Overseer desktop application processes hardware telemetry locally for its monitoring views. The application source reviewed for this FAQ does not include a telemetry-upload feature for sensor readings.

The desktop application and the Overseer website are separate. The website uses third-party services such as Google AdSense; see the TechPvnk Privacy Policy for website privacy terms.

Normal local hardware monitoring does not depend on an internet connection. Internet access is used only for actions that open or retrieve external resources, such as download and release pages or obtaining a required monitoring helper.

Download the current release from the Download page or the GitHub Releases page.

Open a GitHub Issue. For hardware-monitoring problems, include the Overseer and Windows versions, CPU, GPU, laptop or desktop model when relevant, affected reading, and whether LibreHardwareMonitor displays it.

Contributions are welcome through the GitHub repository. You can also support development through Ko-fi.