sodcalculator

10 Tech How-To

Fix hwinfo64 sys Driver Cannot Load

Guide 10-8165 · Updated · Step by step

If you see “hwinfo64.sys driver cannot load� on Windows, the fix is usually to disable Memory Integrity in Windows Security or update the driver to a signed version. This error appears when Windows blocks an unsigned or incompatible kernel driver, and it stops HWiNFO from reading system sensors until resolved.

What Causes the hwinfo64.sys Error

Windows 10 and 11 enforce driver signing by default. When HWiNFO installs its kernel driver (hwinfo64.sys), the operating system checks whether the driver is digitally signed and compatible with the current build. The “cannot load� message appears when:

  • Memory Integrity (HVCI) is enabled and blocks the driver.
  • The driver is outdated and not signed for the current Windows version.
  • Third-party antivirus or security software interferes with driver loading.
  • The driver file is corrupted or partially installed.
  • Windows Update has changed kernel policies.

Memory Integrity is the most common trigger. It is a Windows Security feature that prevents untrusted drivers from running, and it often blocks HWiNFO’s driver even when the driver is valid.

How HWiNFO Uses a Kernel Driver

HWiNFO is a system monitoring tool that reads CPU temperature, fan speeds, voltages, and other sensor data. To access low-level hardware registers, it uses a kernel-mode driver that runs with high privileges. This driver communicates directly with the motherboard’s Super I/O chip and CPU thermal sensors. Windows treats kernel drivers with extra caution because a faulty driver can crash the system or create security holes. HWiNFO’s driver is signed, but Windows may still block it if Memory Integrity is on or if the driver version is older than the Windows build.

Fix 1: Disable Memory Integrity

This is the most effective fix for the “hwinfo64.sys driver cannot load� error. Memory Integrity, also called Hypervisor-protected Code Integrity (HVCI), blocks drivers that are not compatible with the feature. HWiNFO’s driver may be signed but not HVCI-compatible, so Windows refuses to load it.

  1. Open Windows Security (search for it in the Start menu).
  2. Go to Device Security.
  3. Under Core Isolation, click Core Isolation details.
  4. Toggle Memory Integrity to Off.
  5. Restart your computer.

After restarting, launch HWiNFO again. The driver should load. If you prefer to keep Memory Integrity on, try updating HWiNFO first—newer versions may have an HVCI-compatible driver.

Fix 2: Update HWiNFO to the Latest Version

HWiNFO releases frequent updates to keep the driver signed and compatible with Windows changes. An outdated driver is a common cause of the error, especially after a major Windows update.

  1. Go to the official HWiNFO website (hwinfo.com).
  2. Download the latest stable release.
  3. Run the installer and choose Upgrade if prompted.
  4. Restart your computer.

If you are using the portable version, download the new portable ZIP and replace the old files. Always back up your HWiNFO settings (they are stored in the same folder for portable versions) before replacing.

Fix 3: Reinstall the Driver Manually

If updating does not help, the driver file may be corrupted. Reinstalling it manually can resolve the issue.

  1. Close HWiNFO completely (check the system tray).
  2. Open Device Manager (right-click Start → Device Manager).
  3. Go to View → Show hidden devices.
  4. Expand Non-plug and Play Drivers.
  5. Look for HWiNFO Kernel Driver or similar.
  6. Right-click it and select Uninstall device.
  7. Restart your computer.
  8. Install HWiNFO again (or run the portable version).

This forces Windows to re-register the driver from scratch.

Fix 4: Check for Third-Party Antivirus Interference

Some security suites block kernel drivers even if they are signed. If you use a third-party antivirus, temporarily disable its real-time protection and try launching HWiNFO. If it works, add HWiNFO and its driver folder to the antivirus exclusions. Common exclusion paths include:

  • C:\Program Files\HWiNFO64
  • C:\HWiNFO64 (portable version)

Do not disable your antivirus permanently. Only disable it for testing, then re-enable it after adding the exclusion.

Fix 5: Use the HWiNFO Safe Mode

HWiNFO has a built-in “Safe� mode that uses a less invasive driver. This can bypass the loading error while still providing most sensor data.

  1. Open HWiNFO.
  2. In the startup window, check Safe mode (it is a checkbox at the bottom).
  3. Click Run.

Safe mode may disable some advanced features like RAID or NVMe temperature reporting, but it is a reliable workaround if you cannot disable Memory Integrity.

Frequently Asked Questions

Is it safe to disable Memory Integrity?

Disabling Memory Integrity reduces protection against malicious drivers, but it does not make your system inherently insecure. Most users run Windows without it enabled. If you are concerned, update HWiNFO to the latest version first—newer versions may support HVCI, allowing you to keep Memory Integrity on.

Why does the error appear only after a Windows update?

Windows updates can change kernel policies or require drivers to be re-signed. HWiNFO’s driver may be older than the new Windows build, so Windows blocks it. Updating HWiNFO usually resolves this.

Can I use HWiNFO without the kernel driver?

Yes, HWiNFO can run in “sensor-only� mode without the kernel driver, but you will lose access to many hardware sensors. The Safe mode is a better option because it still uses a driver that is less likely to be blocked.

Does this error affect other monitoring tools?

Yes, other tools that use kernel drivers (like CPU-Z or AIDA64) can show similar errors. The fixes above apply to those tools as well, especially disabling Memory Integrity or updating the software.

What if none of these fixes work?

If the error persists, try running HWiNFO as administrator. Right-click the HWiNFO executable and select “Run as administrator.� If that fails, check Windows Event Viewer for the exact error code and search for it on the HWiNFO forum. A clean boot (disabling non-Microsoft services) can also help identify a conflicting program.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →