HWiNFO64 Setup Guide

HWiNFO64 is set up in three stages: install (or run the portable version), choose Sensors-only mode for day-to-day use, and then optionally build a compact Gadget overlay showing just the handful of readings you actually care about. The full process takes about five minutes, and most of the value comes from that last step, since the default sensor window shows far more data than most people need to see at a glance.

Quick answer

Download HWiNFO64 from hwinfo.com, run the installer (or extract the portable ZIP), select “Sensors-only” when prompted, then right-click any sensor row you care about and add it to a Gadget for a small always-visible overlay. Enable logging separately in the sensor window’s settings if you want a historical record rather than just live numbers.

Downloading the right version

HWiNFO64 is distributed only from its official site, hwinfo.com, and it is worth navigating there directly rather than searching, since search ads for hardware monitoring tools occasionally lead to bundled or fake installers. The download page offers both an installer executable and a portable ZIP archive; both contain the identical underlying program and differ only in whether they touch the Windows registry and Start menu.

There is also a 32-bit HWiNFO (without the 64) still offered for legacy systems, but any gaming PC built in the last decade should use HWiNFO64, since the 64-bit version has no meaningful downside and better handles systems with large amounts of RAM or NVMe storage.

After downloading, Windows SmartScreen may show a brief warning for the installer since HWiNFO64 is a smaller independent project rather than a major publisher; this is a standard SmartScreen behavior for less common software and not itself an indicator of a problem, though it’s still worth confirming you downloaded from the official domain before proceeding.

First launch and choosing a mode

On first run, HWiNFO64 presents a settings dialog before the main window opens, including a checkbox for “Sensors-only” mode. Checking this box skips the detailed system summary and drops straight into the live sensor list, which is what most people want for ongoing monitoring rather than a one-time hardware inventory.

The same initial dialog includes options for which sensor categories to enable, including GPU support specifically; make sure this stays checked if you want graphics card temperature and clock data included, since leaving it unchecked at this stage is a common reason people later find GPU rows missing entirely from the sensor list.

These startup options can be changed later from within the program’s settings menu, so nothing chosen here is permanent, but setting Sensors-only and confirming GPU support is enabled during the first launch saves a step later.

Navigating the sensor window

The sensor window itself is organized into collapsible sections by component: CPU, GPU (if enabled), motherboard, memory, and drives each get their own group, with individual rows beneath for each specific measurement (per-core temperatures, individual fan headers, voltage rails, and so on). Clicking the small arrow or plus icon next to a group name expands or collapses it.

For a gaming PC, the rows worth focusing on first are: CPU Package temperature (or the equivalent top-level CPU temp row), GPU Temperature, GPU Hot Spot (if your card and driver expose it), drive temperature under each listed storage device, and CPU/GPU fan RPM rows if your build’s cooling is something you’re actively tuning.

Right-clicking any row opens a context menu with options including resetting min/max recorded values, renaming the row’s display label, and the “Add to Gadget” option covered next. The min/max columns are useful on their own, since they show the highest and lowest values recorded since the program opened, effectively giving you a session summary without needing separate logging.

Building a Gadget overlay

The Gadget feature turns HWiNFO64 from a full window you have to keep open into a small, borderless overlay that sits on the desktop or, with some window management, on top of a game. Right-click any sensor row and select “Add to Gadget” to start building one; repeat for each additional reading you want included.

Once at least one item has been added, a separate small window appears showing just those selected readings, updating live. This Gadget window can be resized, repositioned anywhere on screen, and has its own right-click menu for adjusting transparency, background color, and font size to fit your setup.

A practical starting selection for most gaming builds is CPU temperature, GPU temperature, and one or two drive temperatures; adding too many rows defeats the purpose of a compact overlay, so it’s worth resisting the urge to add every available sensor and instead keeping it to what you would actually glance at during a session.

The Gadget stays on the desktop by default rather than over a fullscreen game; for an overlay that appears inside the game itself, MSI Afterburner’s on-screen display (covered in our PC temperature monitoring software guide) is generally the better tool, since HWiNFO64’s Gadget is primarily designed as a desktop utility rather than an in-game overlay.

Setting up alerts

Threshold alerts are configured from the sensor window rather than the Gadget; right-click a specific sensor row and look for an alerts or warning threshold option, where you can set a value that, if crossed, triggers a visual highlight on that row and optionally a sound notification depending on your configured settings.

A reasonable starting alert threshold for CPU or GPU temperature is roughly 5-10°C below the chip’s documented maximum operating temperature, giving you a warning before actually reaching a throttle point rather than only finding out after performance has already dropped. Check your specific CPU or GPU model’s rated maximum temperature from the manufacturer’s specification page before setting this.

Alerts are most useful for background monitoring during long sessions, streaming, or rendering, where you are not actively watching the sensor window, letting HWiNFO64 flag a problem without requiring constant attention on your part.

Enabling and using CSV logging

Logging is a separate feature from both the sensor window and the Gadget, found within the sensor window’s own settings, typically as a logging or record button in the toolbar. Enabling it starts writing every sensor value to a CSV file at your chosen interval (commonly every one or two seconds), continuing until you stop it or close the program.

A logged session is genuinely useful for catching intermittent problems that don’t show up during a quick glance, like a thermal spike twenty minutes into a game or a GPU clock speed drop that only happens under specific conditions. Open the resulting CSV file in a spreadsheet program afterward, and you can graph any column to visually spot when and how sharply a value changed.

Long logging sessions at a short interval can produce large CSV files over many hours; if you’re logging overnight or for an extended stress test, a 5-10 second interval instead of 1 second keeps file size more manageable while still catching most meaningful trends, since thermal changes generally happen over tens of seconds rather than instantly.

Running at startup and in the background

For anyone who wants HWiNFO64 running continuously rather than launching it manually each session, its settings include a “Start Minimized” and “Run at Windows Startup” option, found in the general settings menu accessible from the sensor window’s toolbar. Enabling both means the program launches automatically and sits quietly in the system tray rather than opening a full window every boot.

Running continuously in the background uses a small, generally negligible amount of system resources, though if you’re specifically optimizing a competitive gaming setup for absolute minimum background overhead, closing it before a match and reopening afterward is a reasonable alternative to leaving it running at all times.

Right-clicking the system tray icon once HWiNFO64 is minimized gives quick access to common actions without reopening the full sensor window, including toggling the Gadget’s visibility, pausing or resuming logging, and exiting the program entirely; this shortcut menu is worth knowing about once you’ve settled into a background-running setup, since it avoids restoring the full window just to check whether logging is still active.

Exporting a system report

Beyond live sensor monitoring, HWiNFO64 can generate a full static report of your system’s hardware, accessible from the main summary screen (or by briefly switching out of Sensors-only mode) through a report generation option in the toolbar, producing an HTML, text, or MHTML file listing detailed specifications for every detected component. This is distinct from the live sensor logging covered earlier, which tracks changing values over time rather than a fixed snapshot of hardware configuration.

This kind of report is genuinely useful for a few specific situations: documenting a system’s exact configuration before selling it, providing detailed hardware specifics when asking for troubleshooting help in a forum or with a manufacturer’s support team, or simply keeping a dated record of a build’s original configuration for your own reference before making future upgrades.

Generating the report takes only a few seconds even on a fully populated system, and the resulting file can be saved anywhere convenient; it’s a reasonable habit to generate and save one shortly after finishing a new build, before you’ve forgotten which specific memory kit or drive model went into it.

Comparing to lighter-weight alternatives

For anyone who finds HWiNFO64’s sensor window overwhelming even in Sensors-only mode, it’s worth remembering it isn’t the only option; CoreTemp and HWMonitor, both covered in our PC temperature monitoring software guide, offer a simpler starting point with less setup involved, at the cost of fewer sensors and no logging or Gadget features. Many people end up settling on HWiNFO64 anyway specifically because the Gadget feature, once configured, effectively hides that complexity behind a compact overlay showing only what you chose.

When the default setup won’t be enough

For very specific diagnostic needs, like isolating a rare intermittent GPU crash, the default Gadget-and-logging setup may not be granular enough on its own; HWiNFO64’s Shared Memory Support feature (in settings) allows other tools to read its sensor data directly, which some advanced overlay, recording, or automation tools use to build more customized monitoring pipelines than HWiNFO64’s own interface supports natively.

Systems with unusual or very new hardware, particularly a motherboard model released after HWiNFO64’s last update, may show incomplete sensor support until the developer adds compatibility; checking for a newer HWiNFO64 build is the standard fix, since sensor support additions are a regular part of its update cycle rather than a rare occurrence.

Customizing the Gadget’s appearance

Once a Gadget window has a few sensors added, right-clicking its background opens options for adjusting font size, background transparency, and whether it stays always-on-top of other windows; a fully transparent background with a readable font size against your desktop wallpaper is a common preference, letting the numbers sit unobtrusively in a screen corner without a visible box around them.

The Gadget also supports a compact single-row layout versus a stacked multi-row layout depending on how many sensors are added and how much screen space you’re willing to dedicate to it; for a two or three sensor selection, a single horizontal row along a screen edge tends to be the least visually intrusive option for regular gaming use.

Position is saved automatically between sessions once the sensor window’s settings have been saved, mentioned earlier in the troubleshooting section, so a Gadget dragged to a specific corner will reliably reopen in that same spot on subsequent launches rather than resetting to a default position each time.

Troubleshooting setup issues

If GPU sensors are missing after setup, revisit the initial or general settings for the GPU support checkbox mentioned earlier; it is occasionally left unchecked either during first launch or after certain updates reset preferences, and re-enabling it usually requires restarting the sensor window to take effect.

A Gadget window that disappears after a reboot, rather than persisting with its saved sensor selection, usually means the settings were not saved before closing; use the sensor window’s dedicated “Save settings” option (rather than just closing the window) if you want Gadget configuration and logging preferences to persist across restarts.

If logging produces a CSV file with blank or inconsistent columns partway through, this can happen if a sensor briefly became unavailable during the log (for example, a drive being ejected mid-session); this is a logging artifact rather than a sign of a hardware fault, though it’s worth confirming the drive or component in question is otherwise working normally.

Slow startup times, particularly noticeable on systems with many drives or a complex RGB ecosystem, usually trace back to sensor enumeration taking longer on more complex hardware configurations; this is normal behavior rather than a bug, though switching to Sensors-only mode (if not already enabled) reduces the startup work HWiNFO64 has to do.

Frequently asked questions

Should I choose the installer or the portable version?

The portable ZIP version needs no installation and leaves no registry entries, a reasonable choice if you just want to run occasional checks; the installer version is more convenient if you plan to use HWiNFO64 regularly and want it available from the Start menu.

What is the difference between Sensors-only mode and the full summary screen?

Sensors-only mode skips straight to the live sensor panel and is faster to load, while the full summary screen shows detailed hardware specifications first, useful mainly the first time you want a full system inventory.

Can HWiNFO64 run automatically at Windows startup?

Yes, its settings include an option to launch at Windows startup, and it can be set to start minimized to the system tray so it runs in the background without an open window.

Does HWiNFO64 work with laptops?

Yes, though laptop sensor support varies more by manufacturer than desktop motherboards do, and some laptop vendors limit which sensors are exposed to third-party software, so certain rows may show no data depending on the model.

Is there a way to reduce how much screen space HWiNFO64 takes up?

Yes, the Gadget feature lets you build a small floating overlay showing only the specific sensors you choose, rather than keeping the full sensor window open, which is the setup most people settle on after initial configuration.

Daniel Kovac, Components Editor, runs HWiNFO64’s logging feature on every cooler and case review conducted in the thermal chamber, since a properly configured Gadget and CSV log catches thermal behavior a quick glance during testing would otherwise miss. Once you’re comfortable reading these sensors, our guides to CPU coolers and case fans cover the hardware side of keeping those numbers in a healthy range.