Reverse engineered HWiNFO 12-hour shared memory limit patch

patch_v7.40_5000.1337

>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

patch_v7.46_5110.1337

>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

You've reminded me to mention that it seems even though you'll still see [12-HOUR TIME LIMIT] next to Shared Memory support as long as you have it ticked it should basically be an infinite 12 hours if that makes sense now. I'm not sure if that warning is supposed to disappear normally but with this patch it seems to have never unchecked itself so far for me after 9 months or so.

Thanks so much!!

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!

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

Might need to override all exploit protection settings (it will say 23 system overrides when done make sure to enable all over ride then disable any feature below the override) because the winnmm.dll or version.dll is most likely being prevented from injection into the program... Sry just woke up excuse the bad grammar.

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.