keyhunt not good
you should learn to configure it, defaul thread subrange is 32 bits, for small ranges with multiple threads you should lower the N value with "-n number" if the range is less than 1 Million keys you should use -n 0x10000
where 0x10000 its a 16 bits subrange per thread
Look

Found i less than a second
are you key hunt creator?
nice too meet you
It was my mistake, I apologize, dear friend
ok , thank you
I meant
https://github.com/WanderingPhilosopher/KeyHuntCudaClienti use of first version keyhunt cuda
Zero clues of how or what you ran, but with a single CPU core, using keyhunt-cuda, it is found pretty much as the program starts:
KeyHunt-Cuda v1.08
COMP MODE : COMPRESSED
COIN TYPE : BITCOIN
SEARCH MODE : Single Address
DEVICE : CPU
CPU THREAD : 1
SSE : YES
RKEY : 0 Mkeys
MAX FOUND : 65536
BTC ADDRESS : 1E5V4LbVrTbFrfj7VN876DamzkaNiGAvFo
OUTPUT FILE : Found.txt
Start Time : Sat May 25 10:11:49 2024
Global start : 20000000000000000 (66 bit)
Global end : 21000000000000000 (66 bit)
Global range : 1000000000000000 (61 bit)
[00:00:02] [CPU+GPU: 5.28 Mk/s] [GPU: 0.00 Mk/s] [C: 0.000000 %] [R: 0] [T: 10,706,944 (24 bit)] [F: 1]
BYE
SO maybe you entered wrong things/flags when trying to run the program.