The Ultimate PID Checker

Discussion in 'MDL Projects and Applications' started by janek2012, Jul 18, 2010.

  1. EFA11

    EFA11 Avatar Guru

    Oct 7, 2010
    8,730
    6,690
    270
    #341 EFA11, Feb 8, 2014
    Last edited by a moderator: May 23, 2017
  2. debin

    debin MDL Member

    Mar 2, 2010
    199
    26
    10
    I have some Win 8.1 MAK Keys, is there already a "The Ultimate PID Checker" Version out for check?o_O

    cheers
    debin
     
  3. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    17,703
    15,807
    340
  4. Carlos Detweiller

    Carlos Detweiller MDL Spinning Tortoise

    Dec 21, 2012
    2,959
    2,579
    90
    Just use the current one. Download the 8.1 pkeyconfig from post #328, extract it and place it next to the keychecker for easy access. In the keychecker, select Custom and browse to the pkeyconfig.xrm-ms file you have just extracted. Then you will be able to check your MAKs, provided the keychecker can access MS servers for determining remaining activation count.
     
  5. debin

    debin MDL Member

    Mar 2, 2010
    199
    26
    10
    Thank you. :rolleyes:
     
  6. waledakmal

    waledakmal MDL Novice

    Apr 7, 2011
    29
    4
    0
    what about retail .. as key checker
     
  7. Carlos Detweiller

    Carlos Detweiller MDL Spinning Tortoise

    Dec 21, 2012
    2,959
    2,579
    90
    pkeyconfig can check all activation channels, including Retail.
     
  8. waledakmal

    waledakmal MDL Novice

    Apr 7, 2011
    29
    4
    0
    pkeyconfig show when mak keys (0) after remaining online ..keys still works ok
    pkeyconfig does not give remaining or activation ...for retails after End Activations online
    like this win 7 ultimate retail key still working offline (call) but pkeyconfig does not give activation account

    try this sir
    ....
    sorry for my bad english
     
  9. Carlos Detweiller

    Carlos Detweiller MDL Spinning Tortoise

    Dec 21, 2012
    2,959
    2,579
    90
    Contrary to checking a Multi-Activation Key (MAK) which has many activations by design, a Retail key has only one. There simply is no way provided by Microsoft for checking status of Retail/OEM keys.

    Checking activation count for MAKs is a feature of VAMT for VL. It's the only action that requires Internet access, as it will operate directly on MS' servers.
     
  10. CoreCore

    CoreCore MDL Novice

    Apr 10, 2014
    1
    0
    0
    I will see if that config file works for 8.1.... Thanks guys
     
  11. topeagle

    topeagle MDL Novice

    May 6, 2014
    1
    0
    0
    I'm trying to understand the windows vbscript posted within this thread to retrieve the Windows 8 Product Key. The VBScript start with:


    isWin8 = (Key(66) \ 6) And 1
    Key(66) = (Key(66) And &HF7) Or ((isWin8 And 2) * 4)


    now isWIn8 will always be either 0 or 1. And the expression ((isWin8 And 2) * 4) will always be 0. Could the author of this code provide some explanation about why he didn't write :


    Key(66) = (Key(66) And &HF7)


    Thx
     
  12. imgwhirl

    imgwhirl MDL Novice

    Jul 13, 2014
    49
    10
    0
    just doing so out of fun i checked my legal key with it, worked great, however,
    does the checker uses my retail key online activation count?
    if so i will refrain from messing around with my keys
     
  13. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    17,703
    15,807
    340
    Activation count of retail keys can't be determined. The checker works locally.
     
  14. tosi

    tosi MDL Novice

    Apr 11, 2014
    4
    0
    0
    Hi,
    first: thank you for the awesome app. I consider it very helpful. Good job.

    However I don't fully understand how it works. What exactly is pidgen.dll and what is pkeyconf? Where is information about the key taken from? How much I can rely on that?

    My goal is to check whether the key is retail or MSDN (I am buying some keys online and I wanna be sure it is not bogus). There is a slight difference in the EULA part in Ultimate PID checker (it says MSDN vs. retail), but if I don't know where it comes from, I can't 100% rely on that.

    Somebody wrote on MS forum that a part of a product ID (three digits -xxx-) makes the difference. There is no official documentation on it and the information differs. While -231- from my current key seems to be an MSDN key according to MS forum, this SW says it is retail. Are they right there or is it nonsense?

    Thank you
     
  15. s1ave77

    s1ave77 MDL Guide Dog/Dev

    Aug 15, 2012
    16,125
    24,347
    340
    Don't confuse things ... MSDN is the source of Retail ISOs and Keys not a license channel. License Channels would be RETAIL, OEM_DM, VOLUME_KMSCLIENT (to name some, there are more).

    Key info is stored in encrypted form in: "C:\Windows\System32\spp\tokens\pkeyconfig\pkeyconfig.xrm-ms".

    So far the tool never failed here, if it says RETAIL you can take that for granted :cool2:.
     
  16. Carlos Detweiller

    Carlos Detweiller MDL Spinning Tortoise

    Dec 21, 2012
    2,959
    2,579
    90
    MSDN keys can be identified by that second part of the ProductID (the mentioned -xxx-). MS uses certain ranges in that segment for MSDN keys. The license channel of MSDN keys is almost always RETAIL.
     
  17. tosi

    tosi MDL Novice

    Apr 11, 2014
    4
    0
    0
    Thank you guys!

    AFAIK all MSDN keys are distributed within retail "channel", but another policy is applied (you can't re-sell them and you can't legally use them if you don't have subscription). If you buy MSDN subscription, you get access to MSDN ISOs and keys, but you can't sell them further (but people do it).

    I have two W7 home premium licenses bought from internet as an example (two different sources).

    Profile: NT 6.1 SP1
    Validity: Valid
    Product ID: XXXXX-231-1403024-06003
    Advanced ID: XXXXX-00212-231-140302-00-1029-7601.0000-2332014
    Activation ID: ee4e1629-bcdc-4b42-a68f-b92e135f78d7
    Edition Type: HomePremium
    Description: Windows 7 SP1 HomePremium Retail
    Edition ID: X16-95500
    Key Type: Retail
    EULA: Retail
    Crypto ID: 212

    Profile: NT 6.1 SP1
    Validity: Valid
    Product ID: XXXXX-232-6262813-86542
    Advanced ID: XXXXX-00172-232-626281-00-1029-7601.0000-2332014
    Activation ID: 3b965dfc-31d9-4903-886f-873a0382776c
    Edition Type: HomePremium
    Description: Windows 7 Home Premium Retail
    Edition ID: X15-39013
    Key Type: Retail
    EULA: MSDN
    Crypto ID: 172

    Both channel ID looks like MSDN (-231- and -232-) (also a lady on MS chat told me the first one is MSDN, but I am not sure if I can trust her, because at first she told me she can't verify a Windows key). Why is there the difference in EULA? All the information here is from pkeyconf (except for product ID, of course). Is there any forum thread explaining all the information (I found only product-id guide for Windows 8)?

    And what is "EULA: ltPERP" in Office licenses? Google doesn't know either.
     
  18. tosi

    tosi MDL Novice

    Apr 11, 2014
    4
    0
    0