If this violates the rules please delete it for me! Can some one help me make a key generator with the following information: exclude following numbers and letters from key: Numbers:0,1,5 Letters: A,E,I,L,N,O,S,U,Z How to create a serial number template Let's take a look at an actual Microsoft product key as an example: The key "CB48T - GGBCX - H269K - C9W64 - X2RWD" would be represented in the SerialNumberTemplate property as "^^%#^ - ^^^^^ - ^%%%^ - ^%^%% - ^%^^^" - the "^" characters represent placeholders for letters, the "#" character represents a number that is ignored, and the "%" character represents a number that will be evaluated by the validation algorithm. So in this case, if you add together the numbers represented by "%" and ignore the number represented by "#" you get 42; dividing this by 7 leaves a remainder of 0 so the validation succeeds. If you were to use this same template for your product key, you would need to generate a series of keys to provide to your customers when you distribute your program, randomizing the placeholder characters, and also randomizing the numbers but making sure that the numbers represented by "%" are divisible by 7. Note that there is a seemingly arbitrary restriction in that each time you change the editable character a new text box is created, so the above example would create 12 textboxes, not 5 as in a Microsoft product key. To get around this restriction, make sure that only one grouping contains the numbers that you will validate, and use the "?" character in all of the other fields: "????? - %%%%% - ????? - ????? - ?????". You could still use a mix of numbers and letters in your keys, but the second box would always contain numbers - i.e. "BC45T - 340707 - 1XFFE - EFT22 - 1XYZ3". What would I need to do to make a key generator?
i was thinking we have 2 pidxchk checker tools available, would it be possible to make a proggie to put random characters into the pid checker, have the pid chcker to check if the key is good or bad if good save to a .txt file, if bad keep going till a good one turns up i know this may take a long time to find good keys but would this be possible to do.
It is possible, but at 30 to 45 seconds plus per key checked, it is not plausible... This has been discussed before many times and it always comes down to the same point. You can do it by brute force (trying every possible combination of alphanumeric characters in sequence, one by one) but it would take so long to find even 1 usable key that probably would not even be genuine when validated online (because it might not be on the windows 7 product key whitelist) that it would be a waste of time to do. I say go for it if you want to try to code a brute force keygen...it would be quite easy to do, to query PidGenX for all possible keys in sequence...but you will be waiting a long, long time...and you'll be cranking your CPU near capacity the whole time, which is probably not good for any length of time straight (like the days or weeks or months straight of brute-force checking that would be required to yield 1 key). Good luck.
The other thing is: Each S/N must have at least 12-15 different numbers and letters: e.g.: BC45T - 34077 - 1XFFE - EFT22 - 1XYZ3 == Can be valit, because of 17 diffrent numbers&letters BB45B - 45454 - 7BCDB - BC45D - DB5C7 == Can't be valid because of only 6 diffrent numbers&letters Next thing is: If two letters are the same and are placed like this: BFFC1, key cant have more "double-letters" eg. CB48T - GGBCX - H269K - C9W64 - X2RWD == Can be Valid CB48T - GGBCX - H269K - BBW64 - X2RWD == Can't be valid because of 2x"double-letters" Brute-force method is very slow, but if you'll have a lot of restrictions and tips - it can be faster Sorry for my English
Also using Nvidia GPU could improve the speed dramatically And also we could only be interested in getting the SLP key (there must be more than available to OEMs) sebus
But bruteforce keygen was already made in early Vista times, both script based on slmgr.vbs and compiled exe... ..nothing really new to do there... cause even if the speed of checking could be increased x1000, it would still take years if not thousands of years to generate one working key. If someone is not lazy, they can calculate the total number of allowed keys from decrypted pkeyconfig.xrm-ms (assuming there can be one key for each PID), and compare it with total number of possible combinations of valid symbols in a MS key (24^25, i guess)...
Has there ever been a successful attempt at generating a key that will activate online for Vista ? The answer as far as I know -- NO!
As I have said before in other threads, the ONLY way that a brute-force keygen would be practical for Windows Vista/7 at all would be if someone were to do it via distributed computing/processing (like SETI@Home and the Stanford medical thing where people "fold" with their GPUs and CPUs)...or with a server farm. Anything else is a waste of time and will only tax your system until it dies a painful death from overheating from being run at full capacity for weeks to months straight....and then we have to hope that that key we found is on MS's "white-list", as it would most likely be a retail key, as those are the most abundant (just guessing based on sheer odds). If we were going to brute force for only SLP keys, then that would be straight-up ridiculous to attempt to do on a single PC, as we narrow our possible "good key" outcome down to only a handful of SLP keys (in comparison to all possible good Win7 keys that are retail, OEM:COA/OEM:Non-SLP, etc.) in the range of millions of possible outcomes/attempts. Good luck though EDIT: As anyone has ever used a product key checker probably knows, the Windows product key algorithms are very complex and utilize massive system resources to check a product key with the pidgen.dll call...just go ahead and run any Vista/7 product key checker and check a key and watch your CPU usage jump, you will see what I mean. Envision running a product key checker 24 hours a day, 7 days a week, for possibly months at a time... It is a sure-fire way to ruin a CPU and motherboard unless you have specialized cooling in place...or distributed processing like I mention above. This is why there are no key generators for Windows 7...not because it is impossible, but because it is so impractical that no one will bother to make one. Maybe one day someone will leak MS' "private key" (yeah right ), but until then brute-force is the only way to go.
Well, had a look at key ranges, and the number of valid keys is definitely not more than 10^12... and the number of possible combinations is 24^25 ( = about 3.2 x 10^34), and this means less than one of 10^21 (1000000000000000000000) randomly generated keys will pass pidchecker successfully. Doesn't look like SETI with GPU's can help here...
If there was a way to brute force for Win7 keys, distributed processing would be the only way. It is just sheer numbers, instead of 1 PC cranking numbers, you would have hundreds of thousands of computers working as well. If you cannot see the power in that then you are not looking. I didn't say that it was practical or realistic, all I said was that it was the only way that a brute force keygen could possible work.
They should like invade googles server farms and set it running on those. We'll have a key every 5 mins
Oh yes I agree~ Luckily keygens for WinRAR and WinZip are simple and easy to search~ Otherwise I will go bankrupt (wasting too much to buy a sw )~ Hopefully only MS will do this fn_cky product key algorithms === I wonder how MS cries when no one purchase its products!!!
another important thing about keygens: don't forget the 8bit music Some music on keygens is so great....
why not ? It has been done for Windows XP Pro (a real keygen, not a brute force to find a relatively good key) M$ use elliptic curves to render the reverse process very slow.