CPU usage can work first
The app can show processor activity while CPU temperature and clock details are locked or unavailable. Use the lock as the setup entry point when offered, rather than treating all CPU statistics as one sensor.
Temperature Sensors
See CPU temperature and clock information beside your other performance readings. Start the optional setup from the CPU lock in SysCubes, complete the Windows sensor steps and check the live values. The status guide below helps you finish setup or identify the reading your PC is supplying.
Optional setup. Supported readings resume on later app launches.
Illustrative sensor states: CPU access has its own setup path, while GPU readings can be available separately.
Quick answer
In the Performance widget, select the CPU lock and choose Unlock CPU readings. Allow the optional Windows sensor setup and complete the official PawnIO installer if it opens. Successful access is remembered for later app launches. If access is active but no CPU temperature appears, check hardware support and diagnostics rather than repeating setup.
Choose your next setup step
Choose the state in SysCubes, then use the manual checklist beside the app. Mark each check as you complete it.
A lock means the app offers a sensor-access setup path. CPU usage can still work while temperature and clock readings need additional access.
If Windows or the installer requests a restart, restart before retrying. A supported CPU reading should replace the lock after access is active.
Follow these manual checks in SysCubes and mark your progress here. Selections reset when you leave the page.
The supported setup path
Choose whether to enable the optional Windows sensor setup. SysCubes starts it when you select Unlock CPU readings, and Windows presents any required administrator approval.
In the Performance widget, find the lock associated with missing CPU temperature or clock readings. Select it to open SysCubes Sensors, the Windows sensor component. The compact overlay and incident report can also show a CPU lock when setup is available.
Review the dialog, then choose Unlock CPU readings to start setup. The action changes to Setting up sensors while busy. Windows can ask for administrator approval. If you cancel, setup remains incomplete and can be retried when you decide to proceed.
The setup connects to the installed service first. If installation is needed, it installs the SysCubes Sensors service and uses the official PawnIO installer for the hardware driver. An existing PawnIO installation can be reused. Review its license and finish any restart the installer requests.
Once access is active, the dialog offers Done. Return to the Performance widget and check CPU temperature and clock speed. Supported readings should appear as fresh values; an active connection with no reading remains unavailable. Capture a new report only after confirming the live values.
Different sources, different availability
A working percentage, a detected processor name or a valid GPU temperature does not prove that every CPU sensor is accessible.
The app can show processor activity while CPU temperature and clock details are locked or unavailable. Use the lock as the setup entry point when offered, rather than treating all CPU statistics as one sensor.
GPU temperature comes through the existing hardware integration. It can be present before CPU setup succeeds. Availability depends on the graphics adapter and sensor support; a missing GPU value is not fixed simply by unlocking CPU readings.
Once supported CPU readings appear live, they can be included in future performance snapshots and incident reports. Capture a new report after setup to review the available values around a slowdown. Older reports retain the values recorded at the time.
SysCubes uses supported LibreHardwareMonitor readings for its hardware sensor integration. This setup focuses on the CPU temperature and clock information displayed by the app, giving those readings a place beside your usage and GPU values.
On PCs with integrated and dedicated graphics, include both GPU models when investigating an unexpected value. The app prefers the adapter with more dedicated video memory when it can determine capacities. The current sensor diagnostic entry helps explain which adapter supplied the reading.
Read what the app is telling you
| What you see | What it means | What to do |
|---|---|---|
| CPU lock / setup not enabled | The app offers an optional access path for missing CPU readings. | Open the lock and choose Unlock CPU readings if you want to allow setup. |
| Setting up sensors | Connection, permission or installation is in progress. | Finish any Windows or PawnIO dialog. Wait for the current action rather than starting another installer. |
| Setup cancelled / Retry setup | The previous setup did not complete. | Retry from the same CPU dialog when ready. Complete a requested Windows restart first. |
| Enabled, with fresh CPU values | Access is active and supported readings are arriving. | Close with Done. Check the readings again after reopening the app. |
| Enabled, but no CPU temperature | Access is active but this PC is not supplying a valid temperature. | Record hardware and sensor diagnostics. Keep the missing value unavailable. |
| Setup error / readings disappear | Setup or the current sensor connection failed. | Record the error, reopen the app and explicitly retry setup if offered. Inspect current diagnostics if it persists. |
Once access is enabled
The sensor opt-in is saved for the current Windows user. Later app launches try the installed service without automatically opening setup or UAC. A stalled service produces an error and reconnect attempts; an explicit setup action can be used for repair.
SysCubes Sensors starts with Windows and reads CPU hardware while the app requests snapshots. It closes hardware access after 20 seconds without requests. This sensor interface supplies readings; it does not expose a hardware-write or overclocking control.
SysCubes Sensors appears in Windows Installed apps and can be removed there. PawnIO is separate because other programs may use it. Review those dependencies before removing the driver; uninstalling the sensor component can make CPU readings unavailable again.
Make the next check useful
Record what changed and which readings still work. That distinguishes incomplete setup, a service connection problem and an unsupported sensor without guessing.
| Record | Why it helps |
|---|---|
| App and Windows versions; exact CPU and GPU models | Identifies the package, operating environment and supported hardware path. |
| Current status and exact setup error | Separates cancelled permission, installation failure and an active connection with no reading. |
| Available CPU usage, clock and temperature; available GPU temperature | Shows whether the gap affects one reading or the whole sensor connection. |
| Fresh Hardware sensors log entry from the affected session | Can identify driver/service state, selected GPU, sensor availability and read errors. |
| Whether the reading survives app relaunch or a requested reboot | Distinguishes first-time setup from reconnect behavior on the same Windows user. |
Review diagnostics before sharing: logs can contain device and system details. For a broader performance investigation, use the FPS drop troubleshooting guide. If your readings work on the desktop but the widget is missing in a game, follow overlay troubleshooting; sensor access and overlay visibility are separate checks.
Your questions, answered
Open the Performance widget and select the CPU lock if it appears. In the SysCubes Sensors dialog, choose Unlock CPU readings. Review the Windows permission request and complete the official PawnIO installer if shown. Successful setup enables supported CPU temperature and clock readings, including readings in future incident reports.
The optional CPU sensor setup can require Windows administrator approval to install its sensor service and hardware driver. The main app remains in its ordinary Overwolf process. After successful setup, later launches reconnect using the saved opt-in without automatically opening UAC. Sensor availability still depends on your PC.
CPU and GPU temperatures can use different access paths. A working GPU reading does not establish CPU sensor access. Check whether the CPU shows a setup lock or remains unavailable after access is enabled. The CPU model, supported sensors and current connection determine whether a valid CPU temperature can be shown.
An active connection means sensor access is enabled, but it does not guarantee a temperature for every processor. If a valid CPU reading is still absent, record the CPU model, app version and current sensor diagnostics. Treat the value as unavailable. Reinstalling repeatedly or interpreting a missing reading as zero will not establish the temperature.
No. Sensor setup enables readings for future monitoring and future report samples. It cannot recover CPU temperatures or clock readings that were missing when an earlier report was recorded. Keep the existing report as evidence of that session, then capture a new incident report after checking live sensor availability.
Your PC. In your hands.
Keep supported temperatures, usage and clock readings together in SysCubes. Explore your monitoring layout and check current Windows release options.
Free • No credit card or account needed • Instant 1-minute setup • Windows 10/11