posted on BA by arseny92 Part of Rights Account Certificate (RAC) GUID, used to enable locked features on a pkey-per-employee basis. Can be traced, unless the system is installed with default key (product.ini), then untraceable. On key installation and activation Security-SPP logs the process to Application Event Log, the process can be seen detailed, described below: On SPP (Software Protection) check load, it initalizes the status for these service objects, to check then if the installed key comforms to one of these algorithms: C:\Windows\system32\sppwinob.dll, msft:spp/windowsfunctionality/agent/7.0, 0x00000000, 0x00000000 C:\Windows\system32\sppobjs.dll, msft:rm/algorithm/phone/1.0, 0x00000000, 0x00000000 C:\Windows\system32\sppobjs.dll, msft:rm/algorithm/pkey/2005, 0x00000000, 0x00000000 C:\Windows\system32\sppobjs.dll, msft:spp/TaskScheduler/1.0, 0x00000000, 0x00000000 C:\Windows\system32\sppobjs.dll, msft:spp/volume/services/kms/1.0, 0x00000000, 0x00000000 C:\Windows\system32\sppobjs.dll, msft:spp/volume/services/kms/licenserenewal/1.0, 0x00000000, 0x00000000 and then checks the Activation ID for validty. If it fails, the Genuine Status for the given Application ID will be set to non-genuine, until installation of a genuine key. It also sends an alert to Winlogon, that Windows is running in Notification period. Winlogon then enforces the policies for a non-genuine system (i.e. removing the background, displaying non-genuine notice on watermark area, popping notifications about counterfeit software, etc.). At the time of installation of a genuine key, the following procedures happen: 1. Installation of a Proof of Purchase, ACID and PkeyID referred here 2. Check validty and type of the key with msft:rm/algorithm/flags/1.0 and msft:rm/algorithm/pkey/2005 3. Acquisition of Rights Account Certificate (this later check on msft:spp/windowsfunctionality/agent/7.0) 4. Installation of two XrML 2.1 Licenses for the received Rights Account Certificate : {msft:sl/RAC/ACTIVATED/PUBLIC} and {msft:sl/RAC/ACTIVATED/PRIVATE} License ID keys. Both keys tying to the given SKU ID as a Product Certificate GUID. 5. Acquisition of an End User License 6. Installation of two XrML 2.1 Licenses {msft:sl/EUL/ACTIVATED/PUBLIC} and {msft:sl/EUL/ACTIVATED/PRIVATE} License ID keys. Both keys tying to the given SKU ID as an End User License. 7. Validation of the license with Windows Activation Technologies with msft:rm/algorithm/hwid/4.0 8. If passed (no several Installation IDs logged for the key), set Genuine Status to genuine for the given Application ID, if fail, set Winlogon to Notification period as described above. 9. Enforcement or excludenent of features' policies (fully customizable, example policy: Shell-InBoxGames-Solitaire-EnableGame), for the given Application ID and SKU ID. This is where SLC calls for RP-permissions for locked features. Conclusion The RAC succeeded the feature, that was known before as a Build GUID. On any Windows 8 build go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion. Note that the BuildGUID string is all ffffffff-ffff-ffff-ffff-ffffffffffff - this is because it is obsolete, it is is no longer used as the build identifier, the Rights Account Certificate is used instead).
A leak will happen when it happens. 7955 is the latest PC build. 7959 is the latest server build. Don't ask for 7971 again or a mod will come and give you an infraction!
A new rule for this thread: Please stop posting fake stuff. If you do, a moderator will come and give you an infraction and you'll eventually get banned. This rule will sure give this thread fake free!