You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7-2Lines changed: 7 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -110,8 +110,13 @@ The rest of the job is done within the code of this keygen.
110
110
*~~Some keys aren't valid, but it's generally a less common occurrence. About 2 in 3 of the keys should work.~~<br>
111
111
**Fixed in v1.2**. Prior versions generated a valid key with an exact chance of `0x40000/0x62A32`, which resulted in exactly
112
112
`0.64884`, or about 65%. My "2 in 3" estimate was inconceivably accurate.
113
-
* Tested **only** on Windows XP Professional SP3, but should work everywhere else as well.
114
-
* Server 2003 key generation not included yet.
113
+
* Tested on multiple Windows XP setups. Works on **Professional x86**, all service packs. Other Windows editions may not work. **x64 DOES NOT WORK**.
114
+
*~~Server 2003 key generation not included yet.~~<br>
115
+
**Fixed in v2.2**
116
+
* Some Windows XP VLK keys tend to be "worse" than others. Some of them may trigger a broken WPA with an empty Installation ID after install.
117
+
You have the best chances generating "better" keys with the `BBB` section set to `640` and the `CCCCCC` section not set to 0.
118
+
* Windows Server 2003/SP2 x64 key generation is broken. I'm not sure where to even start there. The keys don't appear to be valid anywhere,
119
+
but the algorithm is well-documented. The implementation in my case generates about 1 in 3 "valid" keys. What version they're valid in, we're yet to discover.
0 commit comments