Test version with new about option --> All using SLC api. only for Products with PKEY --> Activated or not. not matter, for normal human, only for Version who have install key beta version uploaded, more error decode. there is still some problem, wmi say 180 days api say, not licensed ? wtf ? need few tests
v16.0.0 [compiled at 18-06-25] Code: * Add Status info for Active license's only, With lot of extra extra license status information * Use MRP SL ERROR file RCodes.ini, to expend error list database * Add wmi window, details for every SKU in system * Add alternative Get-OA3xOriginalProductKey method * Update fetch method, now show ESU & Other products well, Also use short `name` from PKEYCONFIG file ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Look better --> Test version, attached. also, show SHort 180 day, 38, 4K, or other type of license using api, no wmi attached. origional name from WMI class. also, it show enum text value of license, not 0,2,3,5 Also, i use MRP SL error file, to get more SL error messege info next step, i want make another form, list of wmi, and information per WMI.
While the Office product is selected, the 'License Info' tab gives the message "Valid key for product's licensing channel was used for activation", the 'Genuine Info' tab gives the message 'The Software Licensing Service reported that the product key is invalid for this Windows edition.' isn't this a contradiction? Office and Windows products are activated with the TSF method.
this is 2 diffrent api, intersting My thoughts, TSForge, so technically it can't be activated So you get an error, but it activated in store file
v16.0.3 [compiled at 20-06-25] Code: * Add Status info for Active license's only, With lot of extra extra license status information * Use MRP SL ERROR file RCodes.ini, to expend error list database * Add wmi window, details for every SKU in system * Add alternative Get-OA3xOriginalProductKey method * Update fetch method, now show ESU & Other products well, Also use short `name` from PKEYCONFIG file * Bug fix in KMS38/HWID, cau`se the script to hang out * Update Parameters XOR logic of For All Function, Who, Include 2 Or more Option * Get-SLIDList, Major update, User firendly parameter error info, Also, Now can use [eQueryIdType]::SL_ID_APPLICATION -> Without `-pQueryId` Will ENUM data using Hardcoded know'e'n App GUID instead
Where can I find what the different fields are and the constrains to them? Like GUID, everything I try is invalid. Or secret. Most numbers work, leave it blank and then decode sn and secrets are like this "8541687472598409", but what is the range, accepted values? What governs an upgrade key? Just curious trying to understand this.
Only Ms know it, But specific- there is range option For each sku, find it in the config file and if you type this -> Code: # Line 9713 - remove part of >> `| select -First 1` GenerateConfigList -pkeyconfig "$env:windir\System32\spp\tokens\pkeyconfig\pkeyconfig.xrm-ms" -SkipKey $true | % { Write-Host; Write-Host SKU ($_).ActConfigId; Write-Host "Range $(($_).KeyRanges.Ranges.Count)"; ($_).KeyRanges.ToString() } }
Interesting. I saw somewhere that ID was a vender code, like dell or hp. Is there a way to generate license key from ePID, like 06401-04919-026-664503-02-1033-26100.0000-2912024 (generated from CZ-ePID gen 2.1.5)?
upload improved version, that start look like origional WMI search All properties show work, like wmi, just with SL-API thank aboody for help with some hard to find properties its not like MS give lot of info. Code: # ***************************** # # v16.0.5 compiled at 21-06-25 # # ***************************** # <# * Add Status info for Active license's only, With lot of extra extra license status information * Use MRP SL ERROR file RCodes.ini, to expend error list database * Add wmi window, details for every SKU in system * Add alternative Get-OA3xOriginalProductKey method * Update fetch method, now show ESU & Other products well, Also use short `name` from PKEYCONFIG file * Bug fix in KMS38/HWID, cau`se the script to hang out * Update Parameters XOR logic of For All Function, Who, Include 2 Or more Option * Get-SLIDList, Major update, User firendly parameter error info, Also, Now can use [eQueryIdType]::SL_ID_APPLICATION -> Without `-pQueryId` Will ENUM data using Hardcoded know'e'n App GUID instead * Add extra Item's in WMI info windows, like, DiscoveredKeyManagement*, KeyManagementService*, OfflineInstallationId, ExtendedGrace (thanks abbody1406 for some missing key's) * Encode Window, Encode by -> Product Name, Filter out match key's, so result's better now * Add extra WMI info, using extract data from SPP* Files #>
that nice attached file for testing purposes offset its must, otherwise, it will continue forever 20,000 to 50,000, its fair number Anyway, selected number will copied to clipboard
Code: # ***************************** # # v16.0.6 compiled at 22-06-25 # # ***************************** # <# * Add extra Item's in WMI info windows, like, DiscoveredKeyManagement*, KeyManagementService*, OfflineInstallationId, ExtendedGrace (thanks abbody1406 for some missing key's) * Encode Window, Encode by -> Product Name, Filter out match key's, so result's better now * Add extra WMI info, using extract data from SPP* Files * Add new System info Pkeyconfig Data Tab * Add new option to encode by Pattern, of User choice * Add extra extra extra Try-Catch, on wmi selection change's #> ------------------------- Problem solved, remove ' ' entiries, Plus, .ToString for ALL ! this version, include config Tab, to check, and encode with pattern, you welcome to check
another nice thing -> it also support not current edition because its parse XML Data some edition that not include in xml file, will not give any result's
something is wrong in the last version/versions, if i try to encode the default win 10 pro key (3V66T) with group 3308, secret 5594737606063274 and ID 0 i receive the error "Validate your Secret input"