HWINFO64 v.6.24 locks up my keyboard pointer on ThinkPad T450s with latest Windows 10 Pro 1909

pacman23

Member
Just updated from the previous version using the Windows installer and, as soon as I ran the program sensors, my screen pointer locked up. Plugging in a USB mouse allowed me to stop the program but the pointer again froze on screen if I unplugged the mouse. Uninstalling HWINFO64 v.6.24 resolved the issue. The previous version ran just fine.
 

Martin

HWiNFO Author
Staff member
Please try to disable the "SMBus Support" option in main Settings - "SMBus / I2C" tab and let me know if that helps.
This is just to narrow down the problem area to determine further steps how to fix this.
 

pacman23

Member
Thanks for that - I've got to leave HWINFO uninstalled just now because I've a few urgent things to do but I'll reinstall and try that out at the first opportunity.
 

pacman23

Member
I reinstalled HWINFO and disabled the "SMBus Support" option in main Settings - "SMBus / I2C" tab before running and had no pointer freezing issues. Thanks for that. I'd be interested to know why that problem occurred. I've only started usng the program very recently and the last version didn't exhibit this problem.
 

Martin

HWiNFO Author
Staff member
There used to be a problem in the last with Synaptics touchpads connected to SMBus that were not properly using the interface so when other tools attempted to communicate with other devices on SMBus it caused such issues. But this was resolved long ago, so I'm not sure if this is the same problem.
You could try to enable back SMBus support in HWiNFO and selectively try to disable particular devices via the "SMBus Device Exclusion" boxes in HWiNFO settings to determine which exact device is causing this. If you would be able to determine which one is it, I could add automatic exclusion in HWiNFO.
 

pacman23

Member
I reinstalled HWINFO and disabled the "SMBus Support" option in main Settings - "SMBus / I2C" tab before running and had no pointer freezing issues. Thanks for that. I'd be interested to know why that problem occurred. I've only started usng the program very recently and the last version didn't exhibit this problem.
 

pacman23

Member
Sorry for the duplicate post - don't know what happened. Thanks for your reply - I'll experiment when I get the opportunity and repost. Stay safe........
 
Top