so, microsoft is indeed aware. but they did little to no effort because i could just use any other blacklisted or non-blacklisted key to activate and it would work just fine. lol
FYI: I heard [removed] and [removed] might work now (but I cannot confirm this)... Google each to find copies. (UPDATE: PM me and I can point you where to find [removed] tools) Note: For educational/informational use only! I have not tried it myself. Let me know if you test it.
i think i've tried xpkey (i've found out its modified date came from like 2000 or something) like days after this post but all the keys failed to validate for windows xp sp3 to really use. i might've used a version of xpkey that was designed for windows xp beta versions because they had wpa in them hence the modified date. but i've never used or heard of xpkeysp2, i'll prob see if i can use it.
it seems that microsoft might've given up or something, the key that wasnt workign for telephone activation now works for telephone again. i think it could've been an error in their servers or anything.
i tried xpkeysp2.exe and surprisingly, it works. it might still be fake though, i dont know how it generates keys like this. it might just have a whole list of keys in it and it just randomizes between the keys. i've just tested it in xp sp3 and online activation actually works too.
wtf, this just found a key in like 17 searches. it didnt work before. maybe like i said, i was using an older version of xpkey.exe because its modified date was from 2000 and this xpkey.exe as im looking at in properties says its from 2002 and its modified date is from january 25th 2003.
I doubt that it is fake, as you can modify the channel id (365 and 360 for Tablet PC/Media Center iirc; i know that there were never retail versions of those, so i guess these are meant for msdn subscribers as they work on msdn discs and from my experience they activate too)
yeah, i wanted to say something about it because i had that as an idea as soon as i started using the program and it gves me an option to change the channel id, so if i could find the channel id for retail or oem windows xp x64 professional, it might generate working keys for it. i think the product family section is just preloaded settings for the options here. nvm, i dont think that would work because you have to set the proper product family for it to start generating product keys for it since xp pro retail which is what i think the keygen is using is 76487 while xp x64 oem is 76588, i dont think this works for xp x64. if theres a keygen that identifies xp x64 oem (76588) and its a similar or an updated version of xpkeysp2.exe then it may work.
the product family does not matter when talking about the validity of the key, as it is determined by the setupp.ini (which you would find out upon using a pid checker, as those convert the key to XXXXX-[channel id]-[etc...]) also, your xpkeysp2 cannot generate oem keys, as those have "OEM" as their channel id (second section of the product id) which you cannot enter into a into a programme that (theoretically) only accepts integers from 1-999 as channel ids also, i am kinda curious as to why "xpkeysp2" (which i also found under the names "mskey4in1") can instantaneously generate a key while the other ones take their time. (even windowsxpkg on github seems to use that brute force approach, even though it has the private keys inside the code)
yeah, im pretty sure the version i have for xp x64 is oem though i always thought it was retail because it still had the activation prompt. i used en_windows_xp_professional_x64.iso for it.
well, i thought the product family had something to do with it because its how it identifies what it is exactly but because it only had xp pro, i thought maybe somewhere in the program, it uses 76487 for reference inside the source-code or its also maybe involved in generating the keys for something.
using the oem version is not a magic shield against the activation prompt. using oem and activating it with slp however is. also, afaik as i know, there is only an oem and vl version of x64 xp
"76487" is the first part of the Product ID (as defined by AMD64\setupp.ini), but irrelevant to the Product KEY Also, the third line determines the product type Retail (might differ from disc to disc, but on my msdn isos i generally found this): Pid=XXXXX000 OEM: Pid=XXXXXOEM VL (some other files might be different from the first two) Pid=XXXXX270
i also tried 000 as the channel id but that didnt work either because i looked at the registry in hkey_local_machine/setup/system/pid. theres a value in it which comes from the setupp.ini i think and in the last 3 digits, its only 000. maybe 000 means oem for xp x64 in numbers because i dont think its normally there since xp sp3 oem has oem as the last 3 digits in setupp.ini. when i tried to input it in the channel id box, it always forces to use 1 digit maybe because it knows its 000 but uses 1 digit. i tried using that for xpkeysp2.exe and i tried to use its keys but it didnt work, xp didnt even recognize it as a product key, thats why i thought it had something to do with the process involved in generating the keys as maybe its using product id as reference because windows xp media center also uses 76487 and thats prob why it worked for you. this may be nothing related to how activation works because i dont know how it really works but maybe it is, thats just my idea. i'll see xp x64 volume edition if that differs since its not oem. xp x64 volume edition has 76588270 as pid. nope, xpkeysp2.exe doesnt work either for volume edition of xp sp2 x64.
please, change the setupp.ini (only works for retail and oem, as vl has different files) BEFORE installing windows (on the installation media). that way you can try over and over again back just going back to the page with the product key request during setup or so you can just restart setup
what do you want me to change exactly? im doing a clean install with en_win_xp_pro_x64_with_sp2_vl_x13-41611.iso.
don't use x64 based editions, as xpkeysp2 cannot generate keys for them (even the valid keys i find get rejected by my "Windows XP" PID checker)
yeah, thats what i meant, i need a new xpkeysp2.exe that recognizes xp sp1 or sp2 x64 because maybe its something to do with pidgen.dll and others that are related that are perhaps also related to the pid value. i think it only allows keys that came from the pid value of 76588 but because this keygen only makes keys from 76487, it doesnt allow it. maybe when windows xp sp2 x64 is trying to validate the product key, maybe its decrypting the key to find out additional information that its only for pid 76487 and not recognizing the product key as valid cause its alien?