-
-
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 |
Hello @EricPlayZ sorry but i did try the DLL and windows defender virus & threat protection did disable itself right after.
I couldn't reproduce it in the successive run.
Did you experience this behavior?
I checked the windows update to see if there was an update who could have caused this but couldn't find any for today.
Could this dll loader cause this?
not suspecting you, just got scared
Hello @EricPlayZ sorry but i did try the DLL and windows defender virus & threat protection did disable itself right after. I couldn't reproduce it in the successive run. Did you experience this behavior? I checked the windows update to see if there was an update who could have caused this but couldn't find any for today. Could this dll loader cause this? not suspecting you, just got scared
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.
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 :)
Well I have been using HWInfo with my own DLL (written in FreePascal instead of C++). I got really pissed off when HWInfo went out of their way to block this. OPs code is still great, it's just that the HWInfo devs are using mechanics to block his DLL from loading. (and mine ofc). I have made a patcher for my own use but here is how you can do it yourself without relying on another binary.
-
Clear Dependent Load Flags. (This is what is blocking the DLL from getting loaded)
a) Get PE-Bear from github. It's a tool to edit binary metadata (among other things)
b) Open it and load the target exe file.
c) Go toLoadConfigtab and scroll down to find the "DependentLoadFlags" parameter. Set its value from 800 to 0 [technically it's getting changed from 0x800 to 0x000]
d) Save the edited binary with say "target-step1.exe" -
While the above is easy, the next one requires a bit of caution. Get HxD or any hex editor and open the binary generated from the previous step. Initiate a search for
uiAccess="true", you will land on some XML. Now move your cursor to the letter"u" of uiAccessand replace the following letter by letter. Make sure the no of characters post edit remain the same. Save the new file as original filename (take backup of the original binary ofc) , and you are done. [why do we need this step?? Signatures that's why]
uiAccess="true"></requestedExecutionLevel>
uiAccess="false"/><!--xxxxxxxxxxxxxxxxx-->
Note: Since you have edited the binary the signature is no longer valid, but that shouldn't be a problem (cuz you edited it). This is still better than static patches because you can repeat it for the next version without depending on someone to write a patch (or ship something nefarious with it). And goes without saying if you are in a commercial space please buy a license to support the devs. Will share a trimmed down ver of my DLL, the day OP's stop working :)
Also sha256 hashes of DLLs shared by OP
527fe83cdfe10a86d4700b8c1d858901b6c2e65548d2c4abb6952c4d76d59734
2ace255421172772f6606f3bd870cee87a983d7be4ad6fb43bda979ad9bbbde0
Edit: With OP I mean EricPlayZ
I haven't been able to verify if it actually works, but if anyone is interested:
build 848
Pattern:
48 3D 00 2E 93 02 76 7B -> 48 3D 00 2E 93 02 EB 7B
Thanks to takenox for the guide on how to "disable" uiAccess
I haven't been able to verify if it actually works, but if anyone is interested: build 848 Pattern: 48 3D 00 2E 93 02 76 7B -> 48 3D 00 2E 93 02 EB 7B Thanks to takenox for the guide on how to "disable" uiAccess
I've done the steps provided above to disable or set to 0 for the DependentLoadFlags parameter, saved .exe as target-step1.exe like he mentioned now I am using HxD to edit the values. I search for Hex value of "48 3D 00 2E 93 02 76 7B" in all directions of the executable and I click on "Search All" yet I am not finding anything. I've tried multiple times that doesn't exist in this executable or am just being plain retarded right now I am so confused why I can't find this if you somehow provided these values, where or what build is this from exactly????? I'm so confused right now LMAO.
I am genuinely confused asf rn..... So instead of tryna patch the 48 3D 00 2E 93 02 76 7B to 48 3D 00 2E 93 02 EB 7B, can't I simply use my edited .exe with the DependantLoadFlags disabled or set to 0, then try and use your .dll again to keep reactivating the 12 hour access like before??? What is the Hex value for? Are HEX values for people that want to do it manually without the .DLL file or having to set DependantLoadFlags to 0?????? I think im just being slow rn, apologies lmao.
Edit - 12 hrs later: Got it working with your .dll combined with disabling DependantLoadFlags, thank you guys for all your work! I am going to switch to LibreHardwareMonitor soon anyways, just haven't felt like pissing with anything but will soon cuz I don't see any reason why I shouldn't. Open source and I only LITERALLY USE THIS DAMNED PROGRAM TO ADD HOT SPOT TEMP SENSOR TO MSI AFTERBURNER AND THIS MF TRYNA CHARGE ME FOR THAT IS MIND BOGGLING.
Original comment below:
OH YEAH, and sorry, above I linked a fork of that AHK script but that was not the original fork that I had linked previously. Which the author actually removed the entire .exe and script, which is insane to me that this person bowed down to this idiot "developer". He may be a developer but not a very kind or logical one at that.
Here is the real reason why you and I should never support this individual. The dev does not understand that even if he claims simple AHK script that clicks the button for you is "violating" hwinfo's TOS, it is not illegal nor warranty scare-baiting people into removing their work. What a bunch of bullshit if I've ever heard of one, "violates hwinfo's terms". IT IS NOT ILLEGAL IS IT????? A SCRIPT THAT CLICKS A BUTTON FOR YOU??????? ARE YOU KIDDING ME RIGHT NOW?
There is no way to know who is clicking the damned button, AHK script or not. Either way, it doesn't work anymore so it's useless but it is still a huge flag to me to see the actual developer posting this "Issue" on his AHK script. 🤦🤬
The balls this guy has, wow now I'm just pissed all over again reading this. Imagine now if this man had some common sense / logic up there what he could actually achieve with that. I mean he made HWINFO so im not tryna say he's not logical in a sense, but he's not logical enough to understand how this makes him look from an outside perspective, and not logical enough to understand this doesn't violate any kind of fucking terms..........
If this developer manages to be following this entire conversation, you can eat a big fat one. 🖕
(Part of my 12 hours later edit - You can ignore my rant sorry I went off here about unrelated DENUVO DRM for no apparently reason. Just have been getting pissed off recently about some things currently.)
Most people like us in here, already have our minds made up with purchasing this kind of thing permanently instead of keep clicking o nthe free trial button, only cuz we already made that decision long ago and we stick with it. Adding this kind of thing into your programs to try and stop us from doing this isn't helping anyone, if anything it makes them looks worse and current ppl to simply go looking for free alternatives, you cannot force these kind of ppl like myself into purchasing anything unfortunately no matter what you do...... It makes them look like an ass too on top of it all, but maybe that's just my own neg ative perspective on it idfk.
I am sorry for my rant, I am getting flashbacks to these Game devs adding Denuvo to their games LITERALLY LAST MINUTE RIGHT BEFORE PRE-LOAD or right before THE ACTUAL RELEASE they say OH OUR GAME HAS DENUVO. That is right there is why I never PRE-ORDER OR PURCHASE ANY GAME ESPECIALLY FROM DEVS THAT ARE KNOWN TO USE DENUVO. HELL WITH ALL OF THAT BS, if i purchase MY DAMNED GAME I BETTER OWN THE FILES AND BE ABLE TO PLAY IT 30 DAYS+ WITHOUT RE-CONNECTING TO TO THE INTERNET AND HAVING TO FETCH A NEW "DENUVO TOKEN" TO RE-VALIDATE THE GAME JUST TO LAUNCH MY GAME.
WHAT AMAZING TIMES WE'RE LIVING ON HOLY HELL. And these game companies anymore still add denuvo, even now with all of the bypasses and all of the voices38 "denuvo bypasses" that have been releasing, they are still pushing Denuvo for no apparenty reason. They think they're saving themselves money doing it, but they would be saving a lot less by not even bothering to incorpate it at all now considering how fast it's bypassed in a few hours or a few days now!!!!!!! Imbecielos in this world, I am sorry but I am not sorry actually for what I just said about Denuvo though LOL.
I uploaded a HWInfo auto restart script to my repo, made for AHK v2. Give it a go if you want, the more the merrier, will iron out issues(if any) faster with more people using it. So far it has run for 1 cycle on my PC and looks like everything is working fine.
@tooknox
Could you guide me in more detail on how to perform each step?
For example, after downloading PE-Bear, what is the exact name of the .exe file I should select?
And in the HxD tool, should I move to the character "u" (before or after it) and replace each character with a random character while maintaining the required length, or should I change it like the command line ["uiAccess="true"....change to..."] that you provided?
And what does the line "48 3D 00 2E 93 02 76 7B -> 48 3D 00 2E 93 02 EB 7B" provided by @0xZeOn mean?
I am not a programmer, so I hope you can guide me in detail and understand my lack of knowledge.
@tooknox Could you guide me in more detail on how to perform each step?
For example, after downloading PE-Bear, what is the exact name of the .exe file I should select?
And in the HxD tool, should I move to the character "u" (before or after it) and replace each character with a random character while maintaining the required length, or should I change it like the command line ["uiAccess="true"....change to..."] that you provided?
And what does the line "48 3D 00 2E 93 02 76 7B -> 48 3D 00 2E 93 02 EB 7B" provided by @0xZeOn mean?
I am not a programmer, so I hope you can guide me in detail and understand my lack of knowledge.
Don't have too much time rn but I can tell you it's probably not worth it cuz I followed every step and have edited HeX values on .exes in past yet couldn't find value: 48 3D 00 2E 93 02 76 7B
Basically that means you're finding the value in the HxD HeX editor program after you've used PE-BEAR to fix the .exe.
To find the HeX value you press Ctrl+F then click on Search All for HeX value (without quotes): "48 3D 00 2E 93 02 76 7B" and change that entire line to exactly: "48 3D 00 2E 93 02 EB 7B"
You can try following his steps it's not too difficult the most difficult part is the part I just mentioned with editing the HeX values...
Apologies, if I had more time I'd explain each step more thoroughly but I did everything a few days ago and yet that HeX value was no where in the .exe so I suspect maybe the HeX values changed or need updated or else perhaps I did open the incorrect.exe or mix my .exe's up whenever opening in HxD to edit the HeX values.
Either way somehow the .DLL file from this repo also works just fine for now so I'm wondering maybe I did screw up somewhere in the process here. Because I thought, or my assumption was that the winmm.dll modified these HeX values in memory. Or maybe it hooks into the .exe a different method I'm unaware of that doesn't involve these HeX values and I'm being stupid right now then lol. (Sorry for my ignorance, I'm no programmer either lmao.)
Note, that the technique used here (DLL sideloading) is commonly used by malware. A similar technique was recently used to hack CPU-Z, although with a malicious payload in the DLL. I'm not saying that this might contain any malicious payload, and I'm not intending to analyze it.
Neither am I going to explain the license terms or argue with certain individuals but note, that crossing certain boundaries can have consequences.
Note, that the technique used here (DLL sideloading) is commonly used by malware. A similar technique was recently used to hack CPU-Z, although with a malicious payload in the DLL. I'm not saying that this might contain any malicious payload, and I'm not intending to analyze it.
Neither am I going to explain the license terms or argue with certain individuals but note, that crossing certain boundaries can have consequences.
Winmm.dll is widely used in tons of things for memory hijacking and other such things I just know that's one of them from my simple knowledge over the years.
Anyways what's your point? Are you windows defender now or what?
Nobody asked you what the .DLL does why the hell out of anyone here would anyone expect the creator of HWinfo to analyze the .DLL file?
You're still off you're rocker with these goofy replies I see and can match the energy.
I still switched to LibreHardwareMonitor anyways because this is not worth it at all when there's an open source alternative when I only need it for HotSpot temp sensor overlay in-game using MSI afterterburner. Not quite sure what I'm doing use the wrong program to begin with.... That's my fault though there.
My point is before all of this non-sense I would've bought a perpetual license for lifetime one day if I could since your program does have some nice features I might use one day...
But after seeing your opened Issue which caused the creator of other AHK script to take it down I am definitely never going to now. Not that it matters to you anyways.
I have no gripe with you patching the "vulnerabilities" in your license to prevent stuff like this from working. That's totally understandable and expected from a dev with this sort of "feature" or paywalled feature I should just say in your program.
But going out of your way to fear monger some rando on a GitHub repo trying to automate the 12-hour reset counter is mind-boggling insane work to me.
Now especially after you're coming in here spewing common sense for no apparent reason adding absolutely nothing to answer any of the questions pertaining to my paragraph above I do not feel 1 bit of regret saying what I just said right now.
Bye now I'm going to decisively ignore any of your goofball replies that add nothing to anything if I can manage in the future
So it's not any disrespect towards you it's just the fact, or more specifically the methodology you go about choosing to handle these kind of things as a developer.
I think you need to, in my opinion fix in general or at least reflect upon your metholdogies here and if they're really helping anyone positively or not.
If you truly cared about HWinfo users, you would analyze the .DLL and see if it's malicious, to be more frank with you, instead of spewing your typical fear-mongering generic nonsense.
For your situation I would actually either ignore it number 1 and accept that no matter what you do u cannot stop people from trying to bypass license requirements. In general there's always going to be people who are trying to bypass licenses and these sort of stupid pay-walled "features". So no matter what you do someone will come along and get around it over and over and over and over as long as the feature is in the program you have running on your PC someone will come along and activate it...
Anyways so u go right ahead and lecture us all on the "malware" potentiality and try to fear monger us all instead of bothering to even begin to scratch any of my questions. But it is totally not surprising to me though, no qualms I understand you're protecting your program but my point still stands.
Accept the fact ppl are going to attempt to bypass your program's BS 12-hour time limit and move on. I don't see how it's worth a headache for either side here. Just keep patching out the memory they use and call it a day.
But why bother going out of your way to fearmonger more, exactly like you're still doing right now with your last reply?????
God, you devs just don't comprehend this because you aren't the ones on the other end. We are the ones having to deal with the hassle of installing this software, only to realize the single useful feature is locked behind a 12-hour paywall.
And yet here you are, still lurking around seeking to find ppl bypassing your license just to fearmonger some more.
Go crawl back home and shh already plz, as respectfully as possible. I don't think you understand where I'm coming from so hopefully now you can, even if it's a fractional amount then that's good in my books.
If you even read all of this which I highly doubt.....
Note, that the technique used here (DLL sideloading) is commonly used by malware. A similar technique was recently used to hack CPU-Z, although with a malicious payload in the DLL. I'm not saying that this might contain any malicious payload, and I'm not intending to analyze it.
Neither am I going to explain the license terms or argue with certain individuals but note, that crossing certain boundaries can have consequences.
Also, your example is completely wrong anyway. The CPUID incident was a compromised web server and mirror host on their own official site distributing a malicious package. It had absolutely nothing to do with community made DLL bypasses like this even if they can potentially be "malware" so why bring up CPU-ID?
https://gist.github.com/N3mes1s/b5b0b96782b9f832819d2db7c6684f84
Equating a Russian supply-chain attack on CPUID to a local winmm.dll paywall bypass is a massive stretch, and we both know it. You can stop playing internet security guard in my mentions. I’ve already moved on to LibreHardwareMonitor anyway. I'm out, peace...
So to sum it up: you openly admit you refuse to analyze the .DLL file, and instead you're just using vague, pseudo-intellectual corporate threats to fear-monger some more. Glad we've gotten this far, thanks for all your help I guess.
Anyways, lmk if u manage to wake up and actually analyze this .DLL file yourself instead of randomly trying to argue with me about something that doesn't have anything to do with the .DLL within this repo specifically.
https://gist.github.com/N3mes1s/b5b0b96782b9f832819d2db7c6684f84
Equating a Russian supply-chain attack on CPUID to a local winmm.dll paywall bypass is a massive stretch, and we both know it. You can stop playing internet security guard in my mentions. I’ve already moved on to LibreHardwareMonitor anyway. I'm out, peace...So to sum it up: you openly admit you refuse to analyze the .DLL file, and instead you're just using vague, pseudo-intellectual corporate threats to fear-monger some more. Glad we've gotten this far, thanks for all your help I guess.Anyways, lmk if u manage to wake up and actually analyze this .DLL file yourself instead of randomly trying to argue with me about something that doesn't have anything to do with the .DLL within this repo specifically.
Note, that the technique used here (DLL sideloading) is commonly used by malware. A similar technique was recently used to hack CPU-Z, although with a malicious payload in the DLL. I'm not saying that this might contain any malicious payload, and I'm not intending to analyze it.
Neither am I going to explain the license terms or argue with certain individuals but note, that crossing certain boundaries can have consequences.Winmm.dll is widely used in tons of things for memory hijacking and other such things I just know that's one of them from my simple knowledge over the years.
Anyways what's your point? Are you windows defender now or what?
Nobody asked you what the .DLL does why the hell out of anyone here would anyone expect the creator of HWinfo to analyze the .DLL file?
You're still off you're rocker with these goofy replies I see and can match the energy.
I still switched to LibreHardwareMonitor anyways because this is not worth it at all when there's an open source alternative when I only need it for HotSpot temp sensor overlay in-game using MSI afterterburner. Not quite sure what I'm doing use the wrong program to begin with.... That's my fault though there.
My point is before all of this non-sense I would've bought a perpetual license for lifetime one day if I could since your program does have some nice features I might use one day...
But after seeing your opened Issue which caused the creator of other AHK script to take it down I am definitely never going to now. Not that it matters to you anyways.
I have no gripe with you patching the "vulnerabilities" in your license to prevent stuff like this from working. That's totally understandable and expected from a dev with this sort of "feature" or paywalled feature I should just say in your program.
But going out of your way to fear monger some rando on a GitHub repo trying to automate the 12-hour reset counter is mind-boggling insane work to me.
Now especially after you're coming in here spewing common sense for no apparent reason adding absolutely nothing to answer any of the questions pertaining to my paragraph above I do not feel 1 bit of regret saying what I just said right now.
Bye now I'm going to decisively ignore any of your goofball replies that add nothing to anything if I can manage in the future
So it's not any disrespect towards you it's just the fact, or more specifically the methodology you go about choosing to handle these kind of things as a developer.
I think you need to, in my opinion fix in general or at least reflect upon your metholdogies here and if they're really helping anyone positively or not.
If you truly cared about HWinfo users, you would analyze the .DLL and see if it's malicious, to be more frank with you, instead of spewing your typical fear-mongering generic nonsense.
For your situation I would actually either ignore it number 1 and accept that no matter what you do u cannot stop people from trying to bypass license requirements. In general there's always going to be people who are trying to bypass licenses and these sort of stupid pay-walled "features". So no matter what you do someone will come along and get around it over and over and over and over as long as the feature is in the program you have running on your PC someone will come along and activate it...
Anyways so u go right ahead and lecture us all on the "malware" potentiality and try to fear monger us all instead of bothering to even begin to scratch any of my questions. But it is totally not surprising to me though, no qualms I understand you're protecting your program but my point still stands.
Accept the fact ppl are going to attempt to bypass your program's BS 12-hour time limit and move on. I don't see how it's worth a headache for either side here. Just keep patching out the memory they use and call it a day.But why bother going out of your way to fearmonger more, exactly like you're still doing right now with your last reply?????
God, you devs just don't comprehend this because you aren't the ones on the other end. We are the ones having to deal with the hassle of installing this software, only to realize the single useful feature is locked behind a 12-hour paywall.
And yet here you are, still lurking around seeking to find ppl bypassing your license just to fearmonger some more.
Go crawl back home and shh already plz, as respectfully as possible. I don't think you understand where I'm coming from so hopefully now you can, even if it's a fractional amount then that's good in my books.
If you even read all of this which I highly doubt.....
Thank you for your support.
I think we probably only really need to use HWiNFO to measure the in-depth parameters of the computer system.
I find that MSI Afterburner itself does a good job of measuring FPS, temperature, usage, clock, etc., for both GPUs and CPUs, since I mainly use it to measure FPS and game performance.
I also tried LibreHardwareMonitor and it works really well, not to mention it's completely free.
But I still decided that using only MSI is fine.
In short, just use whichever software you feel most comfortable with.
Thank you for answering my question.
Best regards
Note, that the technique used here (DLL sideloading) is commonly used by malware. A similar technique was recently used to hack CPU-Z, although with a malicious payload in the DLL. I'm not saying that this might contain any malicious payload, and I'm not intending to analyze it.
Neither am I going to explain the license terms or argue with certain individuals but note, that crossing certain boundaries can have consequences.
https://gist.github.com/N3mes1s/b5b0b96782b9f832819d2db7c6684f84
@malikm After you threatened that guy to make him remove the auto restart script from his git, anything that comes out of your mouth has no more worth than diarrhea.
I forgot to mention that the warning doesn't disappear from the settings, but yes it does remain enabled 24/7! It only patches the timer, that's why. Glad to hear it works!