I know i wasn't very active here, bc i actually stop trying anymore, since i din't discover anything new.
Last month i try do somehow guess, or make out "how activation code are made". I try chatGPT to help me and i try combination of 40 different variation of activation codes but the possibility of guessing that many variants it's almost impossible.
1ACE-6304-DD82-0000-00EC -
BE2E-FCD0-8548-0000-0071 -
069A-2FFA-1DC1-0000-0095 -
8756-85D2-1CA3-****-**39 - this codes are made in hex and in hex we got : 0 1 2 3 4 5 6 7 8 9 A B C D E F, on every single one spot ( so 16 possibilities) if we got like 8 spots to make out it would be very hard, but now we got 14 !!!
I give chatGPT every working code, and ask it to make something like that, or to understand how it was made. I think if AI will give as like 1000 variants of code (that are not the same) we could actually find couple matching codes. But man this would be a lot of trial and error XDD mostly errors
if anyone have another idea i could get some fresh look on this :,)
We tried to figure this out using ChatGPT. It wasn't just a 2-minute brainstorming session — the key idea was to try and find correlations between the hexadecimal codes and the .vs4 files. The files themselves were too large to upload for direct analysis, so ChatGPT asked me to extract the header of the .vs4 files using Windows PowerShell.
As a result, I was able to cut out a segment of the file that contains the main parameters — this became the vs4_header.bin file. At first, I only extracted this header from .vs4 files where I already knew the activation key. In those cases, the key could indeed be found — though it required a search script that ChatGPT helped me put together.
Here’s the main point:
When I created a vs4_header.bin file from a .vs4 file without a known activation key, the key couldn’t be found in it. This was always the result, and ChatGPT came to the same conclusion:
“This is exactly 20 bytes of 0xAA, which is unusual — because in earlier files, the binary version of the activation key was present at the end, and it showed actual varied byte values.
So, my conclusion was that the activation keys aren’t actually stored inside the .vs4 files — they’re likely linked or assigned only when the key is generated.This, however, doesn’t look like a real activation key — more like a placeholder or filler value, possibly something that hasn’t been overwritten yet (or maybe it’s intentionally left like that).”
I’m not a computer scientist, and I know very little about programming or how to properly interpret this kind of data — I just had time and found the topic interesting. It’s totally possible I overlooked something or made incorrect assumptions. Still, I think the idea was worth exploring, and I might dig into it further sometime later!