Cannot install the HWiNFO Driver - nonencrypted sys folders, core iso disabled, no other monitoring tools

[Martin]

Thanks! I have no idea why it flags it as positive and the details are certainly secret.
Their Defender policy is really weird, for example they flagged the vulnerable WinRing0 driver (even though they knew for years very well how dangerous it is), but 1 day later pulled the block. They never released any comment about that.

WinRing0: Why Windows is flagging your PC monitoring and fan control apps as a threat

Is it dangerous? What happens next?

www.theverge.com

 

[Username00]

Weird - the previous beta was working fine for me - now with the update to latest beta - getting the "Cannot install the HWiNFO driver !" pop-up. The only AV I have is Win 11 Defender and that's not showing anything (even with it disabled).
Tried the non-beta version - and that won't start either. Confirmed that the persistent driver option is not selected.
I recall doing something a while back to get this working - but can't remember. Any suggestions?

(using the registered pro version)

 

[polyh3dron]

Weird - the previous beta was working fine for me - now with the update to latest beta - getting the "Cannot install the HWiNFO driver !" pop-up. The only AV I have is Win 11 Defender and that's not showing anything (even with it disabled).
Tried the non-beta version - and that won't start either. Confirmed that the persistent driver option is not selected.
I recall doing something a while back to get this working - but can't remember. Any suggestions?


(using the registered pro version)

For me it took doing a lot of stupid things like removing HWiNFO from my registry, deleting the service from performance monitor, uninstalling and making sure I only install the stable release without updating to the beta after all that. Not sure what fixed it but that might fix it for you. We got another one @Martin

And yeah using the built in updater won’t get a flag from Defender. Martin seems to believe that a Defender rejection is still to blame.

 

[Username00]

For me it took doing a lot of stupid things like removing HWiNFO from my registry, deleting the service from performance monitor, uninstalling and making sure I only install the stable release without updating to the beta after all that. Not sure what fixed it but that might fix it for you. We got another one @Martin

And yeah using the built in updater won’t get a flag from Defender. Martin seems to believe that a Defender rejection is still to blame.

Update: (now I remember!) Ok - figured I would post this in case anyone else ran into a similar issue. I had forgotten that I have one of those CPU coolers with an LCD screen and in that application folder is HWiNFO (a 32bit version that's packaged with the software) that's always running to display the sensors I have on the LCD screen. That's what was locking on to a HWiNFO_x64_204.sys file in the Temp folder which was preventing me from running my regular application.

Anyway - so stopping that application - deleting the driver file in the Temp folder - enabled me to update HWiNFO to the latest beta.

Hope that helps someone.

 

[Martin]

Update: (now I remember!) Ok - figured I would post this in case anyone else ran into a similar issue. I had forgotten that I have one of those CPU coolers with an LCD screen and in that application folder is HWiNFO (a 32bit version that's packaged with the software) that's always running to display the sensors I have on the LCD screen. That's what was locking on to a HWiNFO_x64_204.sys file in the Temp folder which was preventing me from running my regular application.

Anyway - so stopping that application - deleting the driver file in the Temp folder - enabled me to update HWiNFO to the latest beta.

Hope that helps someone.

Thanks, that would explain a lot of things.
Could you please enable Debug Mode in HWiNFO and repeat the automatic update procedure while TRCC is running? Then please provide the HWiNFO64.DBG file that was created.
That should tell me what's going on internally to diagnose the problem.

 

[Martin]

Update: I have identified a potential issue that could be causing this problem.
It will be fixed in the next (Beta) build. But please note that since the currently running version performs the update process, it will require 2 updates for the fix to come into force.

 

[polyh3dron]

Thank you Martin!