LibreHardwareMonitor.sys

[bjm]

@Jonte_H

No @bjm , im just an user, not creator of the program.
I have already tried everything you showed in this post with no luck.
Every time i turn on Block vulnerable kernel drivers again, Norton blocks/removes the file.
I just want to exclude this file from Norton, and this one only since i trust it.

Hello @Jonte_H
Yes, I’ve tried with same results.
Yes, with Block vulnerable kernel drivers enabled, Norton blocks librehardwaremonitor.sys file loading.
I’ve tried with other Block vulnerable kernel drivers reports…with same results.
Sorry…

• maybe, support knows a work-around

fwiw ~ this process [here] works for me to reach:
Norton support via Social Support | Chat | Phone [here]

Please let us know your progress

================================================

AI
Avast has a feature that allows it to “block vulnerable drivers,” meaning it actively identifies and prevents potentially exploitable drivers from loading onto your system, essentially protecting against attacks that might leverage outdated or compromised drivers to gain access to your computer.

Key points about Avast’s vulnerable driver blocking feature:

• Function: This feature scans for drivers with known vulnerabilities and prevents them from loading into the operating system kernel memory.
• User notification: When Avast detects a vulnerable driver, it will typically alert the user.
• Access: To manage this setting, you can navigate to Avast’s settings menu, usually found under “General” or “Troubleshooting” depending on your Avast version.

Why is this important?

• Security benefit:
  Vulnerable drivers can be exploited by malware to gain elevated privileges on a system, so blocking them is a crucial security measure.

• Protection against advanced attacks:
  Cybercriminals often target vulnerable drivers in sophisticated attacks, making this feature a valuable defense against such threats.

Why is Avast so annoying with driver blocking
[…]
Avast employee - March 2023
The reason for exclusions not working is that they’re not implemented yet. The vulnerable driver blocking is a separate feature, not based on “regular” scans, so exclusions have to be implemented separately (plus a separate UI controls should be added).

It’s going to happen… but for now, you can simply disable the vulnerable driver blocking completely - in Troubleshooting, under Enable Self-Defense. (Since you’ll already have a popular vulnerable driver running, it doesn’t matter much if you exclude just that one or disable the feature completely - the door for malware is wide open anyway.)

Avast employee - March 2023
How exactly they are detected, I’m not sure - but it’s definitely not just a generic heuristics, it’s targeting specific drivers.
I’m told the WinRing driver (used by FanControl) is a popular driver that allows any non-privileged user arbitrary write access to hardware and physical memory. So this driver allows anybody to do… well, anything, including e.g. disabling the AV.
[…]
https://community.avast.com/t/why-is-avast-so-annoying-with-driver-blocking/771148

Avast team - November 2023
My name is Jan, and I’m with the Avast senior technical support team, I realize there’s been a delayed response to your query, and I apologize.

I see you have questions about the Avast vulnerable kernel driver detection, which I would like to clarify for you.

The detection dialogue comes from the Avast Premium Security Self-Defense module that protects the application installation from deactivation or uninstallation. It detected and blocked an exploitable driver in your system. It’s very unlikely this would be a false positive because this is usually a very accurate type of detection.

There isn’t any other workaround than disabling the “Block vulnerable kernel drivers” feature if you want to use the application despite our recommendations.
Open Avast Premium Security application and navigate → Menu → Settings → General → Troubleshooting → Enable Self-Defense → Block vulnerable kernel drivers.
However, it leaves the device unprotected and vulnerable.
[…]
https://github.com/winsiderss/systeminformer/issues/1908