Page 52 of 74 FirstFirst ... 242505152535462 ... LastLast
  1.    25 Sep 2016 #511
    Join Date : Dec 2015
    Posts : 5,863
    Windows10

    Quote Originally Posted by RobertJ View Post
    If the systems came with Windows 8 or 8.1 pre-installed and there is no COA sticker (i.e. the keys are embedded in the BIOS/UEFI), I believe it should be possible to retrieve the keys from the firmware.

    @Superfly: In fact I'm surprised ShowKeyPlus doesn't do this, unless I'm missing something? Why should a clean install of Windows 10 affect OEMM key retrieval from the firmware?

    BTW, is there a way to make Win7 key lookup faster? Currently it takes a really long time, and the program remains stuck at "Retrieving edition..." with no indication whether it's hung or still working. If the lookup can't be sped up then perhaps a progress bar can be added?
    Showkeyplus will extract bios oem embedded key. Poster was referring to Windows 8.1 retail keys that had been used to upgrade. Problem is that is seems there is no way of telling the upgrade history of a digital licence.
      My ComputerSystem Spec
  2.    25 Sep 2016 #512
    Join Date : Sep 2016
    Posts : 14
    Windows 10

    Quote Originally Posted by cereberus View Post
    Poster was referring to Windows 8.1 retail keys that had been used to upgrade.
    Dang, I completely missed the word "retail" in his post. So it's good to know that a clean install won't interfere with the program's ability to extract keys embedded in the BIOS.

    Hopefully the other niggles I mentioned can be fixed.

    Also there's something I wanted to confirm - keys are checked 100% locally and never sent out, right?
      My ComputerSystem Spec
  3.    25 Sep 2016 #513

    Quote Originally Posted by RobertJ View Post
    If the systems came with Windows 8 or 8.1 pre-installed and there is no COA sticker (i.e. the keys are embedded in the BIOS/UEFI), I believe it should be possible to retrieve the keys from the firmware.

    @Superfly: In fact I'm surprised ShowKeyPlus doesn't do this, unless I'm missing something? Why should a clean install of Windows 10 affect OEMM key retrieval from the firmware?

    BTW, is there a way to make Win7 key lookup faster? Currently it takes a really long time, and the program remains stuck at "Retrieving edition..." with no indication whether it's hung or still working. If the lookup can't be sped up then perhaps a progress bar can be added?
    Windows 7 key checking has always been slow...it's just the size of the configuration file that's extremely large - the only way to speed it up would be a more efficient XML search algorithm (rather than node iteration) - BTW the wait cursor should appear during the "Retrieving key..." process.


    BTW: A new pre-release to fix some of the issues reported.

    Code:
             Bug fix: Version check returning null error
    
      Exception wording added for valid keys with invalid configuration resulting in a null response for edition.
    https://github.com/Superfly-Inc/Show...howKeyPlus.zip
      My ComputerSystem Spec
  4.    25 Sep 2016 #514
    Join Date : Feb 2014
    Posts : 9,341
    Windows 10 Professional

    @Superfly:

    Works as before on Desktop PC.

    Click image for larger version. 

Name:	000010.png 
Views:	2 
Size:	35.9 KB 
ID:	103161
      My ComputersSystem Spec
  5.    25 Sep 2016 #515

    Thanx @Edwin,

    Does our "cheapie" still reflect the nondescript error?
      My ComputerSystem Spec
  6.    25 Sep 2016 #516
    Join Date : Feb 2014
    Posts : 9,341
    Windows 10 Professional

    Quote Originally Posted by Superfly View Post
    Thanx @Edwin,

    Does our "cheapie" still reflect the nondescript error?
    Not specifically, but...
    the keys are all correct, OEM key, generic entitlement key and my Pro upgrade key!

    Click image for larger version. 

Name:	1.png 
Views:	1 
Size:	82.4 KB 
ID:	103196
      My ComputersSystem Spec
  7.    27 Sep 2016 #517
    Join Date : Sep 2016
    Posts : 14
    Windows 10

    Quote Originally Posted by Superfly View Post
    Windows 7 key checking has always been slow...it's just the size of the configuration file that's extremely large - the only way to speed it up would be a more efficient XML search algorithm (rather than node iteration) - BTW the wait cursor should appear during the "Retrieving key..." process.
    It does appear, but that doesn't provide any assurance that the program hasn't hung or something. Is adding a progress bar at all possible? I think it would really help improve the end user experience (UX).

    Quote Originally Posted by Superfly View Post
    BTW: A new pre-release to fix some of the issues reported.

    Code:
    Bug fix: Version check returning null error
    
    Exception wording added for valid keys with invalid configuration resulting in a null response for edition.
    Ok, so good news is it's no longer crashing. Bad news is I'm getting the same error on trying to check a key on 32-bit Windows as mentioned in that GitHub issue:

    pidgenx2.dll is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support. Error status 0xc000035a.
    Is it extracting the 64-bit version of the DLL even when running on a 32-bit OS?
      My ComputerSystem Spec
  8.    28 Sep 2016 #518

    Quote Originally Posted by RobertJ View Post
    It does appear, but that doesn't provide any assurance that the program hasn't hung or something. Is adding a progress bar at all possible? I think it would really help improve the end user experience (UX).
    Agreed, it would be nice - but the logic takes place within a MS dll ... without it's source we are at it's mercy...

    Quote Originally Posted by RobertJ View Post
    Ok, so good news is it's no longer crashing. Bad news is I'm getting the same error on trying to check a key on 32-bit Windows as mentioned in that GitHub issue:

    Is it extracting the 64-bit version of the DLL even when running on a 32-bit OS?
    Yes, it should only extract the dll if the installed one fails...but I haven't looked into that yet ... stay tuned.

    ... and thanx for the feedback.
      My ComputerSystem Spec
  9.    29 Sep 2016 #519
    Join Date : Dec 2015
    Posts : 5,863
    Windows10

    Hi C,

    Here is an odd one - I am running 10 pro Insider in hyper-v unactivated. and I wanted to get the generic key (to tell somebody how to upgrade to pro without reinstalling), and got the following. The host OS is Windows Pro N, although PC was originally 8 Core (normal) with a bios embedded 8 key.

    I was surprised to see the Vista message.

    Rgds

    M.

    Click image for larger version. 

Name:	2016_09_29_23_00_411.png 
Views:	31 
Size:	45.8 KB 
ID:	103686
      My ComputerSystem Spec
  10.    30 Sep 2016 #520

    Howzit M,

    Interesting hey? I have the same - Hyper-V has a SLIC 2.0 (i.e Vista OEM marker)

    Click image for larger version. 

Name:	Capture.PNG 
Views:	7 
Size:	254.5 KB 
ID:	103740
      My ComputerSystem Spec

 
Page 52 of 74 FirstFirst ... 242505152535462 ... LastLast

Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 16:44.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums