Overseer Help & Getting Started
This guide covers the basic steps for downloading, launching and using Overseer Hardware Monitor on Windows. It also explains what to expect when a sensor reading is unavailable on a particular PC.
Quick Start
- Download the latest Overseer release.
- Run the self-contained Windows x64 installer.
- Launch Overseer.
- Approve the Windows administrator prompt if it appears.
- Open the relevant area for CPU, GPU, memory or drives.
- Use the Readings guide for sensor definitions.
System Requirements
Overseer is a 64-bit Windows desktop application. The current project targets Windows 10 and Windows 11 on x64 systems.
The current OHMv1 Windows x64 installer is self-contained. You do not need to install a separate .NET runtime before using it.
Administrator access is required by the current application build so it can access supported low-level hardware telemetry.
Download & Installation
Use the Overseer Download page to obtain
the current GitHub release. OHMv1 is distributed as the
self-contained Windows x64 installer
Overseer-Setup-1.0.0-x64.exe.
Run the installer and follow the Windows prompts. No ZIP extraction or separate runtime setup is needed for this release.
First Launch
On launch, Overseer detects supported CPU, GPU, memory, motherboard and storage hardware, then initializes the monitoring stack. Some values can take a brief moment to appear while sensor drivers bind and the first readings are collected.
Windows will request administrator approval because the application currently runs elevated. Approve it only when you intended to start Overseer from a trusted release.
Hardware, firmware, drivers and motherboard support affect which sensors can be read. A normal system may show a useful set of readings without exposing every possible temperature or power value.
Navigating Overseer
Overseer presents live hardware information in focused sections rather than a complete raw sensor table. The available panels and values depend on the PC.
Temperatures
CPU, GPU, drive and other supported thermal readings are shown where the device reports them.
Usage
CPU, GPU and memory utilization help show how much of each resource is active at a given moment.
Power
CPU and GPU power values appear when supported by the device, firmware and monitoring interfaces.
Drives
Storage panels can include detected drive details, temperatures and available health information.
System Information
Hardware information provides basic details about the CPU, graphics, memory and connected storage that Overseer detects.
Sidebar Mode
Open Sidebar Mode from the View menu for a dockable live overlay. It can show FPS, CPU, GPU, RAM, drives and network activity while another application is in use.
Tools and Controls
Overseer can export TXT, CSV and screenshots, refresh System Information, open the application log, reset live statistics, stay on top and minimize to the notification area. English, Spanish and temperature-unit settings are available from the menus.
What do these readings mean?
For definitions of CPU package temperature, GPU hotspot, power readings, drive temperatures, usage values and other sensors, see the Readings guide.
Why Is a Reading Missing or Showing N/A?
Overseer can only display telemetry exposed by the hardware, firmware, driver, Windows and the underlying monitoring libraries. A missing value does not automatically mean the hardware is malfunctioning.
For example, CPU temperature may be available while CPU power is not; an Intel integrated GPU may expose limited sensor data; some drives report temperature without all health information; and laptop firmware can restrict certain telemetry.
Missing telemetry is left unavailable rather than displayed as a false zero or estimate. For more context, see why readings can be unavailable.
Administrator Access and PawnIO
Overseer runs with administrator access to read supported low-level hardware telemetry. Windows asks for that approval when Overseer launches.
If PawnIO is not already installed, Overseer may ask to install the helper during setup. This additional installation prompt should not appear on every launch. Not every computer needs every access path, and available readings still vary by hardware.
Local Monitoring
Overseer reads sensor data on the local computer to display its monitoring views. The application source reviewed for this guide does not include a telemetry-upload feature for sensor readings.
Website privacy terms are covered by the TechPvnk Privacy Policy.
Getting More Help
Use these resources when you need sensor definitions, project information or a place to report a problem.
- Readings GuideUnderstand individual sensor values and unavailable readings.
- Using OverseerSidebar Mode, FPS, exports, alerts and controls.
- Report an IssueReport unexpected behavior through GitHub Issues.
- Source CodeView the Overseer project on GitHub.
- TechPvnk Project WebsiteReturn to the Overseer project site.
When reporting a monitoring problem, include the Overseer version, Windows version, CPU and GPU models, laptop or desktop model when relevant, the missing reading, and whether LibreHardwareMonitor itself shows that reading.