-
-
Save jaxFF/7e9e74279a75900d0908536c5b18566b to your computer and use it in GitHub Desktop.
| >hwinfo64.exe | |
| 000000000022005C:3D->90 | |
| 000000000022005D:00->90 | |
| 000000000022005E:2E->90 | |
| 000000000022005F:93->90 | |
| 0000000000220060:02->90 | |
| 0000000000220061:0F->E9 | |
| 0000000000220062:86->81 | |
| 0000000000220063:80->00 |
| >hwinfo64.exe | |
| 0000000000232818:3D->90 | |
| 0000000000232819:00->90 | |
| 000000000023281A:2E->90 | |
| 000000000023281B:93->90 | |
| 000000000023281C:02->90 | |
| 000000000023281D:0F->E9 | |
| 000000000023281E:86->81 | |
| 000000000023281F:80->00 |
seems to be working with v8.45-5950 Beta but will know after 12 hours, thanks so much for the work!!
It stopped working in version 8.46.
It stopped working in version 8.46.
Yeah I got the notification it stopped working as well. :/ You can either grab this .AHK script or use the .exe which does the same thing. It just auto restart HWINFO after 12 hrs. Working for me for now... I will never support this devloper after what I've seen him post on the original fork of this auto hot key mod. https://github.com/Kaan88/HWiNFO-12-hour-limit-refresh
Original fork where the HWINFO dev posted (He deleted everything isn't working use this new fork from above link.): SoFMeRight/HWiNFO_Refresh#1
It stopped working in version 8.46.
Yeah I got the notification it stopped working as well. :/ You can either grab this .AHK script or use the .exe which does the same thing. It just auto restart HWINFO after 12 hrs. Working for me for now... I will never support this devloper after what I've seen him post on the original fork of this auto hot key mod. https://github.com/Kaan88/HWiNFO-12-hour-limit-refresh
Original fork where the HWINFO dev posted (He deleted everything isn't working use this new fork from above link.): SoFMeRight/HWiNFO_Refresh#1
Thanks for the alternative.
I tried it, but the CPU usage is constantly like this image.
The update didn't require any updates in my environment, so I reverted to version 8.44.
It stopped working in version 8.46.
Yeah I got the notification it stopped working as well. :/ You can either grab this .AHK script or use the .exe which does the same thing. It just auto restart HWINFO after 12 hrs. Working for me for now... I will never support this devloper after what I've seen him post on the original fork of this auto hot key mod. https://github.com/Kaan88/HWiNFO-12-hour-limit-refresh
Original fork where the HWINFO dev posted (He deleted everything isn't working use this new fork from above link.): SoFMeRight/HWiNFO_Refresh#1Thanks for the alternative.
I tried it, but the CPU usage is constantly like this image.
The update didn't require any updates in my environment, so I reverted to version 8.44.
Huhhh? What CPU is that? Why the most on my system I just tested the most I saw using that .exe and the actual .ahk script using AutoHotkey itself most I saw is 0.2% It's a hotkey script it shouldn't be using that much CPU utilization wtf.
Huhhh? What CPU is that? Why the most on my system I just tested the most I saw using that .exe and the actual .ahk script using AutoHotkey itself most I saw is 0.2% It's a hotkey script it shouldn't be using that much CPU utilization wtf.
The image is from a 10900k machine, but the same phenomenon occurs on a 9900X3D machine as well.
However, neither machine experienced any problems on VMware.
Both machines are running Server 2025 26100.4652.
Both machines have been customized to disable numerous OS security features, including memory integrity, and driver signatures are also disabled via F7, so it's likely a problem with my environment.
This month's OS update was unusually bug-free, so I updated for the first time in 10 months.
26100.32690
Both computers are now working normally, and the CPU issue described above has disappeared.
It seems the problem was caused by the OS version being too old.
Sorry for the trouble.
It stopped working in version 8.46.
Yeah I got the notification it stopped working as well. :/ You can either grab this .AHK script or use the .exe which does the same thing. It just auto restart HWINFO after 12 hrs. Working for me for now... I will never support this devloper after what I've seen him post on the original fork of this auto hot key mod. https://github.com/Kaan88/HWiNFO-12-hour-limit-refresh
Original fork where the HWINFO dev posted (He deleted everything isn't working use this new fork from above link.): SoFMeRight/HWiNFO_Refresh#1Thanks for the alternative.
I tried it, but the CPU usage is constantly like this image.
The update didn't require any updates in my environment, so I reverted to version 8.44.
Huhhh? What CPU is that? Why the most on my system I just tested the most I saw using that .exe and the actual .ahk script using AutoHotkey itself most I saw is 0.2% It's a hotkey script it shouldn't be using that much CPU utilization wtf.
It stopped working in version 8.46.
Yeah I got the notification it stopped working as well. :/ You can either grab this .AHK script or use the .exe which does the same thing. It just auto restart HWINFO after 12 hrs. Working for me for now... I will never support this devloper after what I've seen him post on the original fork of this auto hot key mod. https://github.com/Kaan88/HWiNFO-12-hour-limit-refresh
Original fork where the HWINFO dev posted (He deleted everything isn't working use this new fork from above link.): SoFMeRight/HWiNFO_Refresh#1Thanks for the alternative.
I tried it, but the CPU usage is constantly like this image.
The update didn't require any updates in my environment, so I reverted to version 8.44.
Welp looks like this actually doesn't re-trick the 12 hour timer after a restart using these AutoHokey scripts, I just now noticed so I'm just going to have to go back to previous version I guess... Damn.
I would be so happy if there could be an update :)
Hey, the behavior sounds normal to me. I don't have any antivirus installed (including Windows Defender, I removed it completely) so I don't have such problems, but you can safely exclude the dll loader from Defender. If not, you can download the original Ultimate ASI Loader's winmm.dll, but you'll have to rename my patch from .dll to .asi for it to work, since my source code modifies the Ultimate ASI Loader to load my file specifically.